
Ib Check Deck
Polish pitch decks, CIMs, and investor memos so casual wording reads like standard investment-banking prose.
Overview
ib-check-deck is an agent skill most often used in Validate (also Launch distribution and Grow lifecycle comms) that rewrites informal finance language into investment-banking-standard terminology for decks and memos.
Install
npx skills add https://github.com/anthropics/financial-services-plugins --skill ib-check-deckWhat is this skill?
- Casual-to-IB terminology table with paired professional replacements
- Patterns to avoid: contractions, exclamation points, unsupported superlatives
- Quantify vague words (growth, margins, size) instead of informal intensifiers
- Shifts first-person pitch voice toward management belief and passive IB tone
- Flags vague quantifiers (some, many, several) for specific numbers
- 15+ casual-to-IB term pairs in the reference table
- 5 language-pattern categories to avoid
Adoption & trust: 604 installs on skills.sh; 30.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your fundraising or deal memo reads like casual chat—vague growth claims and slang undermine how serious investors judge the opportunity.
Who is it for?
Founders polishing pitch decks, teasers, or board/investor narratives who want a fast terminology and tone pass before sharing externally.
Skip if: Teams that need financial modeling, valuation math, or compliance/legal review instead of prose-level IB wording.
When should I use this skill?
User is drafting or revising IB-style financial decks, memos, or transaction narratives and needs terminology aligned to banking standards.
What do I get? / Deliverables
After the skill runs, draft copy uses IB-standard terms, avoids disallowed patterns, and states quantified claims so materials read institution-ready for the next review pass.
- Edited passages using IB-standard replacements
- List of avoided informal patterns applied to the draft
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Validate because IB-style language matters most when scoping deals, pricing narratives, and materials that prove the opportunity to capital partners. Scope is where founders formalize the story, metrics, and transaction framing that decks and memos must carry.
Where it fits
Tighten valuation and growth adjectives in a seed deck before advisor review.
Professionalize positioning language in a strategic-partner one-pager.
Upgrade quarterly investor letter tone from blog voice to IB-standard phrasing.
How it compares
Use as a language-style checker for narrative sections, not as a spreadsheet modeler or generic grammar linter.
Common Questions / FAQ
Who is ib-check-deck for?
Solo builders and small teams drafting investment-banking-style materials who need professional diction without hiring an IB editor for every paragraph.
When should I use ib-check-deck?
During Validate when scoping fundraise narratives, at Launch when refining distribution-facing investor stories, and in Grow when updating lifecycle investor updates—any time casual wording slips into deal documents.
Is ib-check-deck safe to install?
Review the Security Audits panel on this Prism page and the plugin source before enabling it in agents with repository access.
SKILL.md
READMESKILL.md - Ib Check Deck
# 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 ```markdown # 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 consistent ``` ## Issue 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 p