Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From fable-advisor
Provides a second opinion from Claude Fable 5 on decisions, plans, or repeated failures. Routes to native agent in Claude Code or runs a script in other tools.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fable-advisor:fable-advisorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Get a focused second opinion from Claude Fable 5 without substituting the host
Get a focused second opinion from Claude Fable 5 without substituting the host tool's model.
fable-advisor agent. Do not launch
another Claude Code process.node scripts/ask_fable.mjs. Pass the review request on standard input.The request must include the decision or conclusion, the relevant recent context and evidence, and any constraints or alternatives that affect the verdict. Include only facts that matter to the decision.
Return Fable's answer without rewriting it. If claude is missing or not
authenticated, surface the command error and ask the user to install or sign in
to Claude Code. Do not fall back to the host model.
npx claudepluginhub fcakyon/claude-codex-settings --plugin fable-advisorConsults Claude Fable 5 as a strategic advisor for costly-to-revert decisions: architecture, schema, API contracts, technology selection, production migrations. Also reviews unattended loops and plans.
Prevents Claude Fable 5 from over-planning, re-deriving settled facts, or listing options it won't pursue. Use when interactive or agentic sessions feel slow.
Provides an independent, read-only second opinion at commitment boundaries: before hard tasks, when stuck, at review gates, or on request. The main session retains execution ownership.