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.
36
Quality
7%
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 severely underdeveloped, essentially just restating the skill name without explaining what it does or when to use it. It lacks any concrete actions, meaningful trigger terms, or guidance that would help Claude select this skill appropriately from a list of available skills.
Suggestions
Add specific actions the skill performs, e.g., 'Validates test method names follow naming conventions, suggests renames for non-compliant tests, enforces patterns like test_<action>_<expected_result>'
Include natural trigger terms users would say: 'test names', 'naming conventions', 'test method names', 'rename tests', 'test file naming', 'BDD naming'
Add an explicit 'Use when...' clause: 'Use when reviewing test names, enforcing naming standards, or when user mentions test naming conventions or patterns'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Test Naming Enforcer' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'validates', 'renames', 'checks', or 'enforces naming conventions'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause only references the skill name itself rather than providing meaningful trigger guidance. Both components are essentially missing. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'test naming enforcer' repeated twice, which is the skill name itself rather than natural keywords users would say. Missing terms like 'test names', 'naming conventions', 'test file names', 'rename tests', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The 'Test Automation' category and 'naming' focus provide some specificity, but without concrete actions described, it's unclear how this differs from other test-related skills or what specific naming scenarios it handles. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a hollow template with no actual content. It describes a 'Test Naming Enforcer' capability but provides zero concrete guidance on what test naming conventions to enforce, how to detect violations, or how to fix them. The entire body consists of generic boilerplate that could apply to any skill.
Suggestions
Add concrete test naming conventions with examples (e.g., 'should_ReturnX_WhenY', 'test_feature_scenario_expected')
Include executable code showing how to validate test names programmatically (regex patterns, linter rules, or test framework configurations)
Provide before/after examples of poorly-named tests and their corrected versions
Add specific guidance for different test frameworks mentioned in tags (Jest, pytest) since naming conventions differ
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need and add no actionable value. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific naming conventions, no patterns, no commands. The skill describes what it does abstractly but never shows how to actually enforce test naming conventions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The content only lists vague 'capabilities' without explaining any process for enforcing test naming. | 1 / 3 |
Progressive Disclosure | The content has some structure with clear sections (Purpose, When to Use, Capabilities, etc.), but there are no references to detailed materials and the sections contain no substantive content to organize. | 2 / 3 |
Total | 5 / 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
60433a6
- 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.