Tessl • The management layer for AI agent skills

SkillPublic

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.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured skill body: lean, executable, and cleanly split across existing reference files. The inline example is deliberately minimal, which slightly limits standalone actionability, and the debugging workflow stops short of an explicit retry loop.

Suggestions

Add a short inline component-test example (render + interaction with React Testing Library) so the two most common cases are usable without opening references.

Close the debugging loop with an explicit step such as "Fix the issue and re-run the isolated test until it passes".

Add a pre-flight "verify your new test runs in isolation" checkpoint to the test-creation workflow, mirroring the assets/test-checklist.md guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence: no explanation of what Vitest or React Testing Library are, no padded sections — every line instructs ("Run tests with `npm run test`"). Not 4: there is nothing left to trim; each token earns its place.	5 / 5
Actionability	Provides a copy-paste-ready Vitest example and exact commands (`npm run test`, `npm run test:node -- --no-color -t "test name"`, `npm run test:coverage`). Not 5: only a trivial `add(1, 2)` unit example is inline; component and integration examples are delegated to reference files, leaving minor gaps in the common cases.	4 / 5
Workflow Clarity	The debugging section is a clear 5-step sequence with concrete checkpoints (isolate a single test, verify coverage). Not 5: there is no explicit fix-and-re-run feedback loop closing the sequence; not 3: checkpoints are concrete and present, not merely implied.	4 / 5
Progressive Disclosure	A concise overview with well-signaled, one-level-deep references, each annotated ("references/mocking-guide.md - Mock factories and API patterns"), and every referenced file exists in references/ and assets/. Matches the top anchor: easy navigation, content appropriately split.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states what the skill does with named tools and project, and when to use it via an explicit, natural trigger list. The only weakness is missing synonym/extension coverage (e.g., .test.ts, specs) that would make triggering bulletproof.

Suggestions

Add file-extension and synonym triggers such as ".test.ts", "test files", or "test suites" to broaden natural keyword coverage.

Consider mentioning coverage reporting or CI test runs as explicit capabilities if the skill supports them.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions ("Write unit tests, component tests, and integration tests") with named tooling (Vitest, React Testing Library) and target project (AiderDesk), covering the domain comprehensively. Not 4: there are no material gaps — the full test-level spectrum plus the stack is explicitly stated.	5 / 5
Completeness	Clearly answers both "what" (write unit/component/integration tests for AiderDesk with Vitest and React Testing Library) and "when" via an explicit "Use when..." clause with five concrete trigger phrases. Matches the top anchor's structure directly; not 4 because the when-clause is already explicit and specific.	5 / 5
Trigger Term Quality	Triggers like "creating new tests", "adding test coverage", "configuring mocks", and "debugging failing tests" are natural phrases users would say. Not 5: it lacks synonyms and file extensions (e.g., ".test.ts", "specs", "test suites") that the top anchor requires.	4 / 5
Distinctiveness Conflict Risk	Pinned to a specific project (AiderDesk) and specific frameworks (Vitest, React Testing Library), giving it a clear niche with distinct triggers and minimal conflict risk against generic testing skills. Not 4: the project and stack names remove even minor overlap ambiguity.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: hotovo/aider-desk
Path: .aider-desk/skills/writing-tests/SKILL.md
Revision: 980f390

Reviewed: 1 month ago

Discovery Implementation Validation

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.

writing-tests

Table of Contents

Is this your skill?