mohitagw15856
05b6d799f0
Three more learnings from alirezarezvani/claude-skills, applied: 1. SkillCheck validator (scripts/skillcheck.mjs) — validates every SKILL.md against the authoring standard (frontmatter, name/folder match, trigger + produces clauses, required headings) plus tier referential integrity. Errors fail CI; --strict fails on warnings too. New skillcheck.yml workflow and a SkillCheck status badge in the README. Current: 0 errors / 14 advisory warnings across 172 skills. 2. Cursor export platform — build-exports.mjs now generates exports/cursor/<bundle>/<skill>/<skill>.mdc rule files. The PLATFORMS registry now supports per-skill filenames (file as a function). 3. Per-agent installers — scripts/install.sh unifies install for claude/hermes/codex/openclaw/cursor (--link, --target, --dry-run, --list). Curl-able one-liners codex-install.sh, openclaw-install.sh, and cursor-install.sh clone the library and install in a single command. README documents the one-line installs and Cursor exports; CHANGELOG and the authoring standard updated. Claude-Session: https://claude.ai/code/session_016JWn5jRD5tcEFKrubjQ6Px Co-authored-by: Claude <noreply@anthropic.com>
80 lines
3.1 KiB
Plaintext
80 lines
3.1 KiB
Plaintext
---
|
|
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."
|
|
globs:
|
|
alwaysApply: false
|
|
---
|
|
|
|
# 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
|
|
|
|
## Anti-Patterns
|
|
|
|
- [ ] Do not list numbers without explaining what is driving them — narrative must go beyond restating the figures
|
|
- [ ] Do not mix one-off items with recurring performance without clearly distinguishing them
|
|
- [ ] Do not write the same level of detail for all line items — focus depth on the items that matter most
|
|
- [ ] Do not omit forward-looking commentary — a narrative without outlook is incomplete for board or investor audiences
|
|
- [ ] Do not use technical accounting language without translation — the audience is executives, not accountants
|
|
|
|
## 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"
|