Someone just shipped a skill.md that fills a real gap in Claude Code’s native /advisor command. The twist is that the most useful part isn’t the model routing. It’s the checker.
What’s new
/advisor [model|off] lets a main model do the work and call a stronger advisor at decision points. Per the docs, it tends to consult before committing to an approach, when an error keeps recurring, and before declaring a task done. The timing is model-driven, not rule-based.
Here’s the catch. The advisor has no tools. It can’t spawn or direct other agents. So if your job has to be split (collect sources, fact-check, write, judge the draft), /advisor can’t split it for you.
u/Parking-Kangaroo-63 posted a skill that picks between two modes:
- Mode A, native /advisor: one cheaper agent can do the whole task, and only the decisions need a stronger model.
- Mode B, Fable 5.2 as main: the work has to be split across models, and Fable delegates down.
It doesn’t decide whether to delegate at all. That’s the author’s earlier skill, subagent-dispatch-economics. This one starts after that call.
The twist
A Sonnet checker once found a \”quote\” that a Haiku collector had saved, and that quote wasn’t on the page. That’s why the skill gates everything on a checker tier.
The author then ran the pattern on 16 Nov, with Fable 5.2 as main and /advisor off. Four subagent jobs, 339,341 subagent tokens in total:
- Haiku read-only lookup of a tool’s database: 91,409 tokens.
- Sonnet fact-check of the generated skill: 78,437 tokens. Of 28 claims, 8 passed, 4 drifted, 11 were invented and 5 were missing.
- Sonnet fact-check of Fable’s own LinkedIn drafts: 89,861 tokens. Of 56 rows, 37 passed, 5 needed a fix, 10 were unsupported and 4 had no source.
- Haiku cold-read judge of those drafts: 79,634 tokens. Seven drafts scored 2 to 4 out of 5, with 2 AI tells.
The checker flagged 19 lines in the top model’s own drafts. The top model needs checking too.
The mini-workflow
- 🔧 Confirm delegation is already decided. If the answer is don’t delegate, stop and do it in the main session.
- 🔧 Pick the mode. One cheap agent plus decision help means Mode A. A job that must be split means Mode B.
- 🔧 In Mode B, assign tiers. Fable plans, makes the calls and writes the final copy. Haiku collects sources and does read-only lookups. Sonnet fact-checks each claim against its saved source. A cheap model that did not write the draft cold-reads it.
- 🔧 Set the handoff rules. Every subagent writes its full result to a file with no length limit. The message it returns is 200 words or fewer and names the file. The cap is on the return message only, not the file and not the final copy.
- 🔧 Hold collector output until a checker passes it. Verdicts are PASS, FIX, UNSUPPORTED, NO SOURCE. Keep one run-log row per subagent: job, model, tokens, verdict, file.
Pro tips
- Spawn cheap jobs as fresh agents. A forked subagent inherits the parent model and ignores the model override, so a fork won’t give you Haiku.
- Never let the writer judge its own draft.
- Don’t quote the Anthropic April benchmark (Sonnet with an Opus advisor, +2.7 points on SWE-bench Multilingual, 11.9% lower cost per task) as a Fable 5.2 result. Those were older models. The author couldn’t find a Fable advisor number from Anthropic, so the skill leaves it out. That honesty is worth copying.
- If you generate skills like this, give the generator a reference file of verified facts. In the author’s evaluation, runs with a reference file got 8 of 8 usable (74 of 80 required rules came through). Goal-only runs got 0 of 8 worth using.
Fair warning
The author is upfront about the limits. A fresh Sonnet agent followed the skill on four tasks and picked the expected path every time. That’s a smoke test, not an evaluation. Nobody has measured whether Mode B is cheaper or better than one Fable agent doing everything. Treat it as a solid starting template, not proven economics.
Requirements: native /advisor is experimental and needs the Anthropic API, Claude Platform on AWS, or Claude Models on Google Cloud. Fable 5.2 needs Claude Code v2.1.321 or later, and on some plans its usage bills to usage credits.
Call to action
⚓ Grab the skill from the repo (nivlewd1/prompt-optimizer, skill/advisor folder), drop it into a task where you already split work by hand, and compare the run log against your usual way.
Then tell me: has a cheap checker ever caught something your top model got wrong? As u/bytezvex put it, top model drafts still hallucinate little details a checker catches way too often on sourced work. I’d bet most of you have a story!
Claude Code’s /advisor can’t hand work to other agents. Here’s a skill.md that decides when a job needs splitting and which model gets each piece
by u/Parking-Kangaroo-63 in PromptEngineering