New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Clarify brand messaging using narrative structure

StoryBrand Messaging Framework

by wondelai · MIT license · ★ 2,235 on GitHub · updated Sep 10

StoryBrand Messaging Framework cover

Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions "brand message", "website copy", "elevator pitch", "one-liner", "brand script", "StoryBrand framework", "customer as…

---
name: storybrand-messaging
description: 'Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions "brand message", "website copy", "elevator pitch", "one-liner", "brand script", "StoryBrand framework", "customer as hero", or "my messaging isnt resonating". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales and marketing collateral. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.'
license: MIT
metadata:
  author: wondelai
  version: "1.5.0"
---

# StoryBrand Messaging Framework

Clarify your message so customers will listen. Customers don't buy the best products — they buy the ones they can understand the fastest.

## Core Principle

**The customer is the hero, not your brand.** Your brand is the guide who helps the hero win. Position yourself as the hero and you compete with your customer; position yourself as the guide and you serve them.

## Scoring

Overview

Clarify your message so customers will listen. Customers don't buy the best products — they buy the ones they can understand the fastest.

Manual install (npx, ZIP)
Claude Codenpx skills add wondelai/skills --skill storybrand-messaging -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/wondelai/skills/tar.gz/c172996495be \ | tar -xz -C ~/.claude/skills --strip-components=4 skills-c172996495be/plugins/marketing-cro/skills/storybrand-messaging
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/93b519ed016fb7c0061e/storybrand-messaging.zip" -OutFile "$env:TEMP\storybrand-messaging.zip"; Expand-Archive "$env:TEMP\storybrand-messaging.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md14.5 KB
  • references/6 files · 63.6 KB
Read the files here
wondelai/c1729967 files
SKILL.md
Show the full text260 lines

StoryBrand Messaging Framework

Clarify your message so customers will listen. Customers don't buy the best products — they buy the ones they can understand the fastest.

Core Principle

The customer is the hero, not your brand. Your brand is the guide who helps the hero win. Position yourself as the hero and you compete with your customer; position yourself as the guide and you serve them.

Scoring

Goal: 10/10. Score any marketing copy or brand messaging by the Quick Diagnostic: 1 point per satisfied row (7 rows) plus up to 3 points for a one-liner that passes the cocktail party test (clear + repeatable in one hearing). Bands: 9-10 = customer is the hero, all three problem levels named, empathy + authority both shown, a 3-step plan, one obvious Direct CTA, and both success and failure stakes painted; 5-6 = SB7 partly applied but the internal problem, stakes, or CTA is missing; <=3 = brand-as-hero, feature-led, or no clear ask. Always state the current score and the specific changes needed to reach 10/10.

The SB7 Framework

Every compelling story follows the same pattern. Use this structure for all messaging:

1. A Character (The Hero)

Core concept: The customer is the hero, and your job is to define the ONE thing they want. Be specific about that single desire.

Why it works: Naming a desire opens a story gap — the distance between where the customer is and where they want to be. That tension pulls them in because they feel understood and want the gap closed.

Key insights:

  • Focus on ONE desire per message — multiple desires dilute the story gap
  • Tie the desire to survival (physical, financial, relational, or spiritual)
  • Aspirational identity is powerful ("become the leader everyone respects")
  • Different segments have different desires — write separate messaging per role, stage, and pain intensity

Product applications:

Context Application Example
Homepage headline Desire as outcome "You want a beautiful smile" (not "our dentistry is excellent")
Landing page One desire per page "You want to retire early"
Segmentation Tailor desire per segment CEO: "Scale without chaos" vs. IC: "Do your best work without friction"

Copy patterns:

  • "You want [specific desire]..."
  • "Imagine [aspirational identity]..."
  • "What if you could [single clear outcome]?"

See: references/brand-script.md — fill out the BrandScript worksheet here when you need to draft all seven elements for a client from scratch.

2. Has a Problem

Core concept: Define the problem at three levels — external (tangible), internal (emotional), philosophical (the injustice) — and personify it with a specific villain.

