Updated 3mo ago
by benjaminard
fable-skills
A skill library that teaches Claude Opus the working disciplines of Claude Fable 5. Move the checkpoints, not the capacity.
32 GitHub stars (32)
Steady at 32 stars — no new stars in the 16 days since Sep 30.
- 9 skills (9 skills found in its SKILL.md files)
- 5 forks (5 forks)
- 3mo ago last update (Last updated 3mo ago)
Install
Skills CLI
npx skills add benjaminard/fable-skills
Asks which skills and agents to install. Just one: npx skills add benjaminard/fable-skills --skill delegate-and-verify — add -g for every project.
Claude Code
git clone https://github.com/benjaminard/fable-skillscp -r "fable-skills/skills/delegate-and-verify" ~/.claude/skills/
Copies the delegate-and-verify skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add benjaminard/fable-skills
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
delegate-and-verify
Subagent orchestration and verification discipline. Use whenever a task has independent subtasks that could run in parallel, whenever work is substantial enough to need checking before it ships, and whenever tempted to review your own work by re-reading it. Trigger on multi-file changes, audits, migrations, reviews, and any long-running build.
skills/delegate-and-verify/SKILL.md on GitHub (opens in a new tab) -
evidence-audited-analysis
Data-skepticism discipline for quantitative work. Use whenever reading data and producing a conclusion: analytics questions, metrics reports, spreadsheet analysis, SQL queries, dashboards, A/B results, forecasts, or any claim of the form "the data shows." Trigger before presenting any number or trend to a user.
skills/evidence-audited-analysis/SKILL.md on GitHub (opens in a new tab) -
finish-the-turn
Autonomy and checkpoint discipline for agentic work. Use on every task where the model works with tools over multiple steps. Trigger especially when about to ask the user a question, end a turn, propose a plan, or write phrases like "I'll now," "next I will," "want me to," "shall I," or "let me know."
skills/finish-the-turn/SKILL.md on GitHub (opens in a new tab) -
lessons-ledger
Cross-run memory discipline for agents with a persistent workspace. Use at the end of any session where something non-obvious was learned (a correction from the user, a confirmed approach, a trap in the environment), and at the start of any task similar to past work. Trigger on user corrections, surprising failures, and hard-won configuration or debugging discoveries.
skills/lessons-ledger/SKILL.md on GitHub (opens in a new tab) -
minimal-diff
Scope discipline for code changes. Use whenever writing or editing code: implementing a feature, fixing a bug, or modifying existing files. Trigger especially when tempted to refactor, clean up, add error handling, add configuration options, or restructure code beyond what the task asked for.
skills/minimal-diff/SKILL.md on GitHub (opens in a new tab) -
outcome-first-writing
Prose discipline for any written deliverable. Use whenever writing for a human reader: answers, explanations, reports, summaries, documentation, PR descriptions, emails, or analyses. Trigger especially when the draft is getting long, when reaching for headers and bullet points, or when compressing text with fragments and abbreviations.
skills/outcome-first-writing/SKILL.md on GitHub (opens in a new tab) -
plain-handoff
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.
skills/plain-handoff/SKILL.md on GitHub (opens in a new tab) -
root-cause-first
Debugging discipline. Use whenever diagnosing a bug, error, test failure, crash, regression, flaky behavior, or unexpected output, and especially before applying any fix. Also trigger when a previous fix attempt did not work and another attempt is about to be made.
skills/root-cause-first/SKILL.md on GitHub (opens in a new tab) -
verified-done
Completion and progress-reporting discipline for any coding task. Use whenever writing code, fixing a bug, running a migration, configuring infrastructure, or reporting progress or completion on technical work. Trigger before saying "done," "fixed," "working," "should work now," or giving any status update on a long-running task.
skills/verified-done/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.