CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-coverage

Use after writing tests to assess coverage quality across structural, mutation, requirements, and API/integration dimensions; organized knowledge for choosing and interpreting coverage analyses.

Quality

70%

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 ./antigravity/skills/test-coverage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 body is a rich, accurate, well-organized knowledge reference with genuinely strong decision-support content, but it is delivered as a monolithic ~600-line SKILL.md instead of an overview plus one-level-deep reference files, and it spends many tokens re-teaching coverage fundamentals Claude already knows. Offloading per-type details and the sources list into references/ would fix both weaknesses at once.

Suggestions

Move the per-type detail sections (Structural, Mutation, Requirements, API/Integration, Additional Types), the regulated-standards tables, and the Sources list into references/ files (e.g., references/structural.md, references/mutation.md, references/standards.md), keeping SKILL.md as a concise overview with the decision tables and clearly signaled one-level-deep links.

Cut re-explanations of fundamentals Claude already knows — the line/branch/condition coverage definitions, the repeated `A && B` compound-condition example (it appears in the Condition Coverage, Branch Coverage, and worked-example sections), and the basic what-is-mutation-testing prose — keeping only the non-obvious interpretation guidance.

Replace the ~70-line Sources & Further Reading section (which duplicates nearly every link already cited inline) with a single short list or a references/sources.md file.

DimensionReasoningScore

Conciseness

The ~630-line body re-explains concepts Claude already knows (line/branch/condition coverage definitions, the compound-condition `A && B` example repeated across multiple sections, what mutation testing is) and ends with a ~70-line Sources section that duplicates nearly every inline link. Much of the curated content (thresholds, standards, gaming patterns) is genuinely non-obvious, keeping it above anchor 1's pure padding.

2 / 5

Actionability

Concrete guidance throughout: named tools per ecosystem, runnable flags (`go test -cover`, coverage.py branch mode, `--coverage`), Stryker config defaults (`high: 80`, `low: 60`, `break`), the mutation-score formula, and decision tables with an explicit "read the row that matches your artifact" instruction. Not anchor 5 because most tool entries are names/links rather than copy-paste-ready invocations.

4 / 5

Workflow Clarity

For a non-procedural reference it navigates clearly: a consistent six-sub-field structure per coverage type ("Scan any section by these headings"), use-vs-skip heuristics, a sequenced layered stack, and lookup tables. No validation checkpoints are needed since the skill involves no destructive or batch operations, so the cap-at-3 rule does not apply.

4 / 5

Progressive Disclosure

The entire reference manual — per-type detail sections, ecosystem tool tables, regulated-standards tables, and the sources list — is inlined in SKILL.md with no references/ directory at all, matching anchor 2's "content that clearly belongs in separate files is inlined". Good internal section organization keeps it above anchor 1, but there is zero file-level disclosure.

2 / 5

Total

12

/

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 well-formed description that clearly names the domain, enumerates the four coverage dimensions, and includes an explicit trigger clause. It is a polish away from excellent: broader trigger phrasing and a boundary clause against test-strategy skills would close the remaining gaps.

DimensionReasoningScore

Specificity

Enumerates four concrete coverage dimensions ("structural, mutation, requirements, and API/integration") and specific actions ("assess coverage quality", "choosing and interpreting coverage analyses"), with minor gaps since no concrete analysis techniques or tools are named. It lists several specific capabilities but is a notch below anchor 5's fully concrete action inventory.

4 / 5

Completeness

Has both a clear "what" (assess coverage quality across four dimensions; organized knowledge for choosing and interpreting analyses) and an explicit "when" ("Use after writing tests"), so the cap-at-3 rule does not apply. Not anchor 5 because the trigger clause is a single state without concrete trigger phrases for adjacent moments (e.g., "when asked about coverage numbers, mutation scores, or which coverage tool to use").

4 / 5

Trigger Term Quality

Includes natural terms users would say — "writing tests", "coverage", "mutation", "API/integration" — but misses common variations like "code coverage", "branch coverage", "test quality", or tool names. Good keyword coverage with a few natural terms missing matches anchor 4.

4 / 5

Distinctiveness Conflict Risk

The coverage-analysis niche has fairly distinct, domain-specific triggers, giving minimal conflict risk with unrelated skills. Minor overlap risk remains with a general test-writing/test-strategy skill, which the description does not disambiguate even though the body explicitly defers to `design-testing-strategy`.

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

skill_md_line_count

SKILL.md is long (639 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

NeoLabHQ/context-engineering-kit

Path

antigravity/skills/test-coverage/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.