Agent skill · Content & Marketing

story-bank-builder

Use when the user asks to "build a story bank", "collect our origin and customer stories", or "assemble reusable proof stories for the message"; assembles reusable narrative units — origin, founder, customer, transformation, and proof stories — each tagged to a claims-ledger ID and a message-house pillar, with every proof labeled Measured / User-provided / [needs source]. Not for authoring the message house or pillars — use message-system-architect; not for brand voice or naming rules — use brand-language-codifier; not for finished long-form prose — use content-writer; not for adjudicating whe

aaron-he-zhugithub.com/aaron-he-zhuGitHub ↗
claude-codeApache-2.0
Install
npx skills add aaron-he-zhu/aaron-marketing-skills --skill story-bank-builder --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 12 KB
Bundled scripts: none
Version: 19.1.0
Requires: Claude Code and compatible agent-skill hosts
Path: narrative/architect/story-bank-builder/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,508
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Story Bank Builder Assembles the brand's reusable **story bank** — origin, founder, customer, transformation, and proof stories drawn from real interview and case material — each unit tagged to a claims-ledger ID and to a message-house pillar so downstream surfaces pull a consistent, sourced story instead of improvising one. It is the fourth move of the TALE **Architect** phase and feeds two dimensions of [tale-benchmark.md](../../../references/tale-benchmark.md): the `A` *story raw material* behind the strategic narrative arc, and the `E` *proof-point assets exist for each pillar* sub-item (case, benchmark, demo, or testimonial the user has rights to). Every proof inside a story is labeled Measured / User-provided / `[needs source]`; an unverified proof is marked `[needs source]` and submitted to `memory/events/claims.ndjson` via an authorized `operation: propose` request to `registry-events.py` — this skill never adjudicates whether a proof is true. **Scope guard**: this skill produces the story bank *document* only. It does **not** author the message house, pillars, or tagline (that is [message-system-architect](../message-system-architect/SKILL.md) — if no pillars exist to ta

What's inside
Steps it walks through
  1. Quick Start
  2. Skill Contract
  3. Handoff Summary
  4. Data Sources
  5. Instructions
  6. Save Results
  7. Reference Materials
  8. Next Best Skill
More from aaron-marketing-skills
All skills →
About this skill
What does the story-bank-builder skill do?

Use when the user asks to "build a story bank", "collect our origin and customer stories", or "assemble reusable proof stories for the message"; assembles reusable narrative units — origin, founder, customer, transformation, and proof stories — each tagged to a claims-ledger ID and a message-house pillar, with every proof labeled Measured / User-provided / [needs source]. Not for authoring the message house or pillars — use message-system-architect; not for brand voice or naming rules — use brand-language-codifier; not for finished long-form prose — use content-writer; not for adjudicating whe

How do I install it?

Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill story-bank-builder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going