story-bank-builder

Compile and tag narrative assets with YAML frontmatter against claims and pillars.

2.5k|345|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/aaron-he-zhu/aaron-marketing-skills --skill story-bank-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-bank-builder
Source: https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/narrative/architect/story-bank-builder
Command: npx skills add https://github.com/aaron-he-zhu/aaron-marketing-skills --skill story-bank-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users compile a bank of reusable narrative units for marketing messages, ensuring consistency across all communication channels.

Core Features & Use Cases

  • Reusable Story Units: Assembles origin, founder, customer, transformation, and proof stories.
  • Tagging System: Tags each story to a claims-ledger ID and a message-house pillar.
  • Proof Labeling: Labels each proof as Measured, User-provided, or [needs source].
  • Use Case: Ideal for marketing professionals who need a repository of consistent stories to support their messaging and branding efforts.

Quick Start

Build a story bank for [product] from these customer interviews and case notes: [paste]. Tag each story to a pillar.

Frequently Asked Questions about story-bank-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a reusable story bank for marketing narratives?

To build a marketing story bank, you compile user-provided narrative assets and message house data, structuring them with YAML frontmatter and tagging each story to claims-ledger IDs and message-house pillars.

What is a narrative asset bank and how does it support branding?

A narrative asset bank is a structured repository of reusable story units—such as origin, founder, customer, and transformation stories—that ensures messaging consistency across all communication channels.

Do I need a message house to create a repository of customer stories?

Yes, you need message house data to map and tag each story to a specific pillar, ensuring your compiled narrative assets align directly with your broader messaging frameworks and branding strategy.

How do I organize proof stories for content creation and label their sources?

You organize proof stories by tagging them to claims-ledger IDs and labeling each proof as Measured, User-provided, or [needs source], clarifying the validity of your marketing narratives.

What is the best way to structure marketing narratives for consistent reuse?

The best way to structure narratives for reuse is using YAML frontmatter to store story data, tagging each unit against claims and message-house pillars for consistent retrieval across channels.

Are there limitations when assembling a story bank from case notes?

A key limitation is that the story bank requires you to provide existing narrative assets and message house data; it cannot generate original stories or messaging frameworks from scratch.