testing-best-practices
Test layering, execution, and CI guidance across unit, integration, and e2e. Use when designing tests, writing test cases, or planning test strategy for a module.
81
72%
Does it follow best practices?
Impact
97%
1.64xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xbigboss/claude-code/testing-best-practices/SKILL.mdQuality
Discovery
67%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 competent description that covers the basics well, with a clear 'Use when' clause and relevant domain terminology. Its main weaknesses are the somewhat abstract capability descriptions (e.g., 'test layering' and 'execution' are not as concrete as they could be) and moderate trigger term coverage that misses common testing-related vocabulary users might employ.
Suggestions
Make capabilities more concrete by specifying actions like 'write unit tests, structure integration tests, configure e2e test suites, set up CI test pipelines'.
Expand trigger terms to include common variations like 'testing framework', 'test coverage', 'mocking', 'TDD', 'test suite', or specific tool names if applicable.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (testing) and mentions specific test types (unit, integration, e2e) and some actions (layering, execution, CI guidance), but the actions are somewhat abstract rather than concrete tasks like 'write unit tests' or 'configure CI pipelines'. | 2 / 3 |
Completeness | Clearly answers both 'what' (test layering, execution, and CI guidance across unit/integration/e2e) and 'when' (explicit 'Use when' clause covering designing tests, writing test cases, or planning test strategy for a module). | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'tests', 'test cases', 'test strategy', 'unit', 'integration', 'e2e', and 'CI', which users might naturally say. However, it misses common variations like 'testing framework', 'coverage', 'mocking', 'TDD', 'pytest', 'jest', or 'test suite'. | 2 / 3 |
Distinctiveness Conflict Risk | The testing domain is reasonably specific, but 'writing test cases' and 'designing tests' are broad enough that this could overlap with language-specific testing skills or CI/CD-focused skills. The mention of 'for a module' adds some specificity but is still somewhat generic. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill that provides comprehensive test strategy guidance with concrete templates, clear workflows, and explicit validation checkpoints. Its main weakness is that it's somewhat long for a single SKILL.md file—some sections could be tightened or split into supporting files. The hard rules and execution guidance sections are particularly valuable, though a few bullet points restate things Claude would already know.
Suggestions
Consider splitting detailed output format examples (test matrix, implementation plan templates) and CI lane configurations into separate referenced files to improve progressive disclosure and reduce the main file's token footprint.
Tighten the 'Hard rules' section by removing rules that restate general good engineering practice Claude already knows (e.g., 'Never weaken assertions to make tests pass', 'Never hard-code values matching test assertions').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-structured and avoids explaining basic concepts, but some sections are verbose for what they convey. For example, the 'Hard rules' section restates principles Claude already knows (like 'never weaken assertions to make tests pass'), and some bullet points could be tightened. The flake handling and async handling sections add value but could be more compact. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific test matrix formats with example rows, explicit case ID schemes, concrete output templates for strategy/matrix/implementation plan, specific CI lane configurations with time targets, and clear preflight check steps. The markdown output examples are copy-paste ready templates. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (spec → strategy → matrix → implementation → run → iterate) with explicit validation checkpoints: preflight checks before e2e, bounded retries with diagnostics on failure, flake classification before fixing, and the rule to never proceed without reading actual source. The feedback loop for missing cases is also well-defined. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and logical grouping, but it's a monolithic document with no references to supporting files. Given the length and breadth of topics (test layering, execution guidance, CI, output formats), some content like the detailed test matrix examples or CI lane configurations could be split into referenced files for better navigation. | 2 / 3 |
Total | 10 / 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
- NeverSight/skills_feed
- Commit
aa009ea
- 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.