testing-strategies
Design comprehensive testing strategies for software quality assurance. Use when planning test coverage, implementing test pyramids, or setting up testing infrastructure. Handles unit testing, integration testing, E2E testing, TDD, and testing best practices.
84
78%
Does it follow best practices?
Impact
96%
1.14xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent-skills/testing-strategies/SKILL.mdQuality
Discovery
92%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 capabilities and includes explicit 'Use when' triggers with natural terminology. The description uses proper third-person voice and covers the testing domain comprehensively. Minor weakness is potential overlap with more specialized testing skills due to its broad scope.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'planning test coverage', 'implementing test pyramids', 'setting up testing infrastructure', and explicitly names testing types (unit, integration, E2E, TDD). | 3 / 3 |
Completeness | Clearly answers both what ('Design comprehensive testing strategies') and when ('Use when planning test coverage, implementing test pyramids, or setting up testing infrastructure') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'testing', 'test coverage', 'test pyramids', 'unit testing', 'integration testing', 'E2E testing', 'TDD', 'testing best practices' - all common phrases developers use. | 3 / 3 |
Distinctiveness Conflict Risk | While testing-focused, could potentially overlap with language-specific testing skills or CI/CD skills. The broad scope ('comprehensive testing strategies') may conflict with more specialized testing skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides strong, actionable code examples for multiple testing types (unit, integration, E2E, TDD) that are immediately executable. However, it suffers from some verbosity with unnecessary metadata, empty placeholder sections, and explanations of concepts Claude already knows. The workflow lacks validation checkpoints for iterating on test quality or handling failures.
Suggestions
Remove the metadata section (version, tags, related skills) and empty example placeholders - these add no actionable value
Add validation checkpoints to the workflow, such as 'Run coverage report and verify targets are met before proceeding' or 'If tests fail, check X before Y'
Consider splitting detailed code examples for each testing type into separate reference files (UNIT_TESTING.md, E2E_TESTING.md) with SKILL.md as a concise overview
Remove explanations of basic concepts like the test pyramid rationale and AAA pattern definition - Claude already knows these
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elements like the metadata section with version info, empty example placeholders, and explanations of concepts Claude already knows (e.g., what the test pyramid is, basic AAA pattern). The ASCII art pyramid is nice but the ratio guide could be more compact. | 2 / 3 |
Actionability | Excellent executable code examples throughout - TypeScript unit tests with Jest, integration tests with Supertest, E2E tests with Playwright, and TDD examples. All code is copy-paste ready with realistic scenarios like user registration and discount calculation. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced (Steps 1-5), but there are no validation checkpoints or feedback loops. For a testing strategy skill, there should be guidance on what to do when tests fail, how to verify coverage goals are met, or how to iterate on test quality. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but it's somewhat monolithic - all testing types are inline rather than split into separate reference files. The references section links to external resources but the 'Related skills' and empty example sections suggest incomplete organization. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- supercent-io/skills-template
- Commit
c033769
- 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.