Narrative to Numbers

Builds the business story behind a valuation and connects it to the drivers that carry value — market size, growth, margin, reinvestment efficiency and risk. Tests a narrative as possible, plausible and probable, and keeps the feedback loop open. Use when starting a valuation, writing the story behind a company, setting growth or margin assumptions, sanity-checking a story against its numbers, choosing a target margin or sales-to-capital ratio, or when a valuation needs a defensible reason for its inputs.

200 stars 25 forksMarketing, Sales & Business Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lyndonkl/claude

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lyndonkl/claude --skill narrative-to-numbers
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/narrative-to-numbers ~/.claude/skills/narrative-to-numbers

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Narrative to numbers

A story without numbers is a fairy tale. It cannot be wrong, so it cannot be tested, and
it never tells you what price to pay. Numbers without a story are a spreadsheet nobody
believes. Every input came from somewhere, but nobody can say where, so any reader who
disagrees has nothing to argue with except the answer.

The bridge between them is a mapping rule, and it runs both ways:

- Every claim in the story moves **exactly one** driver in the model.
- Every input in the model carries **one sentence** of story.

Two counts prove the bridge holds. Model inputs with no story sentence: zero. Story claims
with no driver: zero. Both counts are mechanical, and the second one is where most
valuations fail — a claim that moves no driver is decoration, and a claim that moves two
is double counted.

This skill owns stages S1, S2, S11 (the driver choices) and S18 of
`knowledge/frameworks/intrinsic-valuation-playbook.md`. It produces `03-narrative/narrative.md` and
`03-narrative/drivers.json`.

## The sequence

```
1. Survey the landscape     business map + base-year numbers + benchmarks
2. Write the narrative      prose, spreadsheet closed
3. Test it                  possible / plausible / probable, then the three screens
4. Connect to drivers       each claim -> one payload field
5. Value it                 dcf-valuation-engine, then the consistency validator
6. Keep the loop open       counter-narratives now, break/shift/change later
```
Read the full skill on GitHub

Details

Skill name
narrative-to-numbers
Path
skills/narrative-to-numbers/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Narrative to Numbers skill do?

Builds the business story behind a valuation and connects it to the drivers that carry value — market size, growth, margin, reinvestment efficiency and risk. Tests a narrative as possible, plausible and probable, and keeps the feedback loop open. Use when starting a valuation, writing the story behind a company, setting growth or margin assumptions, sanity-checking a story against its numbers, choosing a target margin or sales-to-capital ratio, or when a valuation needs a defensible reason for its inputs.

How do I install the Narrative to Numbers skill?

Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Narrative to Numbers popular?

It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.

Related skills

Abstraction Concrete Examples

200

lyndonkl/claude

Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.

Testing & QA25

Academic Letter Architect

200

lyndonkl/claude

Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.

Research & Science25

Adr Architecture

200

lyndonkl/claude

Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.

Software Development25

Quarterly Zoomout

200

lyndonkl/claude

Synthesizes 13 weeks of substacker Growth Analyst reports + the most recent Curator review + a meta-scan of the published corpus into a 400-700 word narrative that names the quarter's shape — what happened, what changed, what held steady, what surprised. Used by the Growth Strategist at the opening of every review. Trigger keywords — quarterly, zoomout, quarter narrative, rollup, what happened this quarter.

Marketing, Sales & Business25

Narrative Handoff Contract

200

lyndonkl/claude

Defines and validates the machine-readable contract that passes a narrative architecture between a structural agent and a drafting agent — architecture.json with evidence-backed slots, capped scene tags, gap dispositions, a DEAD column, and an escalation object for sending defects back upward. Ships a validator script so the rules are enforced rather than requested. Use when two agents or two sessions must hand narrative work to each other, when an architecture needs checking before drafting begins, when a draft must report a defect it cannot fix at its own layer, or when the user mentions han

Marketing, Sales & Business25

Valuation Consistency Checks

200

lyndonkl/claude

Checks a finished valuation for internal consistency across its artifacts — currency agreement between cash flows and discount rate, terminal growth against the riskfree ceiling, reinvestment that pays for the growth assumed, perpetual excess returns, capital weights and beta range, equity bridge arithmetic, tax rates, and the hard constraints a company's type imposes. Grades each finding ERROR, WARN or INFO and exits 1 on any error, so it can gate a pipeline. Use before accepting a DCF, when reviewing someone else's model, when a value looks too high, or when checking terminal value assumptio

Marketing, Sales & Business25

Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.