
Ib Check Deck
- 815 installs
- 33.8k repo stars
- Updated July 22, 2026
- anthropics/financial-services-plugins
ib-check-deck is an agent skill that reviews investment banking pitch decks for number consistency, narrative alignment, IB language, and visual QC without making edits.
About
The ib-check-deck skill performs comprehensive read-only QC on presentations across four dimensions. It works in PowerPoint add-in live deck mode or chat uploaded .pptx mode with identical workflow. Step one extracts text from every slide with slide markers into markdown for script processing. Step two runs extract_numbers.py to normalize units and flag conflicting metric categories, then manually verifies calculations, unit style consistency, and time period alignment. Step three maps narrative claims to supporting charts and data for trend statements, market position claims, and plausibility checks. Step four scans IB register for casual phrasing, contractions, and vague quantifiers using references/ib-terminology.md. Step five runs visual verification for missing chart sources, axis labels, typography drift, and overflow. Output follows references/report-format.md categorized as Critical, Important, or Minor with slide attribution on every finding.
- Four-dimension QC: numbers, narrative, language, and visuals.
- extract_numbers.py normalizes $500M vs $500MM conflicts.
- Data-narrative alignment catches chart vs claim mismatches.
- IB language register scan with terminology replacements.
- Read-only - no edits, severity-rated findings report.
Ib Check Deck by the numbers
- 815 all-time installs (skills.sh)
- +23 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #176 of 1,136 Finance & Trading skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
ib-check-deck capabilities & compatibility
- Capabilities
- cross slide number normalization and conflict de · data narrative claim mapping · ib terminology language polish · visual and formatting verification · severity rated slide attributed report
- Use cases
- presentations · code review
What ib-check-deck says it does
Perform comprehensive QC on the presentation across four dimensions.
npx skills add https://github.com/anthropics/financial-services-plugins --skill ib-check-deckAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 815 |
|---|---|
| repo stars | ★ 33.8k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 22, 2026 |
| Repository | anthropics/financial-services-plugins ↗ |
Are the numbers, narratives, and formatting in my pitch deck consistent and client-ready?
QC an investment banking pitch deck for number consistency, data-narrative alignment, IB language polish, and visual formatting before client delivery.
Who is it for?
Bankers and analysts doing a final proof pass on pitch decks or client presentations before send.
Skip if: Skip when you need to update figures in the deck - use deck-refresh instead of read-only QC.
When should I use this skill?
User asks to check, QC, proof, or do a final pass on a deck, pitch, or client materials.
What you get
A severity-rated QC report with slide-attributed findings across numbers, narrative, language, and visuals.
- IB-polished document copy
- terminology replacement pass
Files
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
.pptxfile.
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:
python scripts/extract_numbers.py /tmp/deck_content.md --checkIt 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. Scan for anything that breaks it: casual phrasing ("pretty good", "a lot of"), contractions, exclamation points, vague quantifiers without numbers, inconsistent terminology for the same concept.
See references/ib-terminology.md for replacement patterns.
4. Visual and formatting QC
Run standard visual verification checks on each slide. You're looking for: missing chart source citations, missing axis labels, typography inconsistencies, number formatting drift (1,000 vs 1K within the same deck), date format drift, footnote and disclaimer gaps.
Visual verification catches overlaps, overflow, and contrast issues that don't show up in text extraction. Don't skip it — a chart with no source citation looks the same as a properly sourced one in the text dump.
Output
Use references/report-format.md as the structure. Categorize by severity:
- Critical — number mismatches, factual errors, data contradicting narrative. These block client delivery.
- Important — language, missing sources, terminology drift. Should fix.
- Minor — font sizes, spacing, date formats. Polish.
Lead with criticals. If there aren't any, say so explicitly — "no number inconsistencies found" is a finding, not an absence of one.
IB Terminology Reference
Casual to Professional Replacements
| Casual/Informal | IB Standard |
|---|---|
| "a lot of growth" | "significant growth" or "X% growth" |
| "pretty good margins" | "attractive margins" or "margins of X%" |
| "they bought the company" | "the company was acquired" |
| "big deal" | "transformative transaction" |
| "cheap valuation" | "attractive valuation" or "valuation discount" |
| "expensive" | "premium valuation" |
| "make more money" | "enhance profitability" or "drive margin expansion" |
| "getting bigger" | "pursuing growth" or "expanding operations" |
| "cut costs" | "implement cost optimization" or "drive operational efficiencies" |
| "good fit" | "strategic fit" or "compelling strategic rationale" |
| "help with" | "support" or "facilitate" |
| "a bunch of" | "multiple" or "numerous" |
| "kind of" / "sort of" | [remove or be specific] |
| "really" / "very" | [remove or quantify] |
| "tons of" | "substantial" or quantify |
| "huge" | "significant" or quantify |
| "pretty much" | [remove or be precise] |
| "basically" | [remove or clarify] |
Language Patterns to Avoid
- Contractions: Don't → Do not, won't → will not
- Exclamation points: Generally inappropriate for IB materials
- First-person: "We think..." → "Management believes..." or passive voice
- Superlatives without evidence: "best-in-class" requires supporting data
- Vague quantifiers: "some", "many", "several" → specific numbers
Preferred Phrasing Patterns
Growth narratives:
- "Demonstrated track record of X% revenue CAGR"
- "Consistent margin expansion over [period]"
- "Proven ability to generate organic growth"
Market position:
- "#X player in [specific segment]"
- "Leading provider of [specific offering]"
- "Differentiated positioning through [specific attribute]"
Strategic rationale:
- "Compelling strategic fit driven by..."
- "Attractive value creation opportunity through..."
- "Synergy potential of $Xm from [specific sources]"
Deck Check Report Format
Report Template
# Deck Check Report: [Presentation Name]
## Summary
- Total issues: X
- Critical: X (number mismatches, factual errors)
- Important: X (narrative-data alignment, language)
- Minor: X (formatting)
## Critical Issues
### Number Consistency
1. **[Issue name]** (Slides X, Y)
- Slide X: [value]
- Slide Y: [value]
- Action: [recommendation]
### Data-Narrative Alignment
1. **[Issue name]** (Slides X, Y)
- Claim: "[quoted text]"
- Data shows: [contradiction]
- Action: [recommendation]
## Important Issues
### Language Polish
1. **[Issue type]** (Slide X)
- Current: "[quoted text]"
- Suggested: "[replacement]"
## Minor Issues
### Formatting
1. **[Issue type]** (Slide X)
- [Description and fix]
## Final Checklist
- [ ] Numbers reconciled
- [ ] Narrative matches data
- [ ] Language meets IB standards
- [ ] Charts sourced
- [ ] Formatting consistentIssue Severity Classification
Critical (must fix before client delivery):
- Number mismatches across slides
- Calculation errors
- Factual inaccuracies (names, titles, dates)
- Data contradicting narrative
Important (should fix):
- Casual/informal language
- Vague claims without specificity
- Terminology inconsistency
- Missing chart sources
Minor (polish items):
- Font/color inconsistencies
- Date format variations
- Spacing/alignment issues
- Orphaned text
#!/usr/bin/env python3
"""
Extract numerical values from presentation content for consistency checking.
Usage:
python extract_numbers.py presentation-content.md
python extract_numbers.py presentation-content.md --output numbers.json
This script parses markdown-formatted presentation content (from markitdown)
and extracts all numerical values with their context and slide references.
"""
import argparse
import json
import re
import sys
from collections import defaultdict
from dataclasses import dataclass, asdict
from pathlib import Path
from typing import Optional
@dataclass
class NumberInstance:
"""A numerical value found in the presentation."""
value: str # Original string representation
normalized: float # Normalized numeric value
unit: str # Detected unit (M, B, K, %, bps, x, etc.)
slide: int # Slide number (0 if unknown)
context: str # Surrounding text for context
line_number: int # Line number in source file
category: str # Detected category (revenue, margin, multiple, etc.)
def normalize_number(value_str: str, unit: str) -> float:
"""Convert a number string with unit to a normalized float value."""
# Remove commas and spaces
clean = re.sub(r'[,\s]', '', value_str)
try:
base_value = float(clean)
except ValueError:
return 0.0
# Apply unit multipliers
multipliers = {
'T': 1e12,
'B': 1e9,
'bn': 1e9,
'billion': 1e9,
'M': 1e6,
'mm': 1e6,
'mn': 1e6,
'million': 1e6,
'K': 1e3,
'k': 1e3,
'thousand': 1e3,
}
for unit_key in sorted(multipliers.keys(), key=len, reverse=True):
if unit_key.lower() in unit.lower():
return base_value * multipliers[unit_key]
return base_value
def detect_category(context: str, unit: str) -> str:
"""Detect the category of a number based on context and unit."""
context_lower = context.lower()
# Revenue-related
if any(term in context_lower for term in ['revenue', 'sales', 'top line', 'topline']):
return 'revenue'
# EBITDA-related
if 'ebitda' in context_lower:
if any(term in context_lower for term in ['margin', '%', 'percent']):
return 'ebitda_margin'
return 'ebitda'
# Margin-related
if any(term in context_lower for term in ['margin', 'profit']):
return 'margin'
# Growth-related
if any(term in context_lower for term in ['growth', 'cagr', 'yoy', 'y/y']):
return 'growth'
# Valuation multiples
if any(term in context_lower for term in ['multiple', 'ev/', 'p/e', 'ev/ebitda', 'ev/revenue']):
return 'multiple'
# Enterprise value / market cap
if any(term in context_lower for term in ['enterprise value', 'ev ', 'market cap']):
return 'valuation'
# Percentage (generic)
if unit in ['%', 'bps', 'percent']:
return 'percentage'
# Multiple indicator
if unit == 'x':
return 'multiple'
return 'other'
def extract_numbers(content: str) -> list[NumberInstance]:
"""Extract all numbers from presentation content."""
numbers = []
current_slide = 0
# Pattern for slide markers (from markitdown format)
slide_pattern = re.compile(r'^#+\s*Slide\s*(\d+)|^<!-- Slide (\d+)')
# Pattern for numbers with various formats
# Matches: $500M, 500M, $500 million, 25%, 25.5%, 2.5x, 150bps, $1,234.56, etc.
number_pattern = re.compile(
r'(?P<currency>[$€£¥])?' # Optional currency symbol
r'(?P<number>[\d,]+(?:\.\d+)?)' # The number itself
r'\s*'
r'(?P<unit>%|bps|x|' # Common units
r'[Tt]rillion|[Bb]illion|[Mm]illion|[Tt]housand|' # Full words
r'[TBMKtbmk]n?|mm|MM)?' # Abbreviations
r'(?!\d)' # Negative lookahead to avoid partial matches
)
lines = content.split('\n')
for line_num, line in enumerate(lines, 1):
# Check for slide marker
slide_match = slide_pattern.match(line)
if slide_match:
current_slide = int(slide_match.group(1) or slide_match.group(2))
continue
# Find all numbers in the line
for match in number_pattern.finditer(line):
value_str = match.group('number')
currency = match.group('currency') or ''
unit = match.group('unit') or ''
# Skip very short numbers without context (likely not financial)
if len(value_str.replace(',', '').replace('.', '')) < 2 and not unit:
continue
# Skip year-like numbers (1900-2099) unless they have units
try:
num_val = float(value_str.replace(',', ''))
if 1900 <= num_val <= 2099 and not unit and not currency:
continue
except ValueError:
pass
# Build full value string
full_value = f"{currency}{value_str}{unit}"
# Get context (surrounding words)
start = max(0, match.start() - 50)
end = min(len(line), match.end() + 50)
context = line[start:end].strip()
# Normalize unit
if currency:
if not unit:
unit = 'USD' # Assume USD for $ without unit
else:
unit = f"USD_{unit}"
normalized = normalize_number(value_str, unit)
category = detect_category(context, unit)
numbers.append(NumberInstance(
value=full_value,
normalized=normalized,
unit=unit or 'none',
slide=current_slide,
context=context,
line_number=line_num,
category=category
))
return numbers
def find_inconsistencies(numbers: list[NumberInstance]) -> list[dict]:
"""Find potential inconsistencies in extracted numbers."""
inconsistencies = []
# Group numbers by category
by_category = defaultdict(list)
for num in numbers:
if num.category != 'other':
by_category[num.category].append(num)
# Check each category for mismatches
for category, instances in by_category.items():
if len(instances) < 2:
continue
# Group by approximate value (within 5% tolerance)
value_groups = []
for inst in instances:
placed = False
for group in value_groups:
ref_value = group[0].normalized
if ref_value > 0:
diff_pct = abs(inst.normalized - ref_value) / ref_value
if diff_pct < 0.05: # 5% tolerance
group.append(inst)
placed = True
break
if not placed:
value_groups.append([inst])
# If we have multiple groups, there might be inconsistencies
if len(value_groups) > 1:
# Sort groups by size (largest first)
value_groups.sort(key=len, reverse=True)
# The largest group is likely "correct", others are potential issues
main_group = value_groups[0]
for other_group in value_groups[1:]:
inconsistencies.append({
'category': category,
'expected': {
'value': main_group[0].value,
'slides': sorted(set(n.slide for n in main_group)),
'count': len(main_group)
},
'found': {
'value': other_group[0].value,
'slides': sorted(set(n.slide for n in other_group)),
'count': len(other_group)
},
'severity': 'high' if category in ['revenue', 'ebitda', 'valuation'] else 'medium'
})
return inconsistencies
def main():
parser = argparse.ArgumentParser(
description='Extract numbers from presentation content for consistency checking'
)
parser.add_argument('input_file', help='Markdown file with presentation content')
parser.add_argument('--output', '-o', help='Output JSON file (default: stdout)')
parser.add_argument('--check', '-c', action='store_true',
help='Check for inconsistencies and report')
args = parser.parse_args()
# Read input
input_path = Path(args.input_file)
if not input_path.exists():
print(f"Error: File not found: {args.input_file}", file=sys.stderr)
sys.exit(1)
content = input_path.read_text()
# Extract numbers
numbers = extract_numbers(content)
# Prepare output
output = {
'total_numbers': len(numbers),
'by_category': defaultdict(list),
'numbers': [asdict(n) for n in numbers]
}
for num in numbers:
output['by_category'][num.category].append({
'value': num.value,
'slide': num.slide,
'context': num.context[:100]
})
output['by_category'] = dict(output['by_category'])
# Check for inconsistencies if requested
if args.check:
inconsistencies = find_inconsistencies(numbers)
output['inconsistencies'] = inconsistencies
if inconsistencies:
print("\n=== POTENTIAL INCONSISTENCIES DETECTED ===\n", file=sys.stderr)
for inc in inconsistencies:
print(f"Category: {inc['category'].upper()}", file=sys.stderr)
print(f" Expected: {inc['expected']['value']} (Slides: {inc['expected']['slides']}, Count: {inc['expected']['count']})", file=sys.stderr)
print(f" Found: {inc['found']['value']} (Slides: {inc['found']['slides']}, Count: {inc['found']['count']})", file=sys.stderr)
print(f" Severity: {inc['severity']}", file=sys.stderr)
print(file=sys.stderr)
# Output results
json_output = json.dumps(output, indent=2)
if args.output:
Path(args.output).write_text(json_output)
print(f"Output written to {args.output}", file=sys.stderr)
else:
print(json_output)
if __name__ == '__main__':
main()
Related skills
FAQ
Does ib-check-deck edit the presentation?
No - it is read-and-report only with no slide modifications.
How does it catch number mismatches?
extract_numbers.py normalizes units and flags when the same metric category shows conflicting values across slides.
What severity levels does the report use?
Critical for number and factual errors, Important for language and sources, Minor for formatting polish.
Is Ib Check Deck safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.