CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fix-regression-proof

Prove each fix with the five self-checks — tester test fails on base, passes on the fix, fails again with only the fix reverted, full suite and guards green, no protected files touched — plus fixer-owned extra tests, and save the evidence for the verifier. Use before handing any fix to the verifier.

77

Quality

97%

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

100%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 model of lean skill writing: a concrete, executable five-step proof checklist with an explicit feedback loop and a hard exit gate, plus actionable pointers for evidence generation and edge cases. No dimension shows a real weakness.

DimensionReasoningScore

Conciseness

Roughly 23 lines with zero padding: every line is a check, a concrete path, or a command, and nothing explains concepts Claude already knows. This matches anchor 5 ('lean and efficient; every token earns its place') and is clearly above anchor 4's 'minor instances of over-explanation'.

5 / 5

Actionability

Provides copy-paste-ready commands ('git diff --name-only base..head', 'tools/fix_loop.py') and concrete destinations ('fixer-tests/', 'evidence/<cluster>-selfcheck.json', TEST-DEFECT), covering the common cases with executable specifics — anchor 5 for an instruction-only skill per the scoring notes.

5 / 5

Workflow Clarity

A numbered five-proof checklist with an explicit error-recovery feedback loop ('If it still passes, the test doesn't exercise your fix; investigate before claiming') and an explicit validation gate ('any failure blocks handoff') — matching anchor 5's checklist, feedback loops, and checkpoints.

5 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no need for external references, and well-organized into 'Five proofs', 'Extra', and 'Exit criteria' sections; cross-skill pointers ('fix-reproduce', 'qa-independent-verification') are clearly signaled and one level deep. Per the judging guidelines this scores 5.

5 / 5

Total

20

/

20

Passed

Description

92%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 concretely enumerates the full five-proof procedure, explicitly states both what the skill does and when to use it, and occupies a distinct niche with low conflict risk. The only weakness is trigger-term coverage — natural synonyms like 'regression' and 'verify' appear in the skill name but not the description.

Suggestions

Include the word 'regression' (or 'prove the fix works') in the description itself, since it is the skill's core concept but currently only appears in the name.

Add one or two natural user phrasings (e.g., 'verify', 'validate') alongside the internal jargon ('tester test', 'fixer guards') so the trigger clause matches how the need would actually be voiced.

DimensionReasoningScore

Specificity

The description enumerates all five concrete checks plus extras ('fails on base', 'passes on the fix', 'fails again with only the fix reverted', 'full suite and guards green', 'no protected files touched', 'save the evidence') — comprehensive concrete coverage with no gaps, matching the anchor 5 rather than anchor 4's 'minor gaps'.

5 / 5

Completeness

Both parts are explicit: 'what' is the fully enumerated five-proof self-check procedure, and 'when' is stated concretely as 'Use before handing any fix to the verifier.' Anchor 4's caveat ('when could be more explicit') does not apply since the trigger condition is fully stated.

5 / 5

Trigger Term Quality

Good natural keywords for this workflow ('fix', 'self-checks', 'test', 'revert', 'verifier', 'handing', 'evidence'), but common variations a user would say are missing — notably 'regression' (present only in the name), 'verify', and 'validate'. This fits anchor 4 (good coverage, a few natural terms missing) rather than 3 (only some relevant keywords) or 5 (comprehensive synonyms).

4 / 5

Distinctiveness Conflict Risk

A clear niche (fixer-side pre-handoff self-check) with a distinct trigger clause and a distinctive five-check enumeration ('fails again with only the fix reverted') that no other skill would share; minimal conflict risk even against the closely related verifier counterpart skill.

5 / 5

Total

19

/

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

itsablabla/qa-bug-agent-skills

Path

skills/fix-regression-proof/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.