Web Application Testing
anthropics/skills
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
Test Naming Enforcer - Auto-activating skill for Test Automation.
Install Test Naming Enforcer
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill test-naming-enforcer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace test-naming-enforcer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/09-test-automation/test-naming-enforcer .claude/skills/test-naming-enforcer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "test-naming-enforcer" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/09-test-automation/test-naming-enforcer into .claude/skills/test-naming-enforcer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-naming-enforcer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/09-test-automation/test-naming-enforcerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill test-naming-enforcer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace test-naming-enforcer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/09-test-automation/test-naming-enforcer .agents/skills/test-naming-enforcer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "test-naming-enforcer" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/09-test-automation/test-naming-enforcer into .agents/skills/test-naming-enforcer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-naming-enforcer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill test-naming-enforcer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace test-naming-enforcer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/09-test-automation/test-naming-enforcer .cursor/skills/test-naming-enforcer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "test-naming-enforcer" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/09-test-automation/test-naming-enforcer into .cursor/skills/test-naming-enforcer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-naming-enforcer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/09-test-automation/test-naming-enforcer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill test-naming-enforcer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace test-naming-enforcer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/09-test-automation/test-naming-enforcer .gemini/skills/test-naming-enforcer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "test-naming-enforcer" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/09-test-automation/test-naming-enforcer into .gemini/skills/test-naming-enforcer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-naming-enforcer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace test-naming-enforcerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill test-naming-enforcer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/09-test-automation/test-naming-enforcer .github/skills/test-naming-enforcer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "test-naming-enforcer" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/09-test-automation/test-naming-enforcer into .github/skills/test-naming-enforcer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-naming-enforcer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill test-naming-enforcer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace test-naming-enforcer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/09-test-automation/test-naming-enforcer .opencode/skills/test-naming-enforcer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "test-naming-enforcer" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/09-test-automation/test-naming-enforcer into .opencode/skills/test-naming-enforcer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-naming-enforcer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
test-naming-enforcer- GitHub stars
- 2.8k
- Token cost
- ~552 tokens
- SKILL.md length
- 196 words
- Files
- 1
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Test Naming Enforcer - Auto-activating skill for Test Automation.
- Works in 4 steps: Provides step-by-step guidance for test… → Follows industry best practices and… → Generates production-ready code and… → …
- : test naming enforcer
- SKILL.md covers Overview, When to Use, Instructions and Examples, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Test Naming Enforcer is an agent skill from jeremylongshore/tons-of-skills-marketplace. Test Naming Enforcer - Auto-activating skill for Test Automation. Triggers on: test naming enforcer, test naming enforcer Part of the Test Automation skill category. Use when writing or running tests. Trigger with phrases like "test naming enforcer", "test enforcer", "test".
Its SKILL.md is about 550 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for Claude Code
It sits in Testing & QA. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- : test naming enforcer
- Test naming enforcer Part of the Test Automation skill category
- With phrases like test naming enforcer
Example prompts
- “test naming enforcer”
- “test enforcer”
- “/test-naming-enforcer”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(cmd:*), Grep
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Provides step-by-step guidance for test naming enforcer
- Follows industry best practices and patterns
- Generates production-ready code and configurations
- Validates outputs against common standards
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBash(cmd:*)Grep
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Test Naming Enforcer loads about 552 tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 196 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 196 words, ~552 tokens.
Download SKILL.mdSave it as
.claude/skills/test-naming-enforcer/SKILL.md (or your agent's skills folder).- name
- test-naming-enforcer
- description
- Test Naming Enforcer - Auto-activating skill for Test Automation. Triggers on: test naming enforcer, test naming enforcer Part of the Test Automation skill category. Use when writing or running tests. Trigger with phrases like "test naming enforcer", "test enforcer", "test".
- allowed-tools
- Read, Write, Edit, Bash(cmd:*), Grep
- compatibility
- Designed for Claude Code
- version
- 1.0.0
- license
- MIT
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- tags
- testing, automation
Test Naming Enforcer
Overview
This skill provides automated assistance for test naming enforcer tasks within the Test Automation domain.
When to Use
This skill activates automatically when you:
- Mention "test naming enforcer" in your request
- Ask about test naming enforcer patterns or best practices
- Need help with test automation skills covering unit testing, integration testing, mocking, and test framework configuration.
Instructions
- Provides step-by-step guidance for test naming enforcer
- Follows industry best practices and patterns
- Generates production-ready code and configurations
- Validates outputs against common standards
Examples
Example: Basic Usage Request: "Help me with test naming enforcer" Result: Provides step-by-step guidance and generates appropriate configurations
Prerequisites
- Relevant development environment configured
- Access to necessary tools and services
- Basic understanding of test automation concepts
Output
- Generated configurations and code
- Best practice recommendations
- Validation results
Error Handling
| Error | Cause | Solution |
|---|---|---|
| Configuration invalid | Missing required fields | Check documentation for required parameters |
| Tool not found | Dependency not installed | Install required tools per prerequisites |
| Permission denied | Insufficient access | Verify credentials and permissions |
Resources
- Official documentation for related tools
- Best practices guides
- Community examples and tutorials
Related Skills
Part of the Test Automation skill category. Tags: testing, jest, pytest, mocking, tdd
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/09-test-automation/test-naming-enforcer of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Compare with similar skills
Test Naming Enforcer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Test Naming Enforcer this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~552 | Automated safety check: Pass | MIT | |
| Web Application Testinganthropics/skills | 180k | 51 repos | ~966 | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Bugsfossasia/eventyay-interpretation | 1.6k | 32 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| TDDpietheinstrengholt/rssmonster | 564 | 30 repos | ~906 | Automated safety check: Pass | MIT | |
| TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph | 112 | 11 repos | ~2.4k | Automated safety check: Pass | None | |
| TDDsanity-io/sanity | 6.4k | 20 repos | ~1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Diagnosing Bugs
fossasia/eventyay-interpretation
Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.
TDD
pietheinstrengholt/rssmonster
Test-driven development. An agent skill from pietheinstrengholt/rssmonster.
TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
- Official
TDD
sanity-io/sanity
Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.
Context Driven Development
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Categories
Questions about Test Naming Enforcer
What does Test Naming Enforcer do?
Test Naming Enforcer - Auto-activating skill for Test Automation. Test Naming Enforcer is an agent skill from jeremylongshore/tons-of-skills-marketplace. Test Naming Enforcer - Auto-activating skill for Test Automation.
When should I use Test Naming Enforcer?
Test Naming Enforcer fits situations like: : test naming enforcer; test naming enforcer Part of the Test Automation skill category; with phrases like test naming enforcer.
How do I install Test Naming Enforcer in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill test-naming-enforcer -a claude-code`. Or copy the skill folder (skills/09-test-automation/test-naming-enforcer in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/test-naming-enforcer in your project. Claude Code loads it when a task matches its description.
How do I install Test Naming Enforcer in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill test-naming-enforcer -a codex`. Or copy the skill folder (skills/09-test-automation/test-naming-enforcer in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/test-naming-enforcer in your project. Codex loads it when a task matches its description.
Can I use Test Naming Enforcer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill test-naming-enforcer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-naming-enforcer, .gemini/skills/test-naming-enforcer, .github/skills/test-naming-enforcer and .opencode/skills/test-naming-enforcer in your project.
What does Test Naming Enforcer need to run?
SKILL.md names no scripts, command-line tools or credentials: Test Naming Enforcer is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(cmd:*), Grep. Compatibility (from SKILL.md): Designed for Claude Code.
Does Test Naming Enforcer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Test Naming Enforcer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Test Naming Enforcer use?
Test Naming Enforcer is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Test Naming Enforcer use?
About 552 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Test Naming Enforcer?
Skills that share tags, products or a category with Test Naming Enforcer: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (pietheinstrengholt/rssmonster, 564 stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Test Naming Enforcer?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.