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.
The description is functional and covers both what the skill does and when to use it, which is its strongest aspect. However, the capability descriptions are somewhat abstract ('test layering', 'execution', 'CI guidance') rather than listing concrete actions, and the trigger terms could be expanded to cover more natural user phrasings. The description would benefit from more specific actions and additional trigger keywords.
Suggestions
Replace abstract terms like 'test layering' and 'execution' with concrete actions such as 'write unit tests, design integration test suites, configure e2e test pipelines, set up CI test workflows'.
Expand trigger terms to include common variations users might say, such as 'testing framework', 'test coverage', 'mocking', 'TDD', 'test runner', or specific tools.
| 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 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 focus is reasonably specific, but 'writing test cases' and 'designing tests' are broad enough that they could overlap with language-specific testing skills or CI/CD-focused skills. The phrase '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 solid, comprehensive testing skill with strong actionability and clear workflows. Its main weakness is length — it packs a lot of content into a single file that could benefit from splitting detailed execution guidance and CI configuration into referenced sub-files. Some sections explain standard testing concepts that Claude already understands, slightly reducing token efficiency.
Suggestions
Consider splitting 'Execution guidance' (preflight, fixtures, async, flake handling) and 'CI guidance' into separate referenced files to improve progressive disclosure and reduce the main skill's token footprint.
Trim explanatory 'Purpose:' lines from test layer definitions — Claude knows what unit/integration/e2e tests are. Keep only the specific policies and constraints unique to this project's approach.
| 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 could be trimmed. | 2 / 3 |
Actionability | The skill provides concrete, actionable output formats with specific markdown templates for test strategy, test matrix with example rows, and implementation plans. The hard rules are specific and unambiguous. The preflight checks, CI lane definitions, and case ID scheme are all directly usable. | 3 / 3 |
Workflow Clarity | The workflow section at the end clearly sequences the overall process (spec → strategy → matrix → plan → code → iterate). Preflight checks provide explicit validation steps before e2e runs. The flake handling includes a clear feedback loop (retry → diagnose → classify → fix). CI guidance separates fast and nightly lanes with clear scope. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, but it's a fairly long monolithic document (~150 lines of substantive content). The detailed test layering policies, execution guidance, and CI guidance could be split into referenced sub-files. No external references are provided for deeper dives on any topic. | 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
f772de4
- 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.