Claude, IB Check Deck — What Does "Checking" a Pitch Deck Actually Mean?

Does having Claude check a pitch deck before it goes out just mean running a spellcheck? It doesn't. The real risk in a deck is usually numbers that stop agreeing with each other across slides, and the check this skill runs is built specifically to catch that, along with three other fixed things, every time it runs.

What a skill is, in this context

This kind of check is built from a Claude Skill, a folder Claude reads before it works. Inside is one file, written in plain language, that spells out exactly what to look for. Claude reads the file, then follows it; the file is the whole program. There's no separate proofreading tool running underneath, and no broader judgment about deck quality beyond what the file specifies.

How the check runs

The steps run in order: read the file, work through each step exactly as written, then return the result. Nothing runs out of sequence unless a step itself says so. For this skill, that fixed sequence applies to every deck it's run against, regardless of industry or deal type.

The four checks, exactly

The checklist is four things. Do the numbers agree across every slide? Does the narrative match the underlying data? Does the language hold up against investment banking standards? And is the formatting clean and consistent? Run the skill on the same deck twice, and it flags the same four things both times. Nothing outside that list gets checked, which is a deliberate boundary, not an oversight.

Reconciling, not proofreading

A skill like this doesn't proofread a deck in the sense of catching typos or grammar. It reconciles it: checking that numbers appearing on multiple slides actually match each other, that the story being told lines up with the numbers backing it, that the language fits the audience the deck is going to, and that formatting is consistent throughout. That's a narrower and more specific job than general editing, and it's worth understanding the difference before assuming a "checked" deck has been proofread in the conventional sense.

Why this scope makes sense for a deck

A pitch deck's biggest credibility risk usually isn't a typo, it's an internal contradiction: a revenue figure on slide four that doesn't match the same figure on slide twelve, or a growth story that the actual data doesn't support. A fixed four-item check that runs the same way every time gives a reliable way to catch exactly that category of error before a deck goes out, rather than relying on someone happening to notice a mismatch on a careful re-read.

Trying it yourself

A direct way to see the mechanism is to ask Claude to check a pitch deck for the same four things: numbers that don't match across slides, claims that don't match the underlying data, language that doesn't fit the intended audience, and any inconsistent formatting, and to list exactly what to fix before it goes out.

Key takeaways

• Claude's IB deck-check skill runs four fixed checks: number agreement, narrative-versus-data match, language standards, and formatting consistency.
• The skill's steps run in a fixed order: read the file, execute each step, return the result.
• Running the skill on the same deck twice flags the same four things; nothing outside that list gets caught.
• The skill reconciles a deck's internal consistency, it doesn't proofread for grammar or spelling.
• A deck's biggest credibility risk is usually a mismatch between slides, which is exactly what this check targets.

Who this is for

Investment banking analysts and associates preparing pitch decks who want a reliable pre-send consistency check, and anyone who wants to understand what "checking a deck" actually covers before assuming it means basic proofreading.