CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An exemplary lean, instruction-only skill body: fully sequenced workflow with explicit validation and feedback loops, concrete commands, and disciplined token efficiency. The only notable gap is the unspecified coverage tooling and test framework in steps 4–6, which presumably lives in the referenced testing doc.

DimensionReasoningScore

Conciseness

The ~30-line body is entirely directive with zero padding — no concept explanations, no restating what Claude already knows (e.g., "Load `verify` with your skill tool" assumes competence without elaboration). Every token earns its place, matching anchor 5.

5 / 5

Actionability

Concrete commands are given ("npx ai-devkit@latest lint --feature <name>", resolve ".ai-devkit.json" "paths.docs", falling back to "docs/ai") alongside specific test categories and context items. It falls short of anchor 5 only because "Run coverage tooling" and the test framework are left unspecified — minor gaps in otherwise executable guidance.

4 / 5

Workflow Clarity

The sequence is explicit with validation checkpoints (lint pre-check, coverage gap identification) and feedback loops for error recovery ("suggest additional tests if below the target"; "If tests reveal design flaws, return to `dev-design`"). This matches anchor 5 rather than 4, which would require missing checkpoints.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external reference files (none exist in the bundle), and its content is organized into clear sections (Phase Contract, Write Tests) with one-level-deep cross-skill navigation (`verify`, `task`, `dev-review`, `dev-design`). This qualifies for 5 under the simple-skill guideline.

5 / 5

Total

19

/

20

Passed

Description

83%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 that clearly states both capability and explicit trigger conditions with concrete, natural phrases. Its main weaknesses are minor: a few missing common trigger synonyms (unit tests, test suite) and generic testing terms that could overlap with non-DevKit testing requests.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("write tests, update testing docs, run coverage, close coverage gaps") tied to a named domain, but coverage is not comprehensive — the scope of testing work (unit, integration, edge cases) is only detailed in the body. It fits anchor 4 (several specific actions, minor gaps) rather than 5.

4 / 5

Completeness

It explicitly answers both "what" ("Testing phase guidance for adding and validating feature test coverage") and "when" ("Use when the user wants to write tests, update testing docs, run coverage, close coverage gaps, or run dev-lifecycle phase 8") with concrete trigger phrases, matching anchor 5. It is not 4 because the when-clause is fully explicit rather than needing more specificity.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ("write tests", "run coverage", "close coverage gaps"), but common variations like "unit tests", "test suite", or "run the tests" are missing. Good coverage with a few natural terms absent matches anchor 4, not 5.

4 / 5

Distinctiveness Conflict Risk

Scoping via "AI DevKit" and "dev-lifecycle phase 8" gives it a clear niche, but generic triggers like "write tests" and "run coverage" overlap with general testing skills. Mostly distinct with minor overlap risk matches anchor 4; it is not 3 because the domain qualifiers meaningfully reduce confusion.

4 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

codeaholicguy/ai-devkit

Path

skills/dev-testing/SKILL.md

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.