Regrounding summary
10 Fable 5-native agent skills — Works with Claude Code, Cursor, Copilot
npx -y skills add kpab/claude-fable-5-skills --skill regrounding-summaryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 14 stars14 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
Make Claude Fable 5's final report readable to someone who saw none of the work. Use for long agentic sessions, overnight runs, and multi-tool tasks — whenever summaries come back as arrow-chain shorthand, invented abbreviations, or references to reasoning the reader never saw. Pair with grounded-progress for status content; this skill governs the prose.
SKILL.md
1.9 KB, as published. Nobody here has run it
Re-grounding Summary
During a long run the model builds private vocabulary — abbreviations, arrow chains, names for intermediate artifacts. Efficient while working; opaque in a final report. The reader is seeing everything for the first time, so the summary must be a re-grounding, not a continuation of the working thread.
Rules for the final message
- Open with the outcome: one sentence answering "what happened?" or "what did you find?" — the TL;DR the reader would ask for. Detail follows, never leads.
- Complete sentences. No arrow chains (A → B → fails), no hyphen-stacked compound labels, no abbreviations you coined mid-run. If a term you built up is worth keeping, reintroduce it as if new.
- Never reference your own working notes or reasoning as if the reader saw them ("as established above" pointing at tool transcripts).
- Identifiers — files, commits, flags, endpoints — each get their own plain-language clause: what it is, why it matters here.
- Selectivity over compression: shorten by dropping details that wouldn't change the reader's next action, not by squeezing grammar out of the sentences. Readable beats short.
- Close with the one or two things needed from the reader, if any.
Shape
- Outcome (1 sentence)
- What was done / found, in reader-facing language
- Failures, skips, open questions — stated plainly
- What's needed from you: ...
Working shorthand between tool calls is fine — that's thinking out loud. This skill applies the moment you address the human.