agentleFS
wickedhardflipwickedhardflip/claude-code-tips/skills/fable-setup/SKILL.md

fable-setup

Skill1 starsChanged 38 days agoMITView on GitHub

Create a subfolder workspace where Fable 5.2 is the main model, unnamed subagents default to Opus, and saved subagents are tiered (fetcher on Haiku, fixer on Sonnet, builder on Opus), with a CLAUDE.md that makes Fable the lead (plans, decides, reviews) and fans bulk work out to parallel subagents. Optional git worktree of a repo inside it. Use when the user says "fable setup", "make a fable folder", "set up a fable session/workspace", or "/fable-setup". Builds the folder only; the user starts the session there.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Junhan2/oh-my-fable★ 61same 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.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If no name is given, ask for one.

    line 20
  2. Very specific:

    If the folder exists and already has .claude/settings.json, stop and say so.

    line 24
  3. Distinctive:

    Never touch the repo's main checkout, even when it has modified files.

    line 34
  4. Very specific:

    Check that the status line shows Fable 5.2 (or /model to confirm).

    line 37
  5. Very specific:

    When the work is merged, remove the worktree: git -C "<repo>" worktree remove "<folder>/repo".

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fable workspace setup

Builds a folder that the user opens a NEW claude session in. A running session cannot switch its own subagent defaults, so the folder carries them: .claude/settings.json makes Fable 5.2 the main model and Opus the default subagent model, .claude/agents/ holds three tiered subagents, and CLAUDE.md holds the working rules.

Templates sit next to this file in templates/.

Args

/fable-setup <name> [repo]

  • <name>: folder name, created under the current workspace folder. A full path is also accepted.
  • [repo]: optional path to a git repo. When given, a worktree goes in <folder>/repo/.

If no name is given, ask for one. Ask nothing else.

Steps

  1. If the folder exists and already has .claude/settings.json, stop and say so. If it exists without one, add the files and leave everything else alone.
  2. Copy templates/settings.json to <folder>/.claude/settings.json as is, and copy templates/agents/*.md (fetcher = Haiku, fixer = Sonnet, builder = Opus) to <folder>/.claude/agents/.
  3. Copy templates/CLAUDE.md to <folder>/CLAUDE.md, replacing {{NAME}}, {{DATE}} (today) and {{REPO_LINE}}:
    • no repo: No repo is attached. Work happens in this folder.
    • repo: The code is in repo/, a git worktree of <repo> on branch <branch>, cut from origin/<default> <sha>. Read the repo's own CLAUDE.md first.
  4. Repo only, all as git -C "<full repo path>":
    • fetch origin --quiet, then symbolic-ref --short refs/remotes/origin/HEAD to find the default branch
    • worktree add "<folder>/repo" -b fable/<name> origin/<default>
    • Never touch the repo's main checkout, even when it has modified files.
  5. Reply with the folder path, the branch and sha if there is a repo, and the start steps:
    1. Open a new terminal in <folder> and run claude.
    2. Check that the status line shows Fable 5.2 (or /model to confirm).
    3. Repo only, and only if the repo has no CLAUDE.md of its own: run /init first so it writes one.
    4. Shift+Tab into plan mode, then give it the job.
    5. /tasks shows which model each subagent is on. /compact when heavy, /clear between jobs.

Notes

  • To change a default for every future folder (effort level, subagent model), edit templates/settings.json. To change it for one folder, edit that folder's .claude/settings.json.
  • Memory is keyed to the folder, so a new folder starts with none. The template points the session at your main memory folder; fill in its path once in templates/CLAUDE.md.
  • When the work is merged, remove the worktree: git -C "<repo>" worktree remove "<folder>/repo".

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.