dev-testing

AI DevKit · Testing phase guidance for adding and validating feature test coverage. Use when the user wants to write tests, update testing docs, run coverage, close coverage gaps, or run dev-lifecycle phase 8.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%Weight 40%Scale 1-3

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

The body is a tight, well-sequenced instruction skill with concrete commands, explicit validation checkpoints, and a feedback loop back to design. As a simple single-purpose instruction skill it hits the strong anchor across all dimensions.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations or filler; every line is actionable instruction that assumes Claude's competence, matching the score-3 'lean and efficient' anchor.	3 / 3
Actionability	Concrete commands ('npx ai-devkit@latest lint --feature <name>'), explicit path resolution ('.ai-devkit.json paths.docs, falling back to docs/ai'), and specific test-type guidance make this copy-paste-ready actionable instruction.	3 / 3
Workflow Clarity	A clear 8-step sequence with a pre-work lint checkpoint (step 1), a verification checkpoint ('Apply the verify skill before making coverage or test-pass claims'), and an explicit error-recovery feedback loop ('If tests reveal design flaws, return to dev-design').	3 / 3
Progressive Disclosure	Under 50 lines with no bundle files and well-organized sections (Phase Contract, Write Tests, Next); per the simple-skills scoring note this earns a 3 with clear organization alone.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

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

The description is concise, concrete, and clearly states both what the skill does and when to use it, with an explicit 'Use when...' trigger and a distinct dev-lifecycle niche. It matches the strong anchor examples across all four dimensions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'adding and validating feature test coverage', 'write tests, update testing docs, run coverage, close coverage gaps' — matching the score-3 anchor rather than the narrower score-2 anchor.	3 / 3
Completeness	Explicitly answers both what ('Testing phase guidance for adding and validating feature test coverage') and when (an explicit 'Use when the user wants to...' clause), satisfying the score-3 anchor with a present trigger clause.	3 / 3
Trigger Term Quality	Natural trigger phrases a user would say ('write tests', 'run coverage', 'close coverage gaps', 'update testing docs') give good coverage; the internal 'dev-lifecycle phase 8' is minor jargon but the rest are common user phrasings.	3 / 3
Distinctiveness Conflict Risk	Scoped to 'AI DevKit · Testing phase' / 'dev-lifecycle phase 8', a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: codeaholicguy/ai-devkit
Path: skills/dev-testing/SKILL.md
Commit: 15b09d2

Reviewed: 12 days ago

Table of Contents

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.