Agent skill

Storybrand Messaging

by wondelai in wondelai/skills

Clarify brand messaging using narrative structure that positions the customer as hero.

MITAuto-check passedMarketing & SEO

Install Storybrand Messaging

skills CLI
$ npx skills add wondelai/skills --skill storybrand-messaging -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wondelai/skills storybrand-messaging --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/storybrand-messaging .claude/skills/storybrand-messaging && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
storybrand-messaging
GitHub stars
2.4k
Token cost
~3.7k tokens
SKILL.md length
1,889 words
Files
7 (incl. references)
Skills in repo
62
Repo updated
First seen
Licence
MIT

At a glance

Clarify brand messaging using narrative structure that positions the customer as hero.

  • Works in 7 steps: A Character (The Hero) → Has a Problem → And Meets a Guide → …
  • The user mentions brand message
  • SKILL.md covers Core Principle, Scoring, The SB7 Framework and The One-Liner, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Storybrand Messaging is an agent skill from wondelai/skills. 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…

Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/brand-script.md`, `references/email-sequences.md` and `references/multi-channel-consistency.md`).

It sits in Marketing & SEO, covering Copywriting, Positioning and messaging and Email marketing. The repository describes itself as: Wondel.ai Agent Skills — Business, Marketing, UX & Coding Frameworks from Bestselling Books. 50 skills + 12 guided journeys for Claude Code, Codex, Cursor & other agentskills.io… The licence is MIT.

When your agent uses it

  • The user mentions brand message
  • StoryBrand framework
  • Customer as hero
  • My messaging isnt resonating

Example prompts

  • “brand message”
  • “website copy”
  • “elevator pitch”
  • “/storybrand-messaging”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. A Character (The Hero)
  2. Has a Problem
  3. And Meets a Guide
  4. Who Gives Them a Plan
  5. And Calls Them to Action
  6. That Helps Them Avoid Failure
  7. And Ends in Success

What it can do on your machine

Read from SKILL.md and the folder at commit c172996. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • amazon.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Storybrand Messaging loads about 3.7k tokens when it runs, and up to ~20k if it reads all its reference files. Until then it costs about 153 tokens; SKILL.md has 1,889 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~153
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~20k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wondelai/skills at commit c172996, republished under its MIT licence (© wondelai). 1,889 words, ~3,701 tokens.

Download SKILL.mdSave it as .claude/skills/storybrand-messaging/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
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
metadata.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

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.

Show full SKILL.md (752 more words)Show less
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.

© wondelai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (references) in storybrand-messaging of wondelai/skills.

  • SKILL.md
  • references/brand-script.md
  • references/email-sequences.md
  • references/multi-channel-consistency.md
  • references/one-liners.md
  • references/sales-conversations.md
  • references/website-wireframe.md

Open the folder on GitHubat commit c172996

Compare with similar skills

Storybrand Messaging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Storybrand Messaging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Storybrand Messaging this skillwondelai/skills2.4k—~3.7kAutomated safety check: PassMIT
Marketing OsYuzzyuk/marketing-os540—~2.5kAutomated safety check: PassMIT
Marketing Campaignaffaan-m/ECC277k1 repos~1.3kAutomated safety check: PassMIT
Marketingericrisco/rsc-harness180—~3.7kAutomated safety check: PassMIT
Smscoreyhaines31/marketingskills54k1 repos~4.6kAutomated safety check: PassMIT
Yao Positioning Skillyaojingang/yao-open-skills1.3k—~805Automated safety check: PassMIT

Similar skills

  • Marketing Os

    Yuzzyuk/marketing-os

    A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.

    540 GitHub stars~2.5k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Marketing Campaign

    affaan-m/ECC

    End-to-end marketing campaign planning and execution. An agent skill from affaan-m/ECC.

    277k GitHub starsUsed in 1 repo~1.3k tokens
    Marketing & SEOAuto-check passed
  • Marketing

    ericrisco/rsc-harness

    A skill your agent uses when the words span a marketing surface — value proposition, section copy, microcopy, launch and email sequences, channel adaptation, SEO-aware structure — grounded in the…

    180 GitHub stars~3.7k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Sms

    coreyhaines31/marketingskills

    When the user wants to plan, build, or optimize SMS, MMS, or WhatsApp marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional/auth SMS.

    54k GitHub starsUsed in 1 repo~4.6k tokens
    Marketing & SEOAuto-check passed
  • Yao Positioning Skill

    yaojingang/yao-open-skills

    Generate evidence-aware positioning reports for personal IPs, courses, products, services, brands, or companies by combining positioning theory, course-marketing analysis, user intent, competitor…

    1.3k GitHub stars~805 tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Autoresearch

    ericosiu/ai-marketing-skills

    Run Karpathy-style autoresearch optimization on any content.

    3.6k GitHub starsUsed in 2 repos~2.2k tokens
    Marketing & SEOAuto-check passed

More from wondelai/skills

All 62 skills in this repo
  • Crossing The Chasm

    wondelai/skills

    Navigate the technology adoption lifecycle from early adopters to mainstream market.

    2.4k GitHub stars~3.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Design Everyday Things

    wondelai/skills

    Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models.

    2.4k GitHub stars~4k tokensUpdated 1 mo ago
    Auto-check passed
  • Design Sprint

    wondelai/skills

    Run a structured 5-day process to prototype, test, and validate product ideas with real users.

    2.4k GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Hooked UX

    wondelai/skills

    Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment).

    2.4k GitHub stars~3.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Improve Retention

    wondelai/skills

    Diagnose and fix retention problems using behavior design (B=MAP).

    2.4k GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Monetizing Innovation

    wondelai/skills

    Design products and pricing around validated willingness to pay, from Ramanujam & Tacke's "Monetizing Innovation".

    2.4k GitHub stars~5.2k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Storybrand Messaging

What does Storybrand Messaging do?

Clarify brand messaging using narrative structure that positions the customer as hero. Storybrand Messaging is an agent skill from wondelai/skills. Clarify brand messaging using narrative structure that positions the customer as hero.

When should I use Storybrand Messaging?

Storybrand Messaging fits situations like: the user mentions brand message; storyBrand framework; customer as hero; my messaging isnt resonating.

How do I install Storybrand Messaging in Claude Code?

Run `npx skills add wondelai/skills --skill storybrand-messaging -a claude-code`. Or copy the skill folder (storybrand-messaging in wondelai/skills) into .claude/skills/storybrand-messaging in your project. Claude Code loads it when a task matches its description.

How do I install Storybrand Messaging in Codex?

Run `npx skills add wondelai/skills --skill storybrand-messaging -a codex`. Or copy the skill folder (storybrand-messaging in wondelai/skills) into .agents/skills/storybrand-messaging in your project. Codex loads it when a task matches its description.

Can I use Storybrand Messaging in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wondelai/skills --skill storybrand-messaging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/storybrand-messaging, .gemini/skills/storybrand-messaging, .github/skills/storybrand-messaging and .opencode/skills/storybrand-messaging in your project.

What does Storybrand Messaging need to run?

SKILL.md names no scripts, command-line tools or credentials: Storybrand Messaging is instructions for the agent only.

Does Storybrand Messaging access the network?

SKILL.md names 1 domain. As links in the text: amazon.com. This is read from the text; nothing was executed.

Is Storybrand Messaging safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Storybrand Messaging use?

Storybrand Messaging is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Storybrand Messaging use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.

What are the alternatives to Storybrand Messaging?

Skills that share tags, products or a category with Storybrand Messaging: Marketing Os (Yuzzyuk/marketing-os, 540 stars), Marketing Campaign (affaan-m/ECC, 277k stars), Marketing (ericrisco/rsc-harness, 180 stars) and Sms (coreyhaines31/marketingskills, 54k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Storybrand Messaging?

wondelai (a GitHub organization) maintains it in wondelai/skills, which has 2,371 GitHub stars. The repository holds 62 skills in this directory. The repository was last updated on September 10, 2026.

Source: wondelai/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.