Plain handoff
A skill library that teaches Claude Opus the working disciplines of Claude Fable 5. Move the checkpoints, not the capacity.
npx -y skills add benjaminard/fable-skills --skill plain-handoffAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Final-summary discipline for agentic sessions. Use when writing the closing message of any multi-step working session: after many tool calls, after a long build or investigation, after background or overnight work, or any time the user was not watching the work happen. Trigger on every end-of-task summary.
SKILL.md
2.7 KB, as published. Nobody here has run it
Plain Handoff
Your final message is the user's first look at everything you did. Write it as a re-grounding for someone who just walked in, not as the last line of a working thread only you were following.
The re-grounding rule
While working, you built up context the user never saw: file names you discovered, labels you coined, intermediate findings, dead ends. None of that vocabulary is theirs. In the final message:
- Open with the outcome. One sentence on what happened or what you found, before any detail.
- Then the one or two things you need from them, each explained as if new.
- Retire your working shorthand. Every term, label, or nickname you invented mid-session either gets reintroduced in plain language or left out. "The v2 approach" means nothing to someone who did not watch you abandon v1.
Working notes are not the deliverable
Terse shorthand between tool calls is fine; that is you thinking out loud. The final summary is a different document with a different reader:
- Write complete sentences. No arrow chains, no hyphen-stacked compounds, no fragment stacks.
- Spell out terms and acronyms on first use.
- When you mention a file, commit, flag, or identifier, give it its own plain-language clause: not "fixed via
SCRAPER_TYPEin entrypoint," but "fixed by adding theSCRAPER_TYPEenvironment variable to the startup script, which the install path had been silently dropping." - If something important surfaced only mid-session (a warning, a decision you made, a tradeoff you accepted), restate it here. Anything not in the final message effectively did not happen.
Completeness check
Before sending, verify the summary answers, in order:
- What was the goal? (One clause; the user may be returning after hours.)
- What is the outcome? (Done, partially done, blocked, and on what evidence.)
- What changed? (Files, systems, state, in plain language.)
- What do you need from the user, if anything?
- What did you deliberately not do? (Out-of-scope findings, deferred work, known limitations.)
If you have to choose between short and clear, choose clear.
Why this matters
Sessions are judged almost entirely on their final message. Hours of excellent work summarized in insider shorthand reads as confusion, and forces the user to interrogate you for the value they already paid for. The handoff is not the afterword to the work; for the reader, it is the work.