MCP HubMCP Hub
SKILL·213134

storybrand-messaging

wondelai
更新日 20 days ago
5 閲覧
2,065
213
2,065
GitHubで表示
メタai

について

このスキルは、顧客を主人公として位置付ける物語構造「StoryBrand」フレームワークを適用することで、開発者がブランドメッセージを明確化することを支援します。ウェブサイトのコピー書き換え、ピッチの構築、マーケティング資料全体での一貫したメッセージングの確保などのタスクで起動されます。このスキルは、ブランドが顧客の物語への導き手としてコミュニケーションする方法を変革することに焦点を当てています。

クイックインストール

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 はwondelai が作成した Claude Skillです。Skillは、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(Markdown/MDXファイルを型安全なデータコレクションに変換するTypeScriptファーストのツール)の本番環境でテストされた設定を提供します。Zodバリデーションによる型安全性を実現し、ブログ、ドキュメントサイト、コンテンツ重視のVite + Reactアプリケーション構築時にご利用ください。Viteプラグインの設定、MDXコンパイルから、デプロイ最適化、スキーマバリデーションまで、すべてを網羅しています。

スキルを見る
polymarket
メタ

このスキルは、開発者がPolymarket予測市場プラットフォームを活用したアプリケーション構築を可能にします。API統合による取引や市場データの取得に加え、WebSocketを介したリアルタイムデータストリーミングにより、ライブ取引や市場活動を監視できます。取引戦略の実装や、ライブ市場更新を処理するツールの作成にご利用ください。

スキルを見る
creating-opencode-plugins
メタ

このスキルは、開発者がコマンド、ファイル、LSP操作など25種類以上のイベントタイプにフックするOpenCodeプラグインを作成することを支援します。JavaScript/TypeScriptモジュール向けに、プラグイン構造、イベントAPI仕様、および実装パターンを提供します。カスタムイベント駆動ロジックでOpenCode AIアシスタントのライフサイクルをインターセプト、監視、または拡張する必要がある場合にご利用ください。

スキルを見る
sglang
メタ

SGLangは、高性能なLLMサービングフレームワークであり、RadixAttentionプレフィックスキャッシュを活用したJSON、正規表現、エージェントワークフロー向けの高速で構造化された生成を特長とします。特にプレフィックスが繰り返されるタスクにおいて、大幅に高速な推論を実現し、複雑な構造化出力やマルチターン対話に最適です。制約付きデコードが必要な場合や、広範なプレフィックス共有を伴うアプリケーションを構築する場合は、vLLMなどの代替案ではなくSGLangを選択してください。

スキルを見る