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.
71
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
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 strong skill description that clearly communicates what the skill does (writes various types of tests using specific frameworks for a specific project) and when to use it (with an explicit 'Use when' clause covering multiple trigger scenarios). The description is concise, uses third person voice, and includes natural trigger terms that users would actually say when needing testing help.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Write unit tests, component tests, and integration tests' and names specific tools (Vitest, React Testing Library). Also mentions configuring mocks, setting up test files, and debugging failing tests. | 3 / 3 |
Completeness | Clearly answers both 'what' (write unit/component/integration tests using Vitest and React Testing Library) and 'when' (explicit 'Use when' clause covering creating tests, adding coverage, configuring mocks, setting up test files, debugging failing tests). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'unit tests', 'component tests', 'integration tests', 'Vitest', 'React Testing Library', 'test coverage', 'mocks', 'test files', 'failing tests'. These cover a wide range of natural user queries about testing. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the combination of project-specific scope (AiderDesk), specific frameworks (Vitest, React Testing Library), and clear testing focus. Unlikely to conflict with other skills unless there are multiple testing skills for the same project. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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-structured skill with excellent progressive disclosure and conciseness. The main weakness is that the core patterns sections are too abstract in the SKILL.md itself—they describe what to do but delegate all concrete examples and executable guidance to reference files that weren't provided. The debugging workflow could benefit from more explicit validation checkpoints.
Suggestions
Add a brief executable code snippet for component testing and mocking directly in the SKILL.md (even 3-4 lines each) so Claude has actionable patterns without needing to read reference files.
Add a clear end-to-end workflow for writing a new test: create file → write test → run → check output → verify coverage, with explicit validation steps between stages.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what Vitest or React Testing Library are, assumes Claude knows how testing frameworks work, and every section delivers actionable information without padding. | 3 / 3 |
Actionability | The quick start provides a complete, executable test example and concrete CLI commands. However, the core patterns sections (unit testing, component testing, mocking) are vague descriptions that delegate all concrete guidance to reference files, and the debugging section is mostly general advice rather than specific executable steps. | 2 / 3 |
Workflow Clarity | The debugging section provides a reasonable sequence of steps, but lacks explicit validation checkpoints or feedback loops. There's no clear workflow for the primary task of writing tests (e.g., create file → write test → run → verify coverage → fix). The steps are more like tips than a structured workflow. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and quick start at the top, core patterns with one-level-deep references to specific guides, and an advanced section with clearly labeled reference files. Navigation is well-signaled and organized for discovery. | 3 / 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
- hotovo/aider-desk
- Commit
e82a91f
- 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.