# Ib Check Deck

Investment banking presentation quality checker.

- Repository: https://github.com/anthropics/financial-services (40971 stars)
- Category: Documents
- License: Apache-2.0
- Last updated: 2026-10-28
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add anthropics/financial-services --skill ib-check-deck -g -a claude-code -y`
Codex: `npx skills add anthropics/financial-services --skill ib-check-deck -g -a codex -y`
Cursor: `npx skills add anthropics/financial-services --skill ib-check-deck -g -a cursor -y`
Gemini CLI: `npx skills add anthropics/financial-services --skill ib-check-deck -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add anthropics/financial-services`

## Description

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".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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:

```
## Slide 1
[slide 1 text content]

## Slide 2
[slide 2 text content]
```

### 1. Number consistency

Run the extraction script on what you collected:

```bash
python scripts/extract_numbers.py /tmp/deck_content.md --check
```

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.

The rest: https://github.com/anthropics/financial-services/blob/HEAD/plugins/agent-plugins/pitch-agent/skills/ib-check-deck/SKILL.md