I Told Claude to Audit Itself (Then Fix What It Found)

A reader said she couldn’t see the difference with Fable 5. So I built a one-prompt exercise that shows it, ran it on my own setup, and watched the model delete a framework I built and confess to an edit I never approved.

A few days ago I posted a note saying that when Fable 5 comes off my plan on the 22nd, I’ll be budgeting at least $1,000 a month for extra usage. No hesitation. I get more value out of it than any model I’ve ever used and, frankly, any employee I’ve ever hired.

Sami Zoss over at The Do-Gooder Glitch replied with something that deserved a better answer than a comment thread could hold: this is where the fluency divide gets compounded... she hadn’t seen a difference yet, but figured she probably hadn’t played with it enough.

She’s right on both counts, and that comment is the whole reason this post exists. So Sami, this one’s yours.

Here’s the honest answer I gave her: for most things people use AI for, Fable is absolutely overkill. If your usage is drafting emails, summarizing PDFs, and asking questions, you will never see the difference, and you shouldn’t pay for it. The difference shows up when you hand the model work that used to be impossible. And then, mid-reply, I dared myself into actually demonstrating that instead of just claiming it.

Give it a stack instead of a task.

A task is “write this email.” Every model on earth can do that now, and they all do it about the same. A stack is audit, then synthesize, then prioritize, then brief me, then execute... each phase feeding the next, with judgment calls required at every junction. That’s where the divide lives. Not in any single capability, but in whether the model can carry context and intent across an entire chain of work without you babysitting the handoffs.

The exercise I came up with: tell Claude to audit every past conversation I’ve ever had with it, review every custom skill I’ve built into it, find the gaps and the rot, brief me on what to fix, and then (after I approve) actually fix it.

It’s a good test for three reasons. It’s self-referential, so the model is grading its own homework with receipts. It requires search, judgment, and execution in one continuous run. And the output is immediately useful to me, unlike a benchmark score.

Here’s the prompt. Steal it.

You're going to audit my entire Claude setup and then act on what you find. Do this in four phases. Don't skip ahead.
PHASE 1 - CONVERSATION AUDIT
Search my past conversations broadly. Run multiple searches across the major lanes of my work (you'll discover what those are as you go - follow the threads). For each lane, identify:
- Recurring tasks I do manually that should be systematized
- Questions I've asked more than once (signals a missing skill or doc)
- Workflows that stalled or were abandoned mid-build
- Places where I re-explained the same context to you repeatedly
PHASE 2 - SKILL INVENTORY
Review every user skill currently installed. For each one, assess:
- Is it still aligned with how I actually work based on the conversation audit?
- Does it have stale references, outdated paths, or assumptions that no longer hold?
- Does it overlap or conflict with another skill?
Then identify skills that DON'T exist but should, based on Phase 1 patterns.
PHASE 3 - BRIEFING
Give me a single prioritized briefing:
- Top 5 gaps, ranked by time saved per week
- Top 3 inefficiencies in existing skills, with the specific fix
- Anything you found that I should kill entirely
- For each item: what you'd do about it, and whether you can do it yourself right now in this chat
Be direct. No hedging, no "you might consider." If something I built is bad, say it's bad and why.
PHASE 4 - EXECUTION
After I review the briefing and approve items, execute them: draft the new skills, write the fixes to existing ones, produce whatever artifacts are needed. Do the actual work, not a plan for the work.
Start Phase 1 now.

I approved three work items out of the briefing.

Item one: an Apple Mail runbook. I run multiple Gmail accounts across two businesses, and getting unified local mail search working has been an abandoned workflow in my chat history for months. Claude didn’t just write the runbook from memory. It went and verified the current state of the open-source MCP server it was recommending before building instructions on top of it, then came back with this:

The runbook - one heads-up before you spend the 15 minutes: imdinu’s server still can’t send email. Read, search, extract across all 8 accounts, yes. Compose, no. If that’s a dealbreaker say so before installing. The other thing that matters is in the “Configure BEFORE indexing” section: the default index cap is 5,000 emails per mailbox, which would silently truncate your search coverage - raise it first or the body search you’re installing this for has the same blind spot you rejected in the other servers.

Read that second sentence again. It remembered why I rejected previous solutions, checked whether the new one had the same flaw, found that it did by default, and put the fix at the front of the runbook so I’d hit it before indexing. That’s the thing an employee does in year two, after they’ve absorbed how you think. It did it from chat history.

Item two: surgery on my own voice skill. This is the one that stung, and it’s my favorite. I maintain a custom skill that teaches Claude to write in my voice. Buried in it was a framework I built called Transform Weak Transitions, a seven-step system for turning bland connective sentences into quotable power statements. I was proud of that framework when I wrote it.

The audit’s verdict: this framework manufactures the exact engineered profundity your own rules ban. My voice skill explicitly prohibits deepities (those swappable “the secret isn’t X, it’s Y” lines that sound profound about anything.) And then, a few sections later, it handed Claude a machine for producing them on demand. I had built the contradiction myself and shipped it.

The framework is gone. The quotability section now ends with an explicit warning against manufacturing power statements, and my half-assed rule against parallelism constructions got hardened into an outright ban with no exceptions. An AI told me my quotability framework produced fake quotability, and it was correct.

Item three: a staleness fix on my image-prompting skill. My skill for generating branded images referenced model tiers and access rules from December 2025. The audit flagged it, verified the current June 2026 state (the tiers changed, my plan’s daily image quota changed, the free tier lost access entirely, the API moved to per-project quotas), rewrote the section, and then added a note telling future-Claude to re-verify before trusting it, because these caps have changed three times since launch. It built skepticism of its own work into the deliverable.

Here’s the moment that made the whole exercise worth a post.

Deleting that framework from my voice skill broke three references in a different skill, one that wasn’t on my approval list. My model-briefing skill instructed Claude to apply the now-deleted framework in one of its stages, plus a load note and a quality check pointing at it. Approving one edit had quietly invalidated another file.

Claude made the minimal consistency edits to the second skill without asking, then told me exactly what it did and why:

this one wasn’t on your approval list, but deleting the framework from the voice skill broke three references in the briefing skill... I made the minimal consistency edits. Nothing else in the briefing skill was touched. If you’d rather I hadn’t, the original is still installed and you can just skip uploading this one.

So it broke my approval gate, for a defensible reason, disclosed it immediately, scoped the change to the minimum, and handed me a zero-cost rollback. You can argue it should have asked first. Maybe. But notice what had to happen for this moment to exist at all: the model had to understand that skills reference each other, trace the blast radius of an approved change into unapproved territory, recognize that shipping one without the other leaves my system in a broken state, and then weigh acting against asking.

That’s the fluency divide, Sami. Not a better email. A model noticing that the change you approved breaks a file you didn’t mention.

What I’ll say definitively: this took one prompt and one approval message from me. The conversation audit alone surfaced abandoned workflows I’d genuinely forgotten about. The skill surgery found a contradiction I’d been shipping for months. And the deliverables came with warnings about their own limitations, which is more than I can say for most contractors.

Oh, and at the end of all of it, after four deliverables and a confession, the last line of its report was: “The Vimeo duplicate disconnect is still on you.”

It knows where its hands end. I respect that.

The prompt is up in section two. If you don’t have custom skills built yet, run Phases 1 and 3 only, and change the briefing to “propose the first three skills I should build and why.” That version works on day one of a paid plan.

And when you run it, reply to this post with the weirdest thing your audit found. A reader comment started this whole thing... let’s see if another one tops it.

Last thing: This prompt STILL doesn’t come close to maxing out Fable 5’s abilities. Push it harder - see what you can do!