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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill test-naming-enforcerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely lacking in all key areas. It provides no concrete actions, no natural trigger terms users would say, and no guidance on when to use the skill. The description essentially just restates the skill name without explaining its purpose or capabilities.
Suggestions
Add specific actions the skill performs, e.g., 'Validates test method names against naming conventions, suggests renamed tests, checks for descriptive test names following Given-When-Then or Should patterns'
Include natural trigger terms users would say: 'test names', 'naming conventions', 'rename tests', 'test method names', 'describe blocks', 'it blocks'
Add an explicit 'Use when...' clause: 'Use when reviewing test files, enforcing naming standards, or when the user asks about test naming conventions or wants to improve test readability'
| 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' guidance is just the skill name repeated. There's no explicit trigger guidance or use cases explaining when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms listed 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 or clear triggers, it could overlap with other testing-related skills. The narrow domain of 'test naming' offers some distinction. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is entirely placeholder boilerplate with no actual substance. It fails to provide any concrete test naming conventions, patterns, examples, or actionable guidance. The content describes what the skill supposedly does without ever demonstrating or instructing anything specific about test naming.
Suggestions
Add concrete test naming conventions with specific examples (e.g., 'test_<methodName>_<scenario>_<expectedResult>' with real code samples)
Include executable code examples showing properly named tests in Jest/pytest with before/after comparisons
Define a clear workflow for reviewing and renaming tests, including validation steps to check naming consistency
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable patterns
| 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 commands, no actual test naming conventions or patterns. The skill describes what it does abstractly but never instructs how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The content only lists vague 'capabilities' without explaining any process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials. No references to examples, patterns, or detailed documentation are provided. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.