Mmcp.market

storybrand-messaging skill

by wondelai·wondelai/skills·2.3k stars·MIT

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.

A100/100content scan

Is the storybrand-messaging skill safe?

Clean: nothing in its files matched our rules. We read 7 files in the folder on 2026-09-28.

No findings.

Install the storybrand-messaging skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/wondelai/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/plugins/marketing-cro/skills/storybrand-messaging ~/.claude/skills/storybrand-messaging
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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:

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:

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:

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:

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:

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:

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]."

More skills from wondelai/skills

  • A37signals-wayBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
  • A37signals-wayBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
  • A37signals-wayBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Ablue-ocean-strategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
  • Ablue-ocean-strategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
  • Ablue-ocean-strategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
  • Aclean-architectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
  • Aclean-architectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
  • Aclean-architectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.

All agent skills → · MCP servers