Design test strategy using Beck's Test Desiderata — which properties matter, which tradeoffs to make. Use when the user asks "how should I test this", "what tests do I need", "review my test strategy", "is this well-tested", or when planning tests for a new feature or refactor.
96
Quality
95%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 strong description with excellent trigger terms and completeness. The explicit 'Use when' clause with multiple natural phrases makes it highly discoverable. The main weakness is that the capabilities could be more concrete—it describes the framework used but not the specific outputs or actions Claude will perform.
Suggestions
Add 1-2 concrete actions to improve specificity, e.g., 'Analyzes test coverage, recommends test types, identifies missing test properties using Beck's Test Desiderata'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (test strategy) and references a specific framework (Beck's Test Desiderata), mentions 'properties' and 'tradeoffs', but doesn't list concrete actions like 'analyze coverage gaps', 'recommend test types', or 'evaluate test isolation'. | 2 / 3 |
Completeness | Clearly answers both what (design test strategy using Beck's Test Desiderata, determine which properties matter and tradeoffs) AND when (explicit 'Use when' clause with multiple trigger phrases and contexts). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural phrases users would say: 'how should I test this', 'what tests do I need', 'review my test strategy', 'is this well-tested', plus contexts like 'planning tests for a new feature or refactor'. | 3 / 3 |
Distinctiveness Conflict Risk | The reference to 'Beck's Test Desiderata' creates a clear niche distinct from generic testing skills. The specific trigger phrases about test strategy and planning differentiate it from skills about writing tests or debugging. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
Excellent skill content that exemplifies good design. The Beck's Desiderata table provides dense, actionable reference material. Strategy templates are copy-paste ready with clear structure. The content respects Claude's intelligence while providing genuinely useful frameworks and checklists that add value beyond what Claude would generate unprompted.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely efficient use of tokens. Tables compress information effectively, no explanation of concepts Claude already knows (testing basics, what properties mean). Every section earns its place with actionable content. | 3 / 3 |
Actionability | Provides concrete strategy templates with checkboxes, specific questions to ask, clear workflow steps, and ready-to-use output formats. The test smells table gives specific symptoms and fixes rather than vague guidance. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit sequencing (Articulate Contract → Identify Boundaries → Choose Approach → Apply Trophy → Evaluate). Each step has concrete sub-questions or criteria. The final 'Confidence Question' serves as a validation checkpoint. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear references to external files (references/desiderata.md, skills/FRAMEWORKS.md, RECIPE.md). Content appropriately split between quick-reference tables inline and detailed guidance in referenced files. One level deep. | 3 / 3 |
Total | 12 / 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.
96a72fa
Table of Contents
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.