Why it works: Companies sell solutions to external problems, but customers buy solutions to internal ones. Naming how the problem makes them feel — confused, overwhelmed, embarrassed — taps the emotional driver behind purchases.

Key insights:

  • External: "my investments are scattered"; internal: "I feel overwhelmed"; philosophical: "people shouldn't need to be experts to retire well"
  • A good villain is specific and relatable, not abstract — "Wall Street jargon designed to confuse you", not "complexity"
  • Most brands stop at external problems, missing the internal ones that drive purchases

Product applications:

Context Application Example
Website problem section Name all three levels External: "Scattered tools." Internal: "You feel overwhelmed." Philosophical: "Teams deserve clarity."
Email nurture Lead with internal problem "Tired of feeling like you're guessing?"
Ad copy Personify the villain "Stop letting confusing software steal your evenings."

Copy patterns:

  • "You're tired of [internal problem]..."
  • "[Villain] has been keeping you from [desire]..."
  • "It's not right that [philosophical problem]..."
3. And Meets a Guide

Core concept: Your brand is the guide, expressing empathy AND authority. Empathy shows you understand the pain; authority proves you can solve it.

Why it works: Customers are looking for a guide, not another hero — think Yoda, not Luke. Empathy makes them feel seen, authority (testimonials, logos, statistics) makes them feel safe, and together they create trust.

Key insights:

  • Show empathy with "we understand" language; show authority with testimonials, client logos, statistics, awards
  • Never make your origin story the centerpiece — that is hero behavior; brief, relevant credentials suffice

Product applications:

Context Application Example
About page Empathy first, then credentials "We know what it's like to feel lost in financial jargon. That's why 10,000 families trust us."
Homepage social proof Empathy headline + authority logos "You're not alone. Join 5,000+ teams who found clarity." + client logos
Sales call Open with empathy, close with authority "I hear you — that sounds frustrating. Here's what we've seen work for teams like yours."

Copy patterns:

  • "We understand what it's like to [empathy statement]..."
  • "We've helped [number] [customers] achieve [result]..."
  • "You don't have to figure this out alone..."

See: references/sales-conversations.md — open when scripting a sales call or discovery session; covers discovery questions, objection handling, and full SB7 sales scripts.

4. Who Gives Them a Plan

Core concept: Give two plans: a Process Plan (3-4 steps showing how to work with you) and an Agreement Plan (commitments that remove risk).

Why it works: A clear plan acts as stepping stones across a creek — it reduces cognitive load and perceived risk. Without one, the path feels murky and customers stall.

Key insights:

  • Process Plan: 3-4 numbered steps max, action verbs, memorable names ("1. Schedule a call. 2. Get a custom plan. 3. Start seeing results.")
  • Agreement Plan: fear-removing commitments ("100% satisfaction guaranteed", "Cancel anytime")
  • More than 4 steps overwhelms; numbering implies order and ease

Product applications:

Context Application Example
Website plan section 3-step process with icons "1. Book a demo. 2. Get onboarded. 3. See results in 30 days."
Pricing page Agreement plan reduces anxiety "No contracts. Cancel anytime. 30-day money-back guarantee."
Email CTA Reference the plan "Getting started is simple — just three steps."

Copy patterns:

  • "Here's how it works: Step 1... Step 2... Step 3..."
  • "Getting started is easy. Just [step 1]."
  • "We promise [agreement plan commitment]."
5. And Calls Them to Action

Core concept: If you don't ask, they won't act. Use a Direct CTA (primary conversion action) plus a Transitional CTA (lower-commitment alternative).

Why it works: Customers act only when challenged to act. The transitional CTA keeps not-yet-ready people in your story until they are.

Key insights:

  • Direct: "Buy Now", "Schedule a Call", "Get Started"; Transitional: "Download Free Guide", "Watch Demo", "Take the Quiz"
  • Make the Direct CTA a visually prominent button (contrasting color) and repeat it down the page
  • Use action language ("Get" not "Submit"); one obvious Direct CTA per page

Product applications:

