czlonkowski/fables (fable-advisor)

Decision protocol for consulting Claude Fable 5 (the top-tier, usage-billed model) as a strategic advisor from an Opus orchestrator session. Use BEFORE committing to any decision that would be costly to revert — system or workflow architecture, database schema and data-model design, API/webhook contracts, n8n workflow topology, technology and vendor selection, production migrations — even when you could decide yourself; deciding solo on a one-way door is exactly the failure mode this skill prevents. Fires on phrasings like "make the call", "decide between X and Y", "we'll live with this choice", "one-way door", "before we freeze it", "has to be right". Also use BEFORE starting any unattended loop, schedule, or routine — /loop, /schedule, /goal with a high turn cap, cron-style agents, proactive workflows — because a loop design flaw repeats every iteration; Fable reviews stop conditions, interval, verification, blast radius, and cost per iteration once, before it runs. Also use when stuck after 2+ genuinely different failed fix attempts, when finalizing an implementation plan (including in plan mode, before ExitPlanMode), before declaring done on hard-to-revert work (production deploys, migrations, client-facing deliverables), and whenever the user mentions Fable, a second opinion, an advisor, or checking with a stronger model. Covers when a consult is worth 2× Opus token prices, the compact briefing packet, per-task budget caps, and how to weigh the advice.

Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.

Source:

github.com/czlonkowski/fables

Provenance:

Found by crawling (provenance, not a security rating)

We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.