CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

verification-ratchet

Use when implementing a requirement, writing tests, deriving property tests from a spec's candidate laws, running and triaging cargo-mutants results, or checking the CRAP complexity gate. Defines what counts as real verification and the only legal responses to failing checks, surviving mutants, and CRAPpy functions.

Quality

88%

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

85%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 an unusually actionable and well-sequenced verification workflow: exact commands, explicit validation checkpoints, error-recovery loops, and rigid triage rules for every check. Its main weaknesses are the monolithic single-file layout with dangling script references and occasional over-explanation of concepts Claude already knows.

Suggestions

Move the Layer 3/4 implementation detail (CRAP join rules, mutation-testing blind spots, the crap-report field rules) into reference files under references/ and keep one-line pointers in SKILL.md, so the main file stays a navigable overview.

Ship the referenced scripts (scripts/crap-report.bb, scripts/complexity-gate.bb, scripts/quality-gate.bb) in the bundle or remove/qualify the citations, since the commands currently point at files the skill does not provide.

Trim explanations of Rust fundamentals ('forbid (unlike deny)', 'Prefer NonZero*', enums-over-booleans) down to bare reminders, and tighten the greenfield 'how do you know it's right' digression to the pattern ranking itself.

DimensionReasoningScore

Conciseness

Mostly dense, field-earned guidance (the tmpfs overflow failure mode, fn-hash snapshot protection, line-range-overlap join) where every token earns its place, with only minor over-explanation of Rust basics ('forbid (unlike deny) cannot be overridden', 'Prefer NonZero*') and a somewhat editorial greenfield digression that could be trimmed.

4 / 5

Actionability

Fully executable throughout: copy-paste commands ('export TMPDIR="$HOME/.cache/cargo-mutants"', the fn-hash piped into 'cargo mutants --file {}', 'cargo llvm-cov nextest --workspace --json'), the exact CRAP formula, threshold 30, and concrete artifact formats like the REQ-ID comment placement.

5 / 5

Workflow Clarity

Layers are explicitly sequenced cheapest-first ('do first', 'After implementation is green', 'Run it after the mutation pass') with strong validation and recovery loops: the false-green 'unviable' mutants check against mutants.out/log with a re-run remedy, and failing properties route through minimize-then-fix-or-STOP with exhaustive legal/illegal triage outcomes.

5 / 5

Progressive Disclosure

Section headers (Layer 0–4, smells) navigate well, but ~250 lines of Layer 3/4 implementation detail (CRAP join rules, mutation blind spots) are inlined where reference files could carry them, and the cited scripts/crap-report.bb, scripts/complexity-gate.bb, and scripts/quality-gate.bb do not exist in the bundle.

3 / 5

Total

17

/

20

Passed

Description

88%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: it explicitly answers both what the skill does and when to use it, with concrete, domain-specific trigger phrases. Its only weaknesses are a few missing natural synonyms and broad opening triggers that could collide with closely related testing skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'deriving property tests from a spec's candidate laws, running and triaging cargo-mutants results, or checking the CRAP complexity gate' — plus the governance behaviors ('the only legal responses to failing checks, surviving mutants, and CRAPpy functions'), comprehensively covering the skill's scope with no gaps.

5 / 5

Completeness

Both halves are explicit: 'Use when implementing a requirement, writing tests, ... or checking the CRAP complexity gate' gives concrete trigger phrases for when, and 'Defines what counts as real verification and the only legal responses to failing checks, surviving mutants, and CRAPpy functions' states what.

5 / 5

Trigger Term Quality

Natural phrases like 'implementing a requirement', 'writing tests', 'property tests', 'cargo-mutants', and 'CRAP complexity gate' would plausibly appear in a user's request, but common synonyms such as 'mutation testing' or 'test strength' are missing.

4 / 5

Distinctiveness Conflict Risk

The cargo-mutants and CRAP-gate triggers occupy a clear niche, but the broad opening triggers 'implementing a requirement' and 'writing tests' risk overlap with the sibling TDD/testing skills the body itself references (tdd-cycle, testing-strategy).

4 / 5

Total

18

/

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

referenced_paths_exist

Referenced path issues: 2 possibly missing (scripts/crap-report.bb, scripts/quality-gate.bb)

Warning

Total

15

/

16

Passed

Repository

igouss/gitweb-rs

Path

.claude/skills/verification-ratchet/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.