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.
77
64%
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 slightly abstract capability descriptions (e.g., 'test layering' and 'execution' rather than concrete actions) and moderate trigger term coverage that misses common testing-related vocabulary users might employ.
Suggestions
Replace abstract terms like 'test layering' and 'execution' with more concrete actions such as 'write unit tests, configure integration test fixtures, set up e2e test workflows, and define CI pipeline test stages'.
Expand trigger terms to include common variations like 'test suite', 'coverage', 'mocking', 'TDD', 'test runner', or specific frameworks users might mention.
| 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
62%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 testing strategy skill with clear workflows and good organizational hierarchy. Its main weaknesses are the lack of executable code examples (ironic for a test-writing skill) and some verbosity in explaining testing concepts Claude already understands. The output format templates are a strong point, providing clear deliverable structures.
Suggestions
Add at least one executable test code example (e.g., a parameterized unit test in Python/TypeScript) to demonstrate the expected output quality, rather than only showing markdown templates.
Trim sections that explain standard testing concepts Claude already knows (e.g., the 'Purpose:' lines for each test layer, general async handling advice) to improve token efficiency.
Consider splitting execution guidance and CI guidance into separate referenced files to keep the main SKILL.md focused on the core decision-making workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and covers a lot of ground, but includes some guidance Claude already knows (e.g., explaining what unit/integration/e2e tests are for, general async handling patterns, basic fixture advice). Some sections like 'Async handling' and 'Flake handling' contain standard testing wisdom that doesn't need to be spelled out. | 2 / 3 |
Actionability | The skill provides structured guidance with concrete output templates (test strategy, test matrix, implementation plan) and specific rules, but lacks executable code examples. The test matrix example is helpful but is a template rather than a real executable test. No actual test code in any language is provided despite the skill being about writing tests. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced: API surface discovery → test strategy → test matrix → implementation plan → CI integration. Preflight checks before e2e provide explicit validation steps. The overall 5-step workflow at the end ties everything together with clear sequencing and feedback loops (step 5: propose missing cases before editing specs). | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear headers and logical sections, but it's a long monolithic document (~150 lines) with no references to external files for detailed content. The CI guidance, execution guidance, and test layering policy sections could each be separate referenced documents to keep the main skill leaner. | 2 / 3 |
Total | 9 / 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
e437c3c
- 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.