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.
75
92%
Does it follow best practices?
Impact
—
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 testing/QA niche. The description is thorough without being padded, and uses proper 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 unlikely to conflict with non-testing 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 actionability, clear workflow sequencing with validation checkpoints, and excellent progressive disclosure through the reference table. The main weakness is minor verbosity in a few places—some descriptive phrases and parenthetical explanations could be trimmed without losing clarity. Overall, it's a high-quality skill that effectively guides Claude through testing tasks across multiple disciplines.
Suggestions
Trim the introductory sentence and the preamble before the code example ('A minimal Jest unit test illustrating the key patterns this skill enforces') to save tokens—the heading and code speak for themselves.
Remove parenthetical explanations in constraints that Claude already understands (e.g., '(e.g., don't test only the success branch of a try/catch)') to improve conciseness.
| 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 slightly verbose with parenthetical explanations Claude doesn't need (e.g., explaining what 'order-dependent' means). | 2 / 3 |
Actionability | Provides a fully executable Jest code example with both happy path and error case, specific assertion patterns, clear MUST DO/MUST NOT constraints, and concrete guidance on what good tests look like. The reference table gives specific tool contexts (k6, Supertest, pytest) making guidance directly applicable. | 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 as feedback loops, and step 5 includes coverage verification before closing. The workflow handles error recovery (fix root cause, re-run) and has explicit gates. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, quick-start example, and a well-organized reference table with 10 topic-specific files and clear 'Load When' conditions. References are one level deep and clearly signaled. Content is appropriately split between the overview and detailed reference files. | 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
e8be415
- 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.