writing-tests
Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.
100
Does it follow best practices?
Agent success when using this skill
Validation for skill structure
Discovery
100%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 excels across all dimensions. It clearly specifies the testing scope (unit, component, integration), names the exact tools (Vitest, React Testing Library), targets a specific project (AiderDesk), and provides explicit 'Use when' triggers covering common testing scenarios. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Write unit tests, component tests, and integration tests' and names specific tools 'Vitest and React Testing Library'. Also mentions concrete activities like 'configuring mocks, setting up test files, debugging failing tests'. | 3 / 3 |
Completeness | Clearly answers both what ('Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library') AND when ('Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'unit tests', 'component tests', 'integration tests', 'test coverage', 'mocks', 'test files', 'failing tests', 'Vitest'. These are terms developers naturally use when discussing testing. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to AiderDesk project testing with Vitest/React Testing Library. The combination of project name, specific testing frameworks, and test types creates a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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.
This is a well-crafted skill that exemplifies good documentation practices. It provides immediate actionability with the Quick Start example, maintains excellent token efficiency by deferring detailed content to reference files, and offers clear navigation to advanced topics. The debugging workflow includes explicit validation steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable code example in Quick Start, specific CLI commands for running tests, and concrete debugging steps. The code is copy-paste ready and the commands are specific. | 3 / 3 |
Workflow Clarity | The debugging section provides a clear numbered sequence with explicit steps. For a testing skill, the workflow from creation to running to debugging is well-structured with validation via coverage commands. | 3 / 3 |
Progressive Disclosure | Excellent structure with concise overview sections and well-signaled one-level-deep references to detailed materials. Core patterns link to specific reference files, and advanced usage clearly points to additional resources. | 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.
- 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.