CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-coverage-audit

Trace codepaths in diffs, map against tests, auto-generate missing coverage — use before shipping PRs

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/skill-coverage-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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, highly actionable process skill: clear phased workflow with hard caps, concrete commands, worked output templates, and explicit anti-patterns. Its main weaknesses are a confusing, irrelevant opening paragraph, duplicated cap statements, and placeholder/slightly-broken search examples; validation of generated tests is delegated rather than inlined.

Suggestions

Delete the 'Artifact consistency before implementation' section — its seat/escalation jargon ('a clean pass costs no seat', 'at most one independent seat') has no role in the coverage workflow and wastes context.

Deduplicate the limits: the 'Red Flags' table repeats the 30-path, 20-test, and 2-minute caps already stated in 'Caps and Limits' — keep only the unique anti-pattern rows there.

Fix the search examples in Phase 2: replace the placeholder "grep -rl \"[function_name]\" tests/" (brackets form a regex character class) with a concrete, executable command, and show one fully substituted example.

Inline a run-tests → fix-failures → re-run loop at the end of Phase 4 instead of only delegating verification to skill-verification-gate, so generated tests are validated within the skill's own workflow.

DimensionReasoningScore

Conciseness

Most of the body is tight and prescriptive (commands, tables, output templates), but there is more than minor waste: the "Artifact consistency before implementation" paragraph is impenetrable policy jargon ("A single artifact skips analysis; a clean pass costs no seat", "Escalation uses at most one independent seat") unrelated to the coverage workflow, and the 30-path / 20-test / 2-minute caps from "Caps and Limits" are restated nearly verbatim in three Red Flags table rows. This fits anchor 3 (mostly efficient, some unnecessary explanation, could be tightened) better than anchor 4's 'minor instances that could be trimmed'.

3 / 5

Actionability

Phase 1 supplies copy-paste git commands and Phase 2 gives concrete find/grep searches, structured inventory/coverage-map templates with worked example rows, a star-rating rubric, and a conventions-detection checklist — mostly executable guidance. It misses anchor 5 because several search commands are unsubstituted placeholders and one is subtly wrong as written ("grep -rl \"[function_name]\" tests/" — the bracketed token is a regex character class, not a literal placeholder), which are minor gaps in executability.

4 / 5

Workflow Clarity

The sequence is explicit and well-ordered (TRACE → MAP → SCORE → DIAGRAM → GENERATE → REPORT, with per-phase steps, caps, and priority rules), and the batch test-generation phase does name a verification checkpoint ("use skill-verification-gate to run the test suite and confirm the new tests pass"), so the missing-validation cap of 3 does not apply. It stops short of anchor 5 because validation is delegated to another skill rather than inlined as a run → fix-failures → re-run feedback loop, and no checkpoint verifies the codepath inventory or coverage map itself.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent) and the skill is a single ~250-line file with clear section headers, an overview, and a Quick Reference that make navigation easy — most content is appropriately placed inline. It does not reach anchor 5 because the file is on the larger side and self-contained material that could live one level deep (e.g., the example inventory/coverage-map tables or the integration guide) is inlined, which is a minor organization gap rather than an ideal split.

4 / 5

Total

15

/

20

Passed

Description

75%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, third-person description with three concrete actions and an explicit when-clause, closely matching the rubric's good-example profile. It sits solidly at 4 across all dimensions: real and specific, but not comprehensive on trigger synonyms or fully disambiguated from neighboring code-review skills within the description field itself.

DimensionReasoningScore

Specificity

The description lists three concrete, well-specified actions — "Trace codepaths in diffs", "map against tests", "auto-generate missing coverage" — matching the anchor for several specific actions with minor gaps. It stops short of anchor 5 because the body's diagramming and before/after reporting phases are not represented, leaving minor gaps in coverage; it is clearly above anchor 3, which expects only 1-2 actions.

4 / 5

Completeness

Both parts are explicitly present: the "what" is "Trace codepaths in diffs, map against tests, auto-generate missing coverage" and the "when" is "use before shipping PRs", so the missing-trigger-clause cap of 3 does not apply. It falls short of anchor 5 because the when-clause is a single timing condition and lacks concrete user-mention trigger phrases (e.g., "when the user asks what is not tested"), matching anchor 4's 'when could be more explicit or specific'.

4 / 5

Trigger Term Quality

Relevant natural keywords are present — "codepaths", "diffs", "tests", "coverage", "shipping PRs" — a user asking about test coverage before a PR would plausibly match these. It fits anchor 4 (good keyword coverage, a few natural terms missing) rather than anchor 5, which expects synonyms and variations such as "untested code", "coverage gaps", or "test generation".

4 / 5

Distinctiveness Conflict Risk

The test-coverage niche (trace codepaths, map against tests, generate missing coverage) is distinct, but the description anchors on "diffs" and "shipping PRs", which are also natural triggers for generic code-review skills — indeed the frontmatter trigger block explicitly warns against activation for "Code review without coverage focus". This minor overlap with closely related skills matches anchor 4 rather than anchor 5's minimal-conflict profile.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

nyldn/claude-octopus

Path

.claude/skills/skill-coverage-audit/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.