Agent skill · writing content · anthropics
ib-check-deck
Investment banking presentation quality checker. Reviews a pitch deck or client-ready presentation for (1) number consistency across slides, (2) data-narrative alignment, (3) language polish against IB standards, (4) visual and formatting QC. Use whenever the user asks to review, check, QC, proof, or do a final pass on a deck, pitch, or client materials — including requests like "check my numbers", "reconcile figures across slides", "is this client-ready", or "what am I missing before I send this out".
Why this skill is useful
Adds a comprehensive QC workflow with executable scripts for number extraction and validation that aren't publicly available.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-08-04. 34,059 stars on the source repository.
What this skill does
IB Deck Checker Perform comprehensive QC on the presentation across four dimensions. Read every slide, then report findings. Environment check This skill works in both the PowerPoint add-in and chat. Identify which you're in before starting: Add-in — read from the live open deck. Chat — read from the uploaded .pptx file. This is read-and-report only — no edits — so the workflow is identical in both. Workflow Read the deck Pull text from every slide, keeping track of which slide each line came from. You'll need slide-level attribution for every finding ("$500M appears on slides 3 and 8, but slide 15 shows $485M"). A deck with 30 slides is too much to hold in working memory reliably — write the extracted text to a file so the number-checking script can process it. The script expects markdown-ish input with slide markers. Format as: 1. Number consistency Run the extraction script on what you collected: It normalizes units ($500M vs $500MM vs $500,000,000 → same number), categorizes values (revenue, EBITDA, multiples, margins), and flags when the same metric category shows conflicting values on different slides. This is the part most likely to catch something a human missed on the fifth read-through. Beyond what the script flags, verify: Calculations are correct (totals sum, percentages add up, growth rates match the endpoints) Unit style is consistent — the deck should pick one of $M or $MM and stick with it Time periods are aligned — FY vs LTM vs quarterly, explicitly labeled 2. Data-narrative alignment Map claims to the data that's supposed to support them. This is where decks go wrong quietly — someone edits the chart on slide 7 and forgets the narrative on slide 4. Trend statements ("declining margins") → does the chart actually go that direction? Market position claims ("#1 player") → revenue and share data support it? Plausibility — "#1 in a $100B market" with $200M revenue is 0.2% share; that's not #1 3. Language polish IB decks have a register. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills anthropics/ib-check-deck