CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

testing-strategy

Use when deciding WHAT kind of test a piece of code needs — before writing tests for a new module, when unsure whether something deserves a property test, an example test, a contract test, or an integration test, or when scoping where cargo-mutants should run. Maps test types onto hexagonal zones. The verification-ratchet skill defines HOW to write each kind; this skill defines WHERE each kind belongs.

Quality

85%

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

75%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-crafted instruction-only skill: it maps a complete decision space (four zones plus golden-master and greenfield variants) with concrete rules, named tools, and field-tested anti-patterns, while correctly deferring deep material to sibling skills. All dimensions land at 4 — the body is occasionally tightenable, a few operational details (running hex-lint, mutation-exclusion workflow) are referenced but not shown, and the structure could better integrate the cross-cutting determinism section.

Suggestions

Trim the field-incident narratives (Zone 2 OS-fallback story, the 11 smoke tests account, the byte-exact golden anecdote) to one-line justifications — the rule each supports is already convincing and the stories cost tokens.

Add the one or two commands a reader needs to act on the structural claims, e.g., how hex-lint is invoked against the zone table and where mutation-scope exclusions are recorded, since the skill leans on both as mechanical enforcement.

Move the determinism-injection list into the zone sections (or label it as a cross-zone checklist up front) so the zone-by-zone decision flow reads as one uninterrupted sequence.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — it never explains hexagonal architecture, proptest, or testcontainers from scratch, and packs rules like "Spec states an EXACT mapping ('100 at 10% → 90') → example test" into single lines. A few passages could be tightened (the Zone 2 data-types discussion and the field-incident narratives in the golden-master and vacuous-green sections), so it sits at anchor 4 rather than 5.

4 / 5

Actionability

For an instruction-only skill the guidance is concrete: a zone→hex-lint-role table, a four-rule example-vs-property decision list naming exact spec shapes, specific tools (testcontainers, wiremock, cargo-mutants, fail_on_skipped), and a concrete strategy fix ("build validity into the strategy (0u8..=100)"). Minor gaps — e.g., how to actually invoke hex-lint or where the zone table's gate runs — keep it below anchor 5.

4 / 5

Workflow Clarity

The decision process is coherently sequenced: identify the zone via the role table, apply that zone's test-type rules, then resolve example-vs-property with the explicit decision list, with anti-patterns as a final checklist. Some verification checkpoints exist (vacuous-green rules, 'a missing golden must panic, never skip'), but there is no single explicit step-by-step workflow with validation loops, matching anchor 4 rather than 5.

4 / 5

Progressive Disclosure

No bundle files exist, and the body handles depth correctly — the golden-parity section explicitly defers ('the full harness discipline... is the golden-parity skill; what follows is the placement summary') and cross-references (verification-ratchet, slice-workflow, tdd-cycle) are clearly signaled one level deep. Sections are well-organized with minor gaps (the determinism-injection list sits outside the zone sequence), fitting anchor 4 rather than the fully split-and-navigable anchor 5.

4 / 5

Total

16

/

20

Passed

Description

87%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 states a precise niche (what test type goes where), gives explicit 'Use when' triggers with natural terminology, and proactively disambiguates from the sibling verification-ratchet skill. The only weakness is slightly incomplete synonym coverage (e.g., 'unit test', 'test strategy') for trigger terms.

DimensionReasoningScore

Specificity

Names several concrete actions — "deciding WHAT kind of test a piece of code needs", "Maps test types onto hexagonal zones", "scoping where cargo-mutants should run" — with only minor coverage gaps. It falls short of anchor 5 because the actions are decision-guidance rather than a comprehensive list of concrete operations, but exceeds anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers both: what ("Maps test types onto hexagonal zones... this skill defines WHERE each kind belongs") and when ("Use when... before writing tests for a new module, when unsure whether something deserves a property test..."). Concrete trigger phrases match the anchor-5 example pattern exactly.

5 / 5

Trigger Term Quality

Includes natural phrases users would say: "property test, an example test, a contract test, or an integration test", "writing tests for a new module", "cargo-mutants". Not anchor 5 because common synonyms like "unit test", "test strategy", and "mutation testing" are absent; better than anchor 3 since coverage is genuinely good rather than partial.

4 / 5

Distinctiveness Conflict Risk

The explicit disambiguation — "The verification-ratchet skill defines HOW to write each kind; this skill defines WHERE each kind belongs" — plus a niche trigger set (test-type selection, cargo-mutants scoping) gives a clear niche with minimal conflict risk, matching anchor 5.

5 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

igouss/gitweb-rs

Path

.claude/skills/testing-strategy/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.