Skill repair loop
Reusable Claude Skills, evals, and repair loops for turning giant prompts into compounding AI workflows.
npx -y skills add Arnie016/fable-mythos --skill skill-repair-loopAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Repairs a Claude Skill after a bad output by identifying the exact failure, patching SKILL.md, and adding a regression test. Use when a skill output is generic, wrong, overhyped, off-format, or fails the user's expectations.
SKILL.md
2.1 KB, as published. Nobody here has run it
Skill Repair Loop
Mission
Improve a Claude Skill based on a real failed output. Do not rewrite the whole skill unless necessary — patch the smallest instruction that would have prevented the failure.
Required input
- The current SKILL.md
- The bad output
- What was wrong with it (infer from the output if unstated)
If the bad output itself is missing, ask for it. You cannot diagnose a failure you haven't seen — do not repair from a description alone.
Workflow
- Classify the failure:
- Trigger failure — skill didn't fire, or fired wrongly (fix: description)
- Format failure — wrong sections/structure (fix: output format)
- Voice failure — generic or off-tone (fix: examples file, not more adjectives)
- Reasoning failure — wrong angle, bad judgment (fix: workflow step)
- Overclaiming — invented facts/hype (fix: hard constraint)
- Missing constraint — did something the skill never forbade
- Capability gap — the executor model can't follow the instruction as written (fix: simplify it or replace prose with a worked example — do NOT add more prose)
- Instruction bloat — the skill is so long the model skimmed it (fix: cut)
- Locate the single missing or weak instruction responsible.
- Patch minimally: keep it short, make it operational, no vague style adjectives. Add an example only if the instruction can't carry the fix alone.
- Replay mentally: would the patched skill have produced the right output on the original failing input? If not, the diagnosis is wrong — go back to step 1.
- Add one regression test to the skill's evals: input, expected behavior, the failure it prevents.
Output format
Diagnosis
The exact failure and its type.
Minimal patch
The changed lines of SKILL.md, before/after.
Regression test
One new eval case in the repo's JSONL format.
Why this patch works
Two sentences max.