CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

86%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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. Its main weakness is that the core patterns section delegates almost all actionable content to reference files, leaving the main body somewhat abstract for unit testing, component testing, and mocking. Adding a brief executable example for component testing and a more explicit test-writing workflow would strengthen it.

Suggestions

Add a brief executable component test example in the Component Testing section (even 3-4 lines) so the main skill body has actionable guidance for more than just unit tests.

Add an explicit workflow for writing new tests (e.g., 1. Create test file → 2. Write test → 3. Run `npm run test` → 4. Check coverage with `npm run test:coverage` → 5. Fix gaps) with validation checkpoints.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It assumes Claude knows what Vitest and React Testing Library are, doesn't explain basic testing concepts, and every section delivers actionable information without padding.

3 / 3

Actionability

The quick start provides a complete, executable example, and the debugging section has concrete commands. However, the core patterns sections (unit testing, component testing, mocking) are vague descriptions that defer all concrete guidance to reference files, leaving the main skill body light on executable specifics for those areas.

2 / 3

Workflow Clarity

The debugging section provides a clear numbered sequence, but there's no explicit validation/verification workflow for the primary task of writing tests. A feedback loop like 'write test → run → check coverage → fix' is only loosely implied rather than explicitly stated with checkpoints.

2 / 3

Progressive Disclosure

The skill is well-structured with a concise overview, quick start, and clearly signaled one-level-deep references to detailed materials. Navigation is easy with descriptive labels for each reference file, and content is appropriately split between the overview and reference documents.

3 / 3

Total

10

/

12

Passed

Description

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.

DimensionReasoningScore

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

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
hotovo/aider-desk
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.