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.
95
93%
Does it follow best practices?
Impact
Pending
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 it does (writes various types of tests using specific frameworks for a specific project) and when to use it (with an explicit 'Use when' clause listing multiple trigger scenarios). It uses third person voice, includes natural trigger terms, and is distinctive enough to avoid conflicts with other skills.
| 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
87%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 that efficiently covers testing patterns for AiderDesk. Its strengths are excellent progressive disclosure with clearly labeled reference files and a concise, actionable quick start. The main weakness is the debugging workflow, which lists steps but lacks an explicit feedback loop (fix → re-run → verify pass).
Suggestions
Add an explicit feedback loop to the debugging section, e.g., after step 3: 'Fix the issue, re-run the failing test, and confirm it passes before moving on.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what Vitest or React Testing Library are, assumes Claude knows testing concepts, and every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides a fully executable code example in the quick start, concrete CLI commands for running tests and debugging, and specific file paths. The debugging section gives a clear, actionable sequence of steps. | 3 / 3 |
Workflow Clarity | The debugging section provides a reasonable sequence of steps, but there's no explicit validation/feedback loop (e.g., fix -> re-run -> verify). The overall workflow for creating tests is implied rather than explicitly sequenced with checkpoints. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and well-signaled one-level-deep references to detailed guides. Content is appropriately split between the main skill file and reference documents, with clear navigation labels. | 3 / 3 |
Total | 11 / 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
9bcd9bb
- 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.