CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-coverage-audit

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

62

Quality

72%

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

77%

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

The content is highly actionable with a clear, well-checkpointed workflow and concrete templates, but it is a long monolithic file with some redundancy across the caps, Red Flags, and Quick Reference sections. Splitting reference material into bundle files and trimming restatement would improve it.

Suggestions

Move the rating rubric, type/risk taxonomy, and ASCII diagram format into a references/ file to slim the main body and enable one-level-deep progressive disclosure.

Deduplicate the caps: the "Red Flags" table restates the 30-path and 20-test limits and the 2-minute cap already listed in "Caps and Limits"; keep them in one place.

Trim the "Quick Reference" section since it only restates the phase headings, or replace it with genuinely new callout content.

DimensionReasoningScore

Conciseness

The body mostly assumes Claude's competence without explaining basics, but the "Red Flags" table restates the caps, the "Quick Reference" restates the phases, and scattered WHY notes add mild padding that could be trimmed.

2 / 3

Actionability

Concrete, copy-paste-ready git/grep/find commands, markdown inventory and coverage-map templates, an ASCII diagram spec with exact fractions, and explicit caps make the guidance fully executable.

3 / 3

Workflow Clarity

A clear 4-phase sequence with numbered steps, explicit caps, a 2-minute "mark as needs manual review" checkpoint, and a Red Flags checklist provides explicit validation and error-recovery guidance.

3 / 3

Progressive Disclosure

No bundle files exist, so cross-skill pointers (skill-tdd, skill-verification-gate, codex-host-adapter.md) are not progressive-disclosure references for this skill; the ~245-line body is a self-contained monolith with sections but no content split into detail files.

2 / 3

Total

10

/

12

Passed

Description

67%

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 specific and explicit about both capability and trigger timing, but leans on technical jargon ("codepaths") and overlaps somewhat with broader code-review/testing skills. Tightening trigger phrasing toward natural user language would raise it.

Suggestions

Replace jargony "codepaths" with natural phrasing like "branches and code paths in your changes" so users are more likely to say it.

Add common trigger variations such as "test coverage", "untested code", or "reviewing a PR before merge".

Sharpen distinctiveness from generic code-review by emphasizing the test-generation output, e.g. "auto-generates missing tests for uncovered branches."

DimensionReasoningScore

Specificity

Names the domain (diffs/tests) and several concrete actions ("Trace codepaths in diffs, map against tests, auto-generate missing coverage"), but the jargony "codepaths" and a less comprehensive action enumeration fall short of the multi-specific 3-anchor example.

2 / 3

Completeness

Both "what" (trace/map/generate coverage) and "when" ("use before shipping PRs") are explicitly stated, with the latter serving as an explicit trigger clause equivalent to a "Use when..." guide.

3 / 3

Trigger Term Quality

"diffs", "tests", "coverage", and "before shipping PRs" include some natural trigger terms, but "codepaths" is technical jargon and common variations like "test coverage", "untested code", or "PR review" are missing.

2 / 3

Distinctiveness Conflict Risk

The diff-coverage-audit niche is reasonably distinct, but the "before shipping PRs" trigger and testing framing could overlap with generic code-review or testing skills.

2 / 3

Total

9

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nyldn/claude-octopus
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.