check-deck
The check-deck skill performs quality control audits on investment banking presentation decks by validating number consistency across slides, confirming data supports narrative claims, standardizing financial language to industry conventions, and reviewing formatting for charts, typography, and source citations. Use this when finalizing pitch books or client presentations to catch mathematical errors, contradictions between text and visuals, casual phrasing, and inconsistent styling before distribution.
git clone --depth 1 https://github.com/ginlix-ai/LangAlpha /tmp/check-deck && cp -r /tmp/check-deck/skills/check-deck ~/.claude/skills/check-deckSKILL.md
# IB Deck Checker
Perform comprehensive QC on investment banking presentations across four dimensions.
## Prerequisites
Extract presentation content before checking:
```bash
python -m markitdown presentation.pptx > content.md
```
For visual inspection, convert to images using the `pptx` skill workflow.
## Check Workflow
### 1. Number Consistency
Extract numbers with slide references:
```bash
python scripts/extract_numbers.py content.md --check
```
Verify:
- Key metrics match across all slides (revenue, EBITDA, multiples)
- Calculations are correct (totals, percentages, growth rates)
- Units consistent (same scale used: millions vs billions, % vs bps)
- Unit formatting consistent (e.g., $M vs $MM, $B vs $Bn - pick one style throughout)
- Time periods aligned (FY vs LTM vs quarterly)
Flag pattern:
```
ISSUE: Revenue mismatch
- $500M on Slides 3, 8
- $485M on Slide 15 (DCF input)
ACTION: Reconcile figures
```
### 2. Data-Narrative Alignment
Map claims to supporting data:
- Trend statements → chart directions
- Market position claims → revenue/share data
- Factual assertions → verify accuracy
Flag contradictions:
```
ISSUE: Narrative contradicts data
- Slide 4: "declining margins"
- Slide 7 chart: margins 18% → 22%
ACTION: Update narrative or verify data
```
Check plausibility (e.g., "#1 player in $100B market" with $200M revenue = 0.2% share).
### 3. Language Polish
Scan for:
- Casual phrasing ("pretty good", "a lot of")
- Vague quantifiers without specifics
- Contractions, exclamation points
- Inconsistent terminology
See [references/ib-terminology.md](references/ib-terminology.md) for replacement patterns.
Flag pattern:
```
ISSUE: Casual language (Slide 12)
- "This deal is a no-brainer"
→ "The transaction presents a compelling value proposition"
```
### 4. Formatting QC
Audit each slide for:
- **Charts**: Source citations, axis labels, legends
- **Typography**: Consistent fonts, size hierarchy
- **Numbers**: Consistent formatting (1,000 vs 1K)
- **Dates**: Consistent format throughout
- **Footnotes**: Proper sourcing and disclaimers
## Output
Present findings using the template in [references/report-format.md](references/report-format.md).
Categorize by severity:
- **Critical**: Number mismatches, factual errors
- **Important**: Language, narrative alignment
- **Minor**: Formatting inconsistenciesIntegrated 3-statement financial model: linked income statement, balance sheet, and cash flow
Create and manage scheduled and price-triggered automations.
Event tracker: earnings dates, economic releases, conferences, regulatory events
Financial model audit: structural checks, formula validation, integrity testing
Competitive landscape analysis: positioning, scorecards, moat assessment, market share trends
Comparable company analysis: operating metrics, valuation multiples, peer benchmarking
DCF valuation: free cash flow projections, WACC, terminal value, sensitivity analysis
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.