test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is a strong, well-crafted skill description that excels across all dimensions. It provides specific concrete actions, comprehensive trigger terms covering multiple testing disciplines and tools, explicit 'Use when' guidance, and a clearly distinct niche. The description is thorough without being padded, using third person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports' across named disciplines (functional, performance, security). | 3 / 3 |
Completeness | Clearly answers both 'what' (generates test files, creates mocking strategies, analyzes coverage, designs architectures, produces plans/reports) and 'when' with an explicit 'Use when...' clause listing numerous specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'unit tests', 'integration tests', 'E2E tests', 'test strategies', 'automation frameworks', 'coverage gaps', 'k6', 'Artillery', 'OWASP', 'flaky tests', 'QA', 'regression', 'test automation', 'quality gates', 'shift-left testing', 'test maintenance'. These are terms practitioners naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around testing and QA. The specific mention of testing tools (k6, Artillery), methodologies (OWASP, shift-left), and testing types (unit, integration, E2E, performance, security) makes it highly distinguishable from general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong progressive disclosure, clear workflow sequencing with validation checkpoints, and actionable code examples. The main weakness is minor verbosity in the introductory text and some constraints that state things Claude already knows. Overall it's a high-quality skill that effectively balances overview content with detailed reference pointers.
Suggestions
Trim the opening description line and the explanatory sentence before the code example — the heading and code speak for themselves.
In the Constraints section, consider removing items that are standard testing knowledge for Claude (e.g., 'Mock external dependencies — never call real APIs or databases in unit tests') and focus on project-specific or non-obvious constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some unnecessary filler phrases like 'Comprehensive testing specialist ensuring software quality through functional, performance, and security testing' and 'A minimal Jest unit test illustrating the key patterns this skill enforces.' The constraints section is useful but some items state things Claude already knows (e.g., don't use production data, mock external dependencies). | 2 / 3 |
Actionability | Provides a fully executable Jest code example with good/bad patterns clearly marked, specific assertion patterns, concrete framework references (Jest, pytest, k6), and actionable constraints with specific examples (e.g., `expect(result).toBe(90)` vs truthiness). The guidance is copy-paste ready and directly usable. | 3 / 3 |
Workflow Clarity | The 5-step core workflow is clearly sequenced with explicit validation checkpoints: step 4 includes failure classification and flaky test handling with feedback loops, and step 5 includes coverage verification before closing. The workflow handles error recovery paths explicitly. | 3 / 3 |
Progressive Disclosure | Excellent use of a reference table with 10 topic-specific files, each with clear 'Load When' conditions. The main skill provides a concise overview and quick-start example while deferring detailed guidance to one-level-deep references. Navigation is clear and well-signaled. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
3d95bb1
- 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.