financial-model-narrative

$npx mdskill add mohitagw15856/pm-claude-skills/financial-model-narrative

Turns financial model outputs into a clear, structured written narrative suitable for board packs, investor updates, or management reporting.

SKILL.md

.github/skills/financial-model-narrativeView on GitHub ↗
---
name: financial-model-narrative
description: "Turn financial model outputs into a clear written narrative. Use when asked to write a financial narrative, explain a financial model, summarise a P&L, or translate spreadsheet numbers into a board-ready story. Produces an executive narrative with key insights, drivers, and forward-looking commentary."
---

# Financial Model Narrative Skill

Turns financial model outputs into a clear, structured written narrative suitable for board packs, investor updates, or management reporting.

## Required Inputs
- **Financial data** (paste key figures: revenue, costs, margins, EBITDA, cash)
- **Period covered** (month / quarter / annual / multi-year)
- **Audience** (board / investors / management / bank / internal)
- **Key message** (what is the headline story?)
- **Actuals vs budget / prior period?** (comparison context)

## Output Structure

### 1. Headline Summary
3-5 sentences. The financial story in plain English. Lead with the most important insight — not "revenue was X" but what that figure means.

### 2. Revenue
- Performance vs prior period / budget
- Key drivers: what caused the movement
- Risks or opportunities in the revenue line

### 3. Costs and Margins
- Gross margin: % and trend
- Key cost movements and why
- EBITDA performance and drivers
- One-off items clearly flagged

### 4. Cash and Balance Sheet
- Cash position and movement
- Runway (for startups)
- Key working capital movements

### 5. Variance Analysis
For each significant variance:

**[Line item] — Over/Under by [amount]**
- **Cause:** [Plain English explanation]
- **Permanent or temporary?** One-time / Structural
- **Action being taken:** [If applicable]

### 6. Forward-Looking Commentary
- Expected next period
- Key risks to forecast
- Key opportunities
- Any reforecast or guidance change

## Writing Rules
- Never just restate a number — always explain what it means
- Flag variances over 10% automatically
- Use past tense for actuals, conditional for forecast
- One insight per paragraph

## Quality Checks

- [ ] Headline summary leads with meaning, not just the number
- [ ] Every significant variance has a cause, permanence, and action
- [ ] Forward-looking commentary includes specific risks and opportunities
- [ ] Audience-appropriate language (board vs investor vs management)
- [ ] One-off items clearly distinguished from recurring items

## Example Trigger Phrases
- "Write a financial narrative for these results: [paste numbers]"
- "Turn this P&L into a board narrative"
- "Write the finance section of our board pack"
- "Explain these financial results in plain English"

More from mohitagw15856/pm-claude-skills

SkillDescription
360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.