CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-coverage-audit

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

61

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

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

The content is highly actionable with executable commands, concrete templates, and a clear multi-phase workflow supported by caps and fallbacks. It is well-structured for progressive disclosure, with the main gap being that explicit inline validation feedback loops for generated tests are delegated to a sibling skill.

Suggestions

Add an explicit validate-fix-retry loop inside Phase 4 (e.g., run the generated test, fix on failure, re-run) rather than only referencing skill-verification-gate, so the workflow stands alone.

Trim redundancy between the Quick Reference six-step list and the Phase headers, which restate the same sequence, to tighten the token budget.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands, tables, and tight step lists; it does not over-explain known concepts, though the Red Flags table and Integration sections add some redundancy with earlier caps/limits content.

4 / 5

Actionability

Provides copy-paste ready git/find/grep commands, concrete codepath inventory and coverage map templates, a quality rubric table, and explicit generation criteria covering the common cases fully.

5 / 5

Workflow Clarity

Four clearly sequenced phases with caps, a Quick Reference, and risk prioritization; the 2-minute cap and 'needs manual review' fallback act as checkpoints, but explicit validate->fix->retry feedback loops for the generated tests are only implicit via the verification-gate integration rather than inline.

4 / 5

Progressive Disclosure

Well-organized into Overview, Caps, four Phases, Integration, Red Flags, and Quick Reference with no bundle files needed; minor organization gaps (e.g., Quick Reference and Phase headings repeat the same six steps) keep it just below a 5.

4 / 5

Total

17

/

20

Passed

Description

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

The description is specific and action-oriented with a clear when-clause, performing well on specificity and distinctiveness. It loses points for trigger term breadth since the natural user phrases live in the separate trigger block rather than the description itself.

Suggestions

Fold 1-2 natural user phrases (e.g., 'test coverage' or 'coverage audit') into the description so trigger terms appear alongside the when-clause, reducing reliance on the separate trigger block.

Broaden the when-clause beyond 'before shipping PRs' to cover the main invocation contexts (e.g., 'Use when auditing test coverage or finding untested code before shipping PRs').

DimensionReasoningScore

Specificity

Lists three concrete actions ('Trace codepaths in diffs', 'map against tests', 'auto-generate missing coverage') with a clear timing directive, minor gaps in coverage but well above naming the domain alone.

4 / 5

Completeness

Has a clear 'what' (trace, map, generate) and a 'when' ('use before shipping PRs'); the 'when' is present but somewhat narrow and lacks explicit trigger phrases, keeping it below a 5.

4 / 5

Trigger Term Quality

Includes 'coverage' and 'tests' as relevant keywords plus 'shipping PRs', but the natural user phrases ('test coverage', 'coverage audit', 'what's not tested') only appear in the trigger block, not the description; common variations are missing.

3 / 5

Distinctiveness Conflict Risk

The niche (diff-based coverage auditing) is mostly distinct with minor overlap risk against general code-review or audit skills; conflict risk is low but not minimal given adjacent skills exist.

4 / 5

Total

15

/

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.

Validation15 / 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
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.