test-naming-enforcer
Test Naming Enforcer - Auto-activating skill for Test Automation. Triggers on: test naming enforcer, test naming enforcer Part of the Test Automation skill category.
34
3%
Does it follow best practices?
Impact
87%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/test-naming-enforcer/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a title and category label with no substantive content. It fails to describe what the skill does, provides no natural trigger terms, and lacks any 'Use when...' guidance. It would be nearly impossible for Claude to correctly select this skill from a pool of alternatives based on this description alone.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Enforces consistent naming conventions for test methods and test classes, validates test names follow patterns like should_X_when_Y, and renames non-compliant tests.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about test naming conventions, test method names, renaming tests, or enforcing test naming standards.'
Remove the duplicate trigger term and expand with natural variations users might say, such as 'test names', 'naming convention', 'test method naming', 'rename test', 'test naming pattern'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Test Automation') and a concept ('Test Naming Enforcer') but describes no concrete actions. There is no indication of what the skill actually does—no verbs like 'validates', 'renames', 'enforces naming conventions', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title, and the 'when' clause is essentially just the skill name repeated. There is no explicit 'Use when...' guidance or meaningful trigger information. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'test naming enforcer' repeated twice. These are not natural keywords a user would say; users are more likely to say things like 'test names', 'naming convention', 'rename tests', 'test method names', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'Test Naming Enforcer' is fairly specific as a niche concept, which reduces conflict risk somewhat. However, without concrete actions described, it could overlap with other test-related skills in ambiguous ways. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template/placeholder with no actual content. It repeatedly references 'test naming enforcer' without ever defining what test naming conventions to enforce, how to enforce them, or providing any concrete examples, patterns, or code. It provides zero value beyond what the skill's title already communicates.
Suggestions
Define the actual test naming conventions to enforce (e.g., 'should_ReturnX_WhenY', 'test_feature_scenario_expected', etc.) with concrete examples for each supported framework (Jest, pytest).
Add executable code examples showing how to validate/lint test names, such as ESLint rules, pytest plugins, or custom scripts that check naming patterns.
Include concrete before/after examples of bad vs. good test names with explanations of why the naming matters.
Remove all boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content like naming pattern rules, enforcement tooling setup, and validation steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know and provides zero domain-specific information about test naming conventions or enforcement. Every section restates the skill name without adding substance. | 1 / 3 |
Actionability | There are no concrete instructions, code examples, commands, naming patterns, or executable guidance whatsoever. The skill describes what it could do ('provides step-by-step guidance') without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero steps. There are no validation checkpoints or any actionable sequence. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive structure with no references to external files, no meaningful section hierarchy, and no actual content to organize. The sections are just restatements of the skill name. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.