test-quality-analysis
Detect test smells, overmocking, flaky tests, and coverage issues. Analyze test effectiveness, maintainability, and reliability. Use when reviewing tests or improving test quality.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill test-quality-analysis89
Quality
86%
Does it follow best practices?
Impact
96%
1.07xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/test-quality-analysis/skills/test-quality-analysis/SKILL.mdDiscovery
85%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 well-crafted skill description that clearly articulates specific capabilities and includes explicit 'Use when' guidance. The description uses proper third-person voice and lists concrete, actionable items. The main weakness is trigger term coverage could be expanded to include more common user phrasings.
Suggestions
Expand trigger terms to include common variations like 'unit tests', 'test suite', 'specs', or 'testing problems' that users might naturally say
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Detect test smells, overmocking, flaky tests, and coverage issues' and 'Analyze test effectiveness, maintainability, and reliability' - these are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Detect test smells, overmocking, flaky tests...Analyze test effectiveness') AND when ('Use when reviewing tests or improving test quality') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'test smells', 'flaky tests', 'coverage', 'test quality', but missing common variations users might say like 'unit tests', 'test suite', 'testing', 'specs', or file extensions like '.test.js'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on test quality analysis with distinct triggers like 'test smells', 'overmocking', 'flaky tests' - unlikely to conflict with general code review or other testing skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently covers test quality analysis with concrete, executable examples and clear anti-pattern demonstrations. The content is well-structured with appropriate use of checklists and code comparisons. The main weakness is the lack of an explicit workflow for conducting a test quality analysis session with validation steps.
Suggestions
Add a 'Test Quality Analysis Workflow' section with explicit steps: 1) Run coverage analysis, 2) Identify gaps/smells, 3) Prioritize fixes, 4) Verify improvements with re-run
Include validation checkpoints in the workflow, such as 'coverage threshold met' or 'no new flaky tests detected' before considering analysis complete
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using code examples to illustrate points rather than verbose explanations. It assumes Claude understands testing concepts and doesn't over-explain basics like what mocking is. | 3 / 3 |
Actionability | Provides fully executable code examples in TypeScript/JavaScript with clear bad/good comparisons. Commands for coverage tools are copy-paste ready with specific flags and output paths. | 3 / 3 |
Workflow Clarity | The skill provides checklists and patterns but lacks explicit multi-step workflows with validation checkpoints. For test analysis tasks, there's no clear sequence like 'run coverage → identify gaps → fix → verify improvement'. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from core concepts to specific smells to tools to checklists. References to related skills (vitest-testing, playwright-testing, mutation-testing) are clearly signaled at the end. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 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.