Context Application Example
Homepage Direct CTA above the fold, repeated "Get Started Free" in header and after each section
Blog post Transitional CTA at the end "Download our free checklist"
Email Single Direct CTA per message One "Schedule Your Call" button

Copy patterns:

  • "Get [desired result] now."
  • "Start your free [trial/demo/assessment] today."
  • "Download your free [lead magnet]."

Ethical boundary: Never label a paid action as "free" or a Transitional CTA — the button text must match what happens on click.

See: references/website-wireframe.md — open when laying out a homepage or site; gives section-by-section structure and interior page templates.

6. That Helps Them Avoid Failure

Core concept: Show what happens if the customer does not act. Without stakes, there is no story.

Why it works: Humans are loss-averse — fear of losing motivates more than promise of gaining. A taste of what could go wrong moves customers from "interested" to "committed".

Key insights:

  • A taste of consequence is enough — don't run a scare campaign
  • Focus on opportunity cost, not punishment ("another year of feeling stuck")
  • Pair failure with success messaging to create contrast

Product applications:

Context Application Example
Landing page stakes section Brief failure scenario before CTA "Without a clear message, you'll keep losing customers to competitors they understand faster."
Email subject line Light urgency "Are you leaving revenue on the table?"
Sales conversation Name cost of inaction "What happens to your team if nothing changes in 6 months?"

Copy patterns:

  • "Don't let [negative outcome] happen when [solution] is this simple."
  • "How long will you wait before [addressing the problem]?"
  • "Every day without [solution], you're [cost of inaction]."
7. And Ends in Success

Core concept: Paint a vivid picture of life after working with you — in terms of status, completeness, and self-realization. Success closes the story gap opened in Element 1.

Why it works: People need to see the destination before starting the journey. Showing the transformation — not features — lets customers place themselves in that future and feel its pull.

Key insights:

  • Status: "Become the go-to expert"; completeness: "Finally have financial peace of mind"; self-realization: "Be the leader you were meant to be"
  • Show transformation with before/after comparisons and specific numbers
  • Keep the success picture tangible, never vague or generic

Product applications:

Context Application Example
Homepage success section Specific after picture "Imagine opening your inbox to qualified leads every morning — no cold outreach required."
Case study Before/after with numbers "Before: 2% conversion rate. After: 11% in 90 days."
Testimonials Customers describe their success "I finally feel like I know where every dollar is going."

Copy patterns:

  • "Imagine [specific success picture]..."
  • "Join [number] [customers] who now [success outcome]..."
  • "Finally, [completeness outcome] — without [old frustration]."

The One-Liner

A single sentence that explains what you do. Use it everywhere.

Formula: [Problem] + [Solution] + [Result]

Structure: "We help [CHARACTER] who struggle with [PROBLEM] to [SOLUTION] so they can [RESULT]."

Example: "We help small business owners who feel overwhelmed by marketing create a clear message so they can grow their revenue."

Test: Can someone repeat it after hearing it once? (the cocktail party test)

See: references/one-liners.md — open when drafting a one-liner; ~20 industry examples plus three alternative formulas (PSR, BAB, "We Exist Because").

Tone and Voice Guidelines

Keep brand voice consistent across channels while adapting to context.

Convey guide qualities: empathy ("We understand..."), authority ("In our experience..."), confidence ("Here's what works..."), helpfulness ("Let us show you...").

Avoid: hero language ("We're the best at..."), jargon (use the customer's words), condescension, and tentative weakness.

See: references/email-sequences.md — open when building a nurture or welcome sequence; SB7-mapped templates and subject-line formulas. See: references/multi-channel-consistency.md — open when adapting the message to a channel; social, video, podcast, and PR playbooks.

Common Mistakes

Mistake Why It Fails Fix
Being the hero Competes with customer Position as guide
Multiple messages Confuses people One clear message per asset
Clever > clear People don't decode messaging Choose clarity always
Feature-focused Customers buy transformation Lead with outcomes
No clear CTA No direction = no action Ask for the sale
No stakes No urgency = no motivation Paint failure picture
Starting with "We" Self-focused Start with customer's problem

Quick Diagnostic

Question If No Action
Can a caveman grasp the offer in 5 seconds? Message too complex Simplify to one desire, one outcome
Is the customer clearly the hero? Brand competes with customer Rewrite from customer's perspective
Is the internal problem named, not just external? Missing the emotional driver Add "how it feels" language
Do you show empathy AND authority? Trust gap Add "we understand" + proof points
Is there a clear 3-step plan? Path feels risky Add Process + Agreement plans
Is there one obvious CTA? Nobody acts Add prominent, repeated Direct CTA
Do you show success AND failure stakes? No narrative tension Paint both outcome pictures

Further Reading

For the complete methodology and worksheets:

About the Author

Donald Miller is the CEO of StoryBrand, which has helped over 10,000 businesses clarify their messaging. A New York Times bestselling author of Building a StoryBrand, Marketing Made Simple, and Business Made Simple, he distilled decades of narrative theory into the practical seven-part SB7 framework.

1---
2name: storybrand-messaging
3description: 'Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions "brand message", "website copy", "elevator pitch", "one-liner", "brand script", "StoryBrand framework", "customer as hero", or "my messaging isnt resonating". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales and marketing collateral. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.'
4license: MIT
5metadata:
6 author: wondelai
7 version: "1.5.0"
8---
9 
10# StoryBrand Messaging Framework
11 
12Clarify your message so customers will listen. Customers don't buy the best products — they buy the ones they can understand the fastest.
13 
14## Core Principle
15 
16**The customer is the hero, not your brand.** Your brand is the guide who helps the hero win. Position yourself as the hero and you compete with your customer; position yourself as the guide and you serve them.
17 
18## Scoring
19 
20**Goal: 10/10.** Score any marketing copy or brand messaging by the Quick Diagnostic: 1 point per satisfied row (7 rows) plus up to 3 points for a one-liner that passes the cocktail party test (clear + repeatable in one hearing). Bands: 9-10 = customer is the hero, all three problem levels named, empathy + authority both shown, a 3-step plan, one obvious Direct CTA, and both success and failure stakes painted; 5-6 = SB7 partly applied but the internal problem, stakes, or CTA is missing; <=3 = brand-as-hero, feature-led, or no clear ask. Always state the current score and the specific changes needed to reach 10/10.
21 
22## The SB7 Framework
23 
24Every compelling story follows the same pattern. Use this structure for all messaging:
25 
26### 1. A Character (The Hero)
27 
28**Core concept:** The customer is the hero, and your job is to define the ONE thing they want. Be specific about that single desire.
29 
30**Why it works:** Naming a desire opens a story gap — the distance between where the customer is and where they want to be. That tension pulls them in because they feel understood and want the gap closed.
31 
32**Key insights:**
33- Focus on ONE desire per message — multiple desires dilute the story gap
34- Tie the desire to survival (physical, financial, relational, or spiritual)
35- Aspirational identity is powerful ("become the leader everyone respects")
36- Different segments have different desires — write separate messaging per role, stage, and pain intensity
37 
38**Product applications:**
39 
40| Context | Application | Example |
41|---------|-------------|---------|
42| Homepage headline | Desire as outcome | "You want a beautiful smile" (not "our dentistry is excellent") |
43| Landing page | One desire per page | "You want to retire early" |
44| Segmentation | Tailor desire per segment | CEO: "Scale without chaos" vs. IC: "Do your best work without friction" |
45 
46**Copy patterns:**
47- "You want [specific desire]..."
48- "Imagine [aspirational identity]..."
49- "What if you could [single clear outcome]?"
50 
51See: [references/brand-script.md](references/brand-script.md) — fill out the BrandScript worksheet here when you need to draft all seven elements for a client from scratch.
52 
53### 2. Has a Problem
54 
55**Core concept:** Define the problem at three levels — external (tangible), internal (emotional), philosophical (the injustice) — and personify it with a specific villain.
56 
57**Why it works:** Companies sell solutions to external problems, but customers buy solutions to internal ones. Naming how the problem makes them feel — confused, overwhelmed, embarrassed — taps the emotional driver behind purchases.
58 
59**Key insights:**
60- External: "my investments are scattered"; internal: "I feel overwhelmed"; philosophical: "people shouldn't need to be experts to retire well"
61- A good villain is specific and relatable, not abstract — "Wall Street jargon designed to confuse you", not "complexity"
62- Most brands stop at external problems, missing the internal ones that drive purchases
63 
64**Product applications:**
65 
66| Context | Application | Example |
67|---------|-------------|---------|
68| Website problem section | Name all three levels | External: "Scattered tools." Internal: "You feel overwhelmed." Philosophical: "Teams deserve clarity." |
69| Email nurture | Lead with internal problem | "Tired of feeling like you're guessing?" |
70| Ad copy | Personify the villain | "Stop letting confusing software steal your evenings." |
71 
72**Copy patterns:**
73- "You're tired of [internal problem]..."
74- "[Villain] has been keeping you from [desire]..."
75- "It's not right that [philosophical problem]..."
76 
77### 3. And Meets a Guide
78 
79**Core concept:** Your brand is the guide, expressing empathy AND authority. Empathy shows you understand the pain; authority proves you can solve it.
80 
81**Why it works:** Customers are looking for a guide, not another hero — think Yoda, not Luke. Empathy makes them feel seen, authority (testimonials, logos, statistics) makes them feel safe, and together they create trust.
82 
83**Key insights:**
84- Show empathy with "we understand" language; show authority with testimonials, client logos, statistics, awards
85- Never make your origin story the centerpiece — that is hero behavior; brief, relevant credentials suffice
86 
87**Product applications:**
88 
89| Context | Application | Example |
90|---------|-------------|---------|
91| About page | Empathy first, then credentials | "We know what it's like to feel lost in financial jargon. That's why 10,000 families trust us." |
92| Homepage social proof | Empathy headline + authority logos | "You're not alone. Join 5,000+ teams who found clarity." + client logos |
93| Sales call | Open with empathy, close with authority | "I hear you — that sounds frustrating. Here's what we've seen work for teams like yours." |
94 
95**Copy patterns:**
96- "We understand what it's like to [empathy statement]..."
97- "We've helped [number] [customers] achieve [result]..."
98- "You don't have to figure this out alone..."
99 
100See: [references/sales-conversations.md](references/sales-conversations.md) — open when scripting a sales call or discovery session; covers discovery questions, objection handling, and full SB7 sales scripts.
101 
102### 4. Who Gives Them a Plan
103 
104**Core concept:** Give two plans: a Process Plan (3-4 steps showing how to work with you) and an Agreement Plan (commitments that remove risk).
105 
106**Why it works:** A clear plan acts as stepping stones across a creek — it reduces cognitive load and perceived risk. Without one, the path feels murky and customers stall.
107 
108**Key insights:**
109- Process Plan: 3-4 numbered steps max, action verbs, memorable names ("1. Schedule a call. 2. Get a custom plan. 3. Start seeing results.")
110- Agreement Plan: fear-removing commitments ("100% satisfaction guaranteed", "Cancel anytime")
111- More than 4 steps overwhelms; numbering implies order and ease
112 
113**Product applications:**
114 
115| Context | Application | Example |
116|---------|-------------|---------|
117| Website plan section | 3-step process with icons | "1. Book a demo. 2. Get onboarded. 3. See results in 30 days." |
118| Pricing page | Agreement plan reduces anxiety | "No contracts. Cancel anytime. 30-day money-back guarantee." |
119| Email CTA | Reference the plan | "Getting started is simple — just three steps." |
120 
121**Copy patterns:**
122- "Here's how it works: Step 1... Step 2... Step 3..."
123- "Getting started is easy. Just [step 1]."
124- "We promise [agreement plan commitment]."
125 
126### 5. And Calls Them to Action
127 
128**Core concept:** If you don't ask, they won't act. Use a Direct CTA (primary conversion action) plus a Transitional CTA (lower-commitment alternative).
129 
130**Why it works:** Customers act only when challenged to act. The transitional CTA keeps not-yet-ready people in your story until they are.
131 
132**Key insights:**
133- Direct: "Buy Now", "Schedule a Call", "Get Started"; Transitional: "Download Free Guide", "Watch Demo", "Take the Quiz"
134- Make the Direct CTA a visually prominent button (contrasting color) and repeat it down the page
135- Use action language ("Get" not "Submit"); one obvious Direct CTA per page
136 
137**Product applications:**
138 
139| Context | Application | Example |
140|---------|-------------|---------|
141| Homepage | Direct CTA above the fold, repeated | "Get Started Free" in header and after each section |
142| Blog post | Transitional CTA at the end | "Download our free checklist" |
143| Email | Single Direct CTA per message | One "Schedule Your Call" button |
144 
145**Copy patterns:**
146- "Get [desired result] now."
147- "Start your free [trial/demo/assessment] today."
148- "Download your free [lead magnet]."
149 
150**Ethical boundary:** Never label a paid action as "free" or a Transitional CTA — the button text must match what happens on click.
151 
152See: [references/website-wireframe.md](references/website-wireframe.md) — open when laying out a homepage or site; gives section-by-section structure and interior page templates.
153 
154### 6. That Helps Them Avoid Failure
155 
156**Core concept:** Show what happens if the customer does not act. Without stakes, there is no story.
157 
158**Why it works:** Humans are loss-averse — fear of losing motivates more than promise of gaining. A taste of what could go wrong moves customers from "interested" to "committed".
159 
160**Key insights:**
161- A taste of consequence is enough — don't run a scare campaign
162- Focus on opportunity cost, not punishment ("another year of feeling stuck")
163- Pair failure with success messaging to create contrast
164 
165**Product applications:**
166 
167| Context | Application | Example |
168|---------|-------------|---------|
169| Landing page stakes section | Brief failure scenario before CTA | "Without a clear message, you'll keep losing customers to competitors they understand faster." |
170| Email subject line | Light urgency | "Are you leaving revenue on the table?" |
171| Sales conversation | Name cost of inaction | "What happens to your team if nothing changes in 6 months?" |
172 
173**Copy patterns:**
174- "Don't let [negative outcome] happen when [solution] is this simple."
175- "How long will you wait before [addressing the problem]?"
176- "Every day without [solution], you're [cost of inaction]."
177 
178### 7. And Ends in Success
179 
180**Core concept:** Paint a vivid picture of life after working with you — in terms of status, completeness, and self-realization. Success closes the story gap opened in Element 1.
181 
182**Why it works:** People need to see the destination before starting the journey. Showing the transformation — not features — lets customers place themselves in that future and feel its pull.
183 
184**Key insights:**
185- Status: "Become the go-to expert"; completeness: "Finally have financial peace of mind"; self-realization: "Be the leader you were meant to be"
186- Show transformation with before/after comparisons and specific numbers
187- Keep the success picture tangible, never vague or generic
188 
189**Product applications:**
190 
191| Context | Application | Example |
192|---------|-------------|---------|
193| Homepage success section | Specific after picture | "Imagine opening your inbox to qualified leads every morning — no cold outreach required." |
194| Case study | Before/after with numbers | "Before: 2% conversion rate. After: 11% in 90 days." |
195| Testimonials | Customers describe their success | "I finally feel like I know where every dollar is going." |
196 
197**Copy patterns:**
198- "Imagine [specific success picture]..."
199- "Join [number] [customers] who now [success outcome]..."
200- "Finally, [completeness outcome] — without [old frustration]."
201 
202## The One-Liner
203 
204A single sentence that explains what you do. Use it everywhere.
205 
206**Formula:** `[Problem] + [Solution] + [Result]`
207 
208**Structure:** "We help [CHARACTER] who struggle with [PROBLEM] to [SOLUTION] so they can [RESULT]."
209 
210**Example:** "We help small business owners who feel overwhelmed by marketing create a clear message so they can grow their revenue."
211 
212**Test:** Can someone repeat it after hearing it once? (the cocktail party test)
213 
214See: [references/one-liners.md](references/one-liners.md) — open when drafting a one-liner; ~20 industry examples plus three alternative formulas (PSR, BAB, "We Exist Because").
215 
216## Tone and Voice Guidelines
217 
218Keep brand voice consistent across channels while adapting to context.
219 
220**Convey guide qualities:** empathy ("We understand..."), authority ("In our experience..."), confidence ("Here's what works..."), helpfulness ("Let us show you...").
221 
222**Avoid:** hero language ("We're the best at..."), jargon (use the customer's words), condescension, and tentative weakness.
223 
224See: [references/email-sequences.md](references/email-sequences.md) — open when building a nurture or welcome sequence; SB7-mapped templates and subject-line formulas.
225See: [references/multi-channel-consistency.md](references/multi-channel-consistency.md) — open when adapting the message to a channel; social, video, podcast, and PR playbooks.
226 
227## Common Mistakes
228 
229| Mistake | Why It Fails | Fix |
230|---------|-------------|-----|
231| Being the hero | Competes with customer | Position as guide |
232| Multiple messages | Confuses people | One clear message per asset |
233| Clever > clear | People don't decode messaging | Choose clarity always |
234| Feature-focused | Customers buy transformation | Lead with outcomes |
235| No clear CTA | No direction = no action | Ask for the sale |
236| No stakes | No urgency = no motivation | Paint failure picture |
237| Starting with "We" | Self-focused | Start with customer's problem |
238 
239## Quick Diagnostic
240 
241| Question | If No | Action |
242|----------|-------|--------|
243| Can a caveman grasp the offer in 5 seconds? | Message too complex | Simplify to one desire, one outcome |
244| Is the customer clearly the hero? | Brand competes with customer | Rewrite from customer's perspective |
245| Is the internal problem named, not just external? | Missing the emotional driver | Add "how it feels" language |
246| Do you show empathy AND authority? | Trust gap | Add "we understand" + proof points |
247| Is there a clear 3-step plan? | Path feels risky | Add Process + Agreement plans |
248| Is there one obvious CTA? | Nobody acts | Add prominent, repeated Direct CTA |
249| Do you show success AND failure stakes? | No narrative tension | Paint both outcome pictures |
250 
251## Further Reading
252 
253For the complete methodology and worksheets:
254 
255- [*"Building a StoryBrand: Clarify Your Message So Customers Will Listen"*](https://www.amazon.com/Building-StoryBrand-Clarify-Message-Customers/dp/0718033329?tag=wondelai00-20) by Donald Miller
256 
257## About the Author
258 
259Donald Miller is the CEO of StoryBrand, which has helped over 10,000 businesses clarify their messaging. A New York Times bestselling author of *Building a StoryBrand*, *Marketing Made Simple*, and *Business Made Simple*, he distilled decades of narrative theory into the practical seven-part SB7 framework.
260 
View all files on GitHub →

Details

Updated
Sep 10, 2026
License
MIT
Stars on the repo
★ 2,235
Checked
Source
wondelai/skills ↗
Creator
wondelai · 320 listings
View creator

Similar skills

See all →
SkillAnalyze active ads from Meta/Facebook, GoogleAd library teardownScrapeCreators/social-media-research-skills · by ScrapeCreatorsUse when the user wants to analyze active ads from Meta/Facebook, Google, or LinkedIn ad libraries; tear down a competitor's messaging; extract hooks, offers, CTAs, video transcripts, landing page claims, and test ideas from public ads.★ 2.6k GitHub starsSkillTurn product materials into listing visuals for Taobao, JDEcommerce visual copywritingfeichanggege/ecommerce-visual-copywriting-skill · by feichanggegeTurn product materials into listing visuals for Taobao, JD, Douyin, Amazon, Shopify and TikTok Shop: main-image and detail-page storyboards, in-image copy, image prompts, plus an evidence and ad-compliance check.★ 985 GitHub starsSkillTell us about your plans and pricesPricing Page (High‑Conversion) — Web Design Skillboraoztunc/skills · by Meng ToTell us about your plans and prices, and get back a ready-to-build pricing page: plan layout, what each tier includes, buttons, and answers to common buyer questions.★ 361 GitHub starsSkillWrites opening hooks and post titles for long-form articlesCopywriting hookssamber/cc-skills · by samberWrites opening hooks and post titles for long-form articles in EN or FR — blog posts, Substack/Medium/dev.to, LinkedIn long-form, newsletters, essays. Trigger whenever the user asks for a hook, opening, lede, intro, first sentence/paragraph, opener, accroche, attaque, phrase d'accroche, or première phrase — including punching up a flat intro or draft opening — or for a post title, titre d'article, or headline. Do NOT trigger for social posts (LinkedIn feed, Twitter/X, TikTok, Bluesky), READMEs, taglines, email subjects, ad copy, landing-page headlines, press releases, SEO meta, or body rewrites. Do NOT use for end-of-article CTAs — use samber/cc-skills@copywriting-cta instead.★ 222 GitHub starsSkillSomeone wants landing page ideas, conceptsEcom landing pageskgelster/awesome-ecom-skills · by kgelsterUse when someone wants landing page ideas, concepts, or angles for a store: give me landing page concepts", "LP ideas", "landing page angles", a campaign or ad landing page, pages for a new audience/segment, a seasonal/event/promo page, or a geo/local page. Also use when a chosen concept gets picked and needs building out into an actual page (section-by-section blueprint), or when auditing an existing landing page against best practice. The core insight: one product becomes dozens of pages by varying the ANGLE, not the product. Not for full-site information architecture, product detail pages, collection pages, or blog/SEO content (a landing page has ONE goal, no site chrome). Use an SEO/content skill. Not for the ad or email creative itself, though message match with the page matters.★ 49 GitHub starsSkillWrite sales pages, email sequencesEW Skill — Sales CopyDeupaxx/EveryDay-Writer · by DeupaxxWrite sales pages, email sequences, and direct-response copy that converts through clarity and specificity rather than manipulation. Use for launches, offers, and conversion-focused email. Enforces the EW anti-AI rules, proof standards, and the writer's voice profile.★ 32 GitHub stars

More from wondelai

SkillManage software complexity through deep modulesA Philosophy of Software Design Frameworkwondelai/skills · by wondelaiManage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", "pass-through method", "this code is over-engineered", or "simplify this design". Also trigger when reviewing an interface for simplicity, evaluating whether an abstraction is pulling its weight, deciding whether a comment is worth writing, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For architecture boundaries, see clean-architecture.★ 2.2k GitHub starsSkillMetrics are the language of validated learningActionable metrics guidewondelai/skills · by wondelaiMetrics are the language of validated learning. The wrong metrics create the illusion of progress while the startup drifts toward failure.…★ 2.2k GitHub starsSkillAdvertising media is the vehicle that carries your messagewondelai/skills · by wondelaiAdvertising media is the vehicle that carries your message to your target market. Choosing the right media is not about what is trendy — it…★ 2.2k GitHub starsSkillAn affordance is a relationship between an objectAffordances: Designing for Actionwondelai/skills · by wondelaiAn affordance is a relationship between an object and a person that determines how the object could possibly be used. A chair affords…★ 2.2k GitHub starsSkillLean UX was designed to work inside Agile development teamsAgile integration for lean UXwondelai/skills · by wondelaiLean UX was designed to work inside Agile development teams, not alongside them. The central mechanism is dual-track agile, where a…★ 2.2k GitHub starsSkillThis reference translates the AMP framework from theoryAMP Applied: Practical Applications of Autonomy, Mastery, and Purposewondelai/skills · by wondelaiThis reference translates the AMP framework from theory into practice across six domains: product gamification, team management,…★ 2.2k GitHub stars