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
Quality
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 follows the correct structure with an explicit 'Use when...' clause. Its main weaknesses are the somewhat abstract capability statement and limited trigger term coverage. The description would benefit from more concrete actions and additional natural keywords users might use when seeking testing help.
Suggestions
Expand trigger terms to include common variations like 'testing', 'TDD', 'test coverage', 'mocking', or specific framework names users might mention.
Make capabilities more concrete by listing specific actions like 'write unit tests, configure test runners, set up CI pipelines, create test fixtures'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (testing) and mentions some actions ('designing tests, writing test cases, planning test strategy'), but the capabilities section ('Test layering, execution, and CI guidance') is somewhat abstract rather than listing concrete specific actions like 'create unit tests' or 'configure CI pipelines'. | 2 / 3 |
Completeness | Clearly answers both what ('Test layering, execution, and CI guidance across unit, integration, and e2e') and when ('Use when designing tests, writing test cases, or planning test strategy for a module') with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'tests', 'test cases', 'test strategy', 'unit', 'integration', 'e2e', and 'CI', but missing common variations users might say like 'testing', 'TDD', 'coverage', 'mocking', 'pytest', 'jest', or 'automated tests'. | 2 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to testing domain with mentions of unit/integration/e2e and CI, but could potentially overlap with general coding skills or CI/CD-specific skills; the 'module' scope helps but isn't highly distinctive. | 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 with excellent workflow clarity and concrete output templates. The main weaknesses are moderate verbosity (some redundant explanations and repeated concepts) and a monolithic structure that could benefit from progressive disclosure via linked reference files. The hard rules and execution guidance sections are particularly well-crafted.
Suggestions
Extract the detailed output format templates (test strategy, test matrix, implementation plan) into a separate TEMPLATES.md file and reference it
Consolidate redundant guidance about async handling and flake prevention that appears in multiple sections
Remove 'Purpose:' explanations for each test layer - Claude understands what unit/integration/e2e tests are for
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant explanations (e.g., 'Purpose:' statements that Claude would infer). The hard rules section repeats concepts that could be consolidated, and some guidance like 'never use fixed sleep' is stated multiple times across sections. | 2 / 3 |
Actionability | Provides highly concrete, executable guidance with specific commands, markdown templates for outputs, case ID schemes, and explicit CI lane configurations. The test matrix format and implementation plan templates are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear multi-step workflow at the end (spec → strategy → matrix → implementation → tests). Preflight checks section provides explicit validation steps. The CI guidance includes clear sequencing for PR vs nightly lanes with specific targets. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but it's a monolithic document that could benefit from splitting detailed guidance (e.g., CI configuration, output format templates) into separate reference files. No external file references are provided. | 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
5342bca
- 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.