A skill library for storytelling & narratives — built for the AI era, installable into any AI agent.
A beat is the atomic unit of story: the smallest moment where a value shifts. BeatLib is a library of the moves that make narrative work.
Building is cheap now. A competent founder can generate a full Sequoia-format deck in an afternoon, and investors know it. What can't be generated is a decision that already cost something, an eval built from years of real data, a refusal that loses deals every month, a customer quoting you unprompted.
BeatLib is a library of portable Agent Skills that do one thing: excavate what a company has actually built, decided, and refused, and arrange it into a narrative someone can retell without you in the room. Each skill is a set of instructions any capable LLM can run — drop it into Claude Code, Cursor, Codex, or claude.ai and it runs the same.
The first two skills are pitch-story and story-architect. More are in the pipeline.
The npx skills add CLI scans the skills/ folder in this repo, so every skill below installs the same way.
Install everything:
npx skills add https://github.com/boldcapplatform/beatlibInstall a single skill by its install name (the name: field in the skill's frontmatter):
npx skills add https://github.com/boldcapplatform/beatlib --skill "pitch-story"This repo is also a Claude Code plugin marketplace. Add it once, then install:
/plugin marketplace add boldcapplatform/beatlib/plugin install beatlibEvery skill is a folder under skills/. Open its SKILL.md, paste it into your system prompt or context, and attach the skill's reference files when it asks for them (they load per phase, not upfront).
The Install name column is the exact value you pass to --skill.
| Skill (folder) | Install name | Description | Status |
|---|---|---|---|
pitch-story |
pitch-story |
Turns a founder's raw material into an investor pitch built as a chaptered story with technical depth and taste. | Stable |
story-architect |
story-architect |
Architects purposeful, influential narratives using research-backed and screenwriting frameworks, plus critique and script-doctor repair modes. | Stable |
Not a deck template. A skill that interviews a founder, excavates what they've actually built and refused, and arranges it into a chaptered story an investor can retell without the founder in the room.
- Graph engineering, not loop engineering. Everything the founder provides becomes typed nodes (facts, decisions, beliefs, unlocks, customer voices, world-states) with typed edges (caused, cost, proves, against). A belief with no proves edge is a claim, and claims get cut. The graph — not the deck — is the company's narrative asset: it re-cuts for the hire pitch, the launch post, the Series A.
- It communicates; it never strategizes. It presents what exists — it will not invent your GTM, your metrics, or your moat. Every section has a Context Bar; thin material gets an itemized Context Request instead of a plausible-sounding draft.
- What you get back: a three-sentence retell, a 60-second verbal pitch, a one-pager, a cold email, chaptered deck copy, a written memo, a technical appendix, a gap list of what you haven't lived yet — and a final Story Document as a single self-contained HTML file, print-ready for PDF.
Full documentation lives in skills/pitch-story/SKILL.md. Its eleven principles, in three acts, are the spine of the whole library.
A story architect for purposeful, influential narratives — brand stories, origin stories, pitch narratives, and scripts that change beliefs, not just entertain. It layers four bodies of craft, loaded on demand:
- Kendall Haven's story science — what the audience's brain requires, and how stories influence.
- Robert McKee's Story — how events, values, and choices under pressure produce meaning and emotion.
- Blake Snyder's Save the Cat — loglines, the 15-beat map, and blunt diagnostics.
- Marketing shapes — StoryBrand SB7, Hero's Journey, the Pixar formula, 3-Act Structure.
It interviews first, architects before drafting (audience, controlling idea, characters, influence line), and audits every draft against a ten-point Quality Bar. Two Story Doctor modes — Sully (merciless critic) and Milo (the fixer) — handle brutal audits and rescues.
Full documentation lives in skills/story-architect/SKILL.md.
More storytelling skills to follow. The pattern is deliberate: each skill excavates lived material and refuses to generate what the author hasn't earned.
Created by Siddharth Ram · BoldCap · X @siddharth_ram · LinkedIn · community@boldcap.com
The skill format follows the behavioral-guideline structure popularized by Andrej Karpathy's coding guidelines. Packaging follows the Agent Skills / Claude Code plugin conventions.
MIT — use it, fork it, ship it. If it helps you raise or tell a better story, tell a founder about it.