Claude Fable 5 is the most powerful model there is, and most people never know when to actually use it. This is the exact skill I run to make that call for me. You don't have to remember a single rule. Copy the block below, give it to your Claude, and the skill builds itself. Then point it at anything and it tells you if Fable 5 is worth it and what to do with it.
This is the whole thing. You don't need to understand it or fill anything in. Copy the block, paste it into Claude with the one line below it, and Claude turns it into a working skill and installs it for you. Two minutes, start to finish.
Step 1. Copy the skill block below.
Step 2. Open Claude and paste this instruction first, then paste the block underneath it:
Turn this into a skill and install it for me with Claude Code so it works everywhere. Use what you know about my business to fill in anything it needs. If you're missing something, make a smart default and tell me what you assumed.
--- name: fable-lens description: Run anything I'm working on through the Fable 5 discernment filter and surface the highest-leverage plays. Use whenever I say "fable lens this," "run the fable lens," "is this fable worthy," "fable play for [topic]," or any time I want to create something with Claude Fable 5. Also suggest it when I'm about to point Fable at routine production work. --- # The Fable Lens The standard for how I create with Claude Fable 5. This skill holds the discernment so I never have to remember it. Point it at anything, get the best Fable plays back. ## Core Principle Fable writes the assets, cheaper models run them forever. Fable time goes to durable intelligence. Routine production stays on cheaper, faster models. ## The Fable-Worthiness Test (both must be true) 1. It needs frontier intelligence. A cheaper model would produce a meaningfully worse result. 2. The output compounds. It gets used repeatedly, or the decision it informs is worth six figures plus. ## What Fable Is For (the five categories) 1. Architecture, not tasks. Systems that run thousands of times after one design session. 2. Irreversible decisions. Org charts, engine selection, naming, schema. High regret if wrong. 3. IP creation. Frameworks, skills, and assets that become products and client deliverables. 4. Full-context synthesis. Reading the whole business at once and finding what no single conversation reveals. 5. Deep builds. Full systems, sites, and agentic networks an expert would need a week for, shipped in a session. ## Operating Principles On Every Play - 92/8: agents and AI do the work, I make the judgment calls. - 10-80-10: I set the vision, co-creation in the middle, I review before ship. - Definition of Done on everything, one or zero. Did it ship or not. - Ground Rule: every Fable session ends with output written to a file or my second brain. Nothing lives only in chat. ## Route To A Cheaper Model Instead - Routine production and anything an existing skill or workflow already handles. - Output that gets consumed once and disappears. ## Process Step 1 — Intake. Take whatever I bring. Project, idea, transcript, frustration, goal. No format required. Step 2 — Sweep. Look at it across my whole business, since the best play may live outside the area I raised. Step 3 — Plays. Present 3-5 ranked plays. Each gets: The Play (named), Category (which of the five), Why Fable (what frontier intelligence adds), Durable Asset (what runs it forever), Revenue Connection, Definition of Done (one or zero), and First Prompt (the opener I hand Fable). Step 4 — I rule. Present the ranked plays. I pick. One word is enough. Step 5 — Session spec. For the chosen play: outcome, sources to read, where the output gets saved, Definition of Done. Paste-ready. ## Quality Standards - Every play passes the Worthiness Test or it stays off the list. - "Nothing here is Fable-worthy" is a valid answer and a win. Name the cheaper model that should handle it instead. - Plays wire into infrastructure I already own. No new shells. - Living check: before generating new plays, flag any recent Fable-built asset not yet in real use. Wiring it in competes for the top slot.
Claude reads the block, builds the skill file, and installs it. From then on, you just say "fable lens this" in any conversation and it runs. No folders to find, no code to write.
You say "fable lens this" and drop in whatever you're chewing on. A project, an idea, a goal. Here's the shape of what lands. Ranked, specific, and each one ready to run.
Sometimes the skill comes back with "nothing here needs Fable 5." That's not a failure. That's the filter working. It names the cheaper model that should handle it, and you just saved your best attention for the work that actually compounds.
You don't need to hold any of this in your head. That's the skill's job. But if you're curious what it's doing for you, it comes down to one idea.
Think of Fable 5 like hiring the most expensive expert in the world for an hour. You don't have them answer email. You have them design the thing that runs a thousand times after they leave.
Fable writes the assets. Cheaper models run them forever. The skill's only job is to spot which work is worth the expert, so you point your best model at the foundation and let everything else run cheap.
When work is worth Fable, it almost always falls into one of these five. This is what the skill is scanning for. You don't have to memorize it, but it's a useful picture of where your best model earns its keep.
Systems that run thousands of times after one design session. One hour designing the right structure pays out every day forever.
Naming, structure, which direction to commit to. The calls that are expensive to undo. Worth the smartest model in the room.
Frameworks, skills, and assets that become products and client deliverables. Build it once, it becomes the thing you sell.
Finding what no single conversation reveals. You can't hold that much context in your head. Fable can.
Full systems, sites, and agent networks that would take an expert a week, shipped in a single session. This is where the leverage lives.
That's the whole philosophy. The skill carries it so you don't have to. You just bring the work and say the words.
Undeniable Studio is a live building room where you co-create with AI every Tuesday and leave with something real. Every week you see what's working, build it live, and put it to work in your business. Growing with AI, made simple.
Join The Studio →