SKILL·213134

storybrand-messaging

wondelai
更新于 Yesterday
1,896
193
1,896
在 GitHub 上查看
ai

关于

This skill helps developers clarify brand messaging by applying the StoryBrand framework, which structures narratives to position the customer as the hero. It's triggered for tasks like rewriting website copy, crafting pitches, or ensuring consistent messaging across marketing collateral. The skill focuses on transforming how a brand communicates as a guide to the customer's story.

快速安装

Claude Code

推荐
主要方式
npx skills add wondelai/skills -a claude-code
插件命令备选方式
/plugin add https://github.com/wondelai/skills
Git 克隆备选方式
git clone https://github.com/wondelai/skills.git ~/.claude/skills/storybrand-messaging

在 Claude Code 中复制并粘贴此命令以安装该技能

技能文档

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:

ContextApplicationExample
Homepage headlineDesire as outcome"You want a beautiful smile" (not "our dentistry is excellent")
Landing pageOne desire per page"You want to retire early"
SegmentationTailor desire per segmentCEO: "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:

ContextApplicationExample
Website problem sectionName all three levelsExternal: "Scattered tools." Internal: "You feel overwhelmed." Philosophical: "Teams deserve clarity."
Email nurtureLead with internal problem"Tired of feeling like you're guessing?"
Ad copyPersonify 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:

ContextApplicationExample
About pageEmpathy 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 proofEmpathy headline + authority logos"You're not alone. Join 5,000+ teams who found clarity." + client logos
Sales callOpen 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:

ContextApplicationExample
Website plan section3-step process with icons"1. Book a demo. 2. Get onboarded. 3. See results in 30 days."
Pricing pageAgreement plan reduces anxiety"No contracts. Cancel anytime. 30-day money-back guarantee."
Email CTAReference 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:

ContextApplicationExample
HomepageDirect CTA above the fold, repeated"Get Started Free" in header and after each section
Blog postTransitional CTA at the end"Download our free checklist"
EmailSingle Direct CTA per messageOne "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:

ContextApplicationExample
Landing page stakes sectionBrief failure scenario before CTA"Without a clear message, you'll keep losing customers to competitors they understand faster."
Email subject lineLight urgency"Are you leaving revenue on the table?"
Sales conversationName 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:

ContextApplicationExample
Homepage success sectionSpecific after picture"Imagine opening your inbox to qualified leads every morning — no cold outreach required."
Case studyBefore/after with numbers"Before: 2% conversion rate. After: 11% in 90 days."
TestimonialsCustomers 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

MistakeWhy It FailsFix
Being the heroCompetes with customerPosition as guide
Multiple messagesConfuses peopleOne clear message per asset
Clever > clearPeople don't decode messagingChoose clarity always
Feature-focusedCustomers buy transformationLead with outcomes
No clear CTANo direction = no actionAsk for the sale
No stakesNo urgency = no motivationPaint failure picture
Starting with "We"Self-focusedStart with customer's problem

Quick Diagnostic

QuestionIf NoAction
Can a caveman grasp the offer in 5 seconds?Message too complexSimplify to one desire, one outcome
Is the customer clearly the hero?Brand competes with customerRewrite from customer's perspective
Is the internal problem named, not just external?Missing the emotional driverAdd "how it feels" language
Do you show empathy AND authority?Trust gapAdd "we understand" + proof points
Is there a clear 3-step plan?Path feels riskyAdd Process + Agreement plans
Is there one obvious CTA?Nobody actsAdd prominent, repeated Direct CTA
Do you show success AND failure stakes?No narrative tensionPaint 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.

GitHub 仓库

wondelai/skills
路径: plugins/wondelai-skills/skills/storybrand-messaging
0
agent-skillsai-skillsbusinessclaude-codeclaude-code-marketplaceclaude-code-plugin
FAQ

常见问题

什么是 storybrand-messaging Skill?

storybrand-messaging 是一个 Claude Skill,作者为 wondelai。Skill 将 Claude 按需加载的说明和资源打包,让 Claude 无需额外提示即可执行与 storybrand-messaging 相关的任务。

如何安装 storybrand-messaging?

使用本页的安装命令:将 storybrand-messaging 作为插件添加到 Claude Code,或将其仓库克隆到 skills 目录,然后重启 Claude 以加载该 Skill。

storybrand-messaging 属于哪个分类?

storybrand-messaging 属于元分类。

storybrand-messaging 可以免费使用吗?

可以。storybrand-messaging 已收录在 AIMCP,可免费安装。

相关推荐技能

content-collections

Content Collections 是一个 TypeScript 优先的构建工具,可将本地 Markdown/MDX 文件转换为类型安全的数据集合。它专为构建博客、文档站和内容密集型 Vite+React 应用而设计,提供基于 Zod 的自动模式验证。该工具涵盖从 Vite 插件配置、MDX 编译到生产环境部署的完整工作流。

查看技能
polymarket

这个Claude Skill为开发者提供完整的Polymarket预测市场开发支持,涵盖API调用、交易执行和市场数据分析。关键特性包括实时WebSocket数据流,可监控实时交易、订单和市场动态。开发者可用它构建预测市场应用、实施交易策略并集成实时市场预测功能。

查看技能
creating-opencode-plugins

该Skill帮助开发者创建OpenCode插件,用于接入命令、文件、LSP等25+种事件。它提供了插件结构、事件API规范和JavaScript/TypeScript实现模式,适合需要拦截操作、扩展功能或自定义事件处理的场景。开发者可通过它快速构建响应式模块来增强OpenCode AI助手的能力。

查看技能
sglang

SGLang是一个专为LLM设计的高性能推理框架,特别适用于需要结构化输出的场景。它通过RadixAttention前缀缓存技术,在处理JSON、正则表达式、工具调用等具有重复前缀的复杂工作流时,能实现极速生成。如果你正在构建智能体或多轮对话系统,并追求远超vLLM的推理性能,SGLang是理想选择。

查看技能