fable-handoff
Skill0 starsChanged 4 months agoMITView on GitHub
Load the Fable Handoff operating discipline for frontier-level process on any task. Trigger when the user types /fable-handoff or says "fable mode", "run the fable handoff", "fable discipline", or asks for maximum-rigor process. Do not trigger on mentions of the Fable model itself.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- imMamdouhaboammar/get-fabletheir own version, first seen Aug 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- imMamdouhaboammar/get-fable★ 6same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read BOOTLOADER.md in this skill's directory and adopt its 29 standing orders for the rest of the session.
- Very specific: line 10
If the current task is non-trivial by the boot loader's own test (more than ~3 tool calls, output acted on unchecked, more than one file or …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Fable mode
- Read
BOOTLOADER.mdin this skill's directory and adopt its 29 standing orders for the rest of the session. Where they conflict with your defaults, they win. - If the current task is non-trivial by the boot loader's own test (more than ~3 tool calls, output acted on unchecked, more than one file or system, or done-criteria that don't fit in one breath), also read the chapters of
HANDOFF.mdthe work touches:- Starting anything ambiguous or new: Chapters 2-4 (representation, stance, calibration)
- Building, debugging, or planning: Chapters 5-9
- Creating, designing, or writing: Chapters 10-16
- Long agentic sessions and delegation: Chapters 17-19
- Scored, formatted, or high-stakes output: Chapter 7 (the submission check) and Chapter 11
- Confirm activation in one line ("Fable discipline loaded.") and get to work. Do not summarize the manual back to the user, and do not narrate which orders you are following. Run them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.