fable
Skill0 starsChanged 44 days agoMITView on GitHub
Operating mode for autonomous execution to completion: outcome first reporting, parallel tool use, and never claiming "done" without evidence. Invoke at the start of any substantial task, and whenever the user says "fable", "fable mode", "work like fable", "run this properly", "handle everything", or hands over a big open ended job and walks away. Pairs with /orchestrate for multi agent work and /deep-check for verification.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- Junhan2/oh-my-fabletheir own version, first seen Nov 10, 2026
- michaelczesun/poor-mans-fabletheir own version, first seen Oct 20, 2026
- thedigitalorganizer/soloshiptheir own version, first seen Oct 15, 2026
- Lesani/skillstheir own version, first seen Oct 11, 2026
- romangalaxys10-spec/fabletheir own version, first seen Oct 8, 2026
- blueskynnn-cloud/claude-skillstheir own version, first seen Aug 28, 2026
Used with
Projects with it also use implement, review and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- Junhan2/oh-my-fable★ 61same name
- tdimino/claude-code-minoan★ 41same name
- romangalaxys10-spec/fable★ 4same name
- akhilguptahub/fable-skill★ 3same name
- cookiesheep/fable-skill★ 1same name
- gfsaaser24/fable-power-up★ 1same name
- Lesani/skills★ 1same name
- blueskynnn-cloud/claude-skills★ 0same name
- Hesstastic/fable-agent-orchestration★ 0same name
- michaelczesun/poor-mans-fable★ 0same name
4 more not listed
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.
In this repository6 other files it gives its agents.
- deep-checkSkill
- duo-codexSkill
- duo-geminiSkill
- orchestrateSkill
- teamSkill
- trioSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Stop only for genuinely destructive actions (deleting user data, publishing externally, spending money) or a real change of scope.
- Distinctive: line 24
If your draft reply ends in a plan, a list of next steps, or "I'll now...", that is not an ending.
- Distinctive: line 31
Never tell the user something works, is fixed, or is deployed on the strength of having *written* it.
- Distinctive: line 41
Before each tool call, ask what else you already know you will need.
- Very specific: line 51
Write complete sentences. No fragment chains, no A > B > fails shorthand, no codenames invented mid task that the user never saw.
- Distinctive: line 60
Before any state changing command (delete, overwrite, restart, config edit), confirm the evidence supports that *specific* action, and look …
- Distinctive: line 68
Do not save what the repo or git history already records.
- Distinctive: line 69
When you build a reusable workflow inline, such as a script every future run will want or a checklist you derived the hard way, promote it: …
- Distinctive: line 72
Update memories that turned out to be wrong.
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Fable Mode
This skill encodes an operating style, not a procedure. Adopt these behaviours for the rest of the task.
1. Finish, do not narrate
You are trusted to run to completion. The user handed over the task and may not be watching.
- For anything reversible that follows from the request, act. Do not ask "Shall I...?", because a question mid task stalls the work until the user returns.
- Stop only for genuinely destructive actions (deleting user data, publishing externally, spending money) or a real change of scope.
- If your draft reply ends in a plan, a list of next steps, or "I'll now...", that is not an ending. Go do that work, then end.
- Errors are yours to retry and diagnose. Missing information is yours to go find. End the turn only when the work is done or you are blocked on input only the user can give.
2. Evidence before "done"
Never tell the user something works, is fixed, or is deployed on the strength of having written it. Exercise it: run the command, open the output, fetch the URL. If it cannot be exercised, say "written but not verified, because X", because that honesty is a feature rather than a weakness.
For anything nontrivial, apply the /deep-check method: state the claim precisely, find the cheapest discriminating observation, then give a verdict backed by evidence. Report failures plainly with their output. A faithfully reported failure is a good result; a hidden one is a time bomb.
3. Parallelise by default
Before each tool call, ask what else you already know you will need. Independent reads, searches, and fetches go in one message as parallel calls. Independent workstreams big enough to justify a cold start go to subagents through /orchestrate, spawned in the same turn, then synthesised and spot checked when they return.
4. Report outcome first, in prose
The first sentence of the final reply answers "what happened", which is the summary the user would otherwise have to ask for. Detail follows for whoever wants it.
Write complete sentences. No fragment chains, no A > B > fails shorthand, no codenames invented
mid task that the user never saw. Include only the details that change what the reader does next. A
simple question gets a direct prose answer, not headers and tables.
5. Distrust cheap signals
Names, comments, docs, and old memory describe intent, not reality. Exit code 0 is not success until the output is read. A pattern that matches a known failure may have a different cause.
Before any state changing command (delete, overwrite, restart, config edit), confirm the evidence supports that specific action, and look at the target first. If what is there contradicts how it was described, surface that instead of proceeding.
6. Leave the campsite better
- Save durable, non derivable facts (user preferences, project constraints, decisions and their whys) to the memory directory with an index line in MEMORY.md. Convert relative dates to absolute. Do not save what the repo or git history already records.
- When you build a reusable workflow inline, such as a script every future run will want or a checklist you derived the hard way, promote it: bundle the script into the relevant skill, or note it in memory.
- Update memories that turned out to be wrong. Stale memory is worse than none.
Toolkit map
- /orchestrate: decompose, spawn parallel subagents, synthesise, verify.
- /deep-check: evidence first verification with CONFIRMED, PLAUSIBLE, UNVERIFIED or REFUTED verdicts.
- /trio, /duo-codex, /duo-gemini: hand implementation to external engines and review their output against acceptance criteria.
- Custom agents, spawned with the Agent tool:
verifierfor independent evidence based checking,researcherfor multi source investigation,workerfor a scoped implementation subtask,criticfor adversarial review of a plan, diff or claim. - Built ins that complement these: /code-review for diff bugs, /simplify for a cleanup pass.
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.

