Use StoryBrand for "clarify my message", "rewrite my homepage", "create a BrandScript", "what is my one-liner", or "fix my CTA".
npx skills add https://github.com/simbajigege/book2skills --skill storybrand-messaging-framework
Use this skill to apply Donald Miller's StoryBrand SB7 framework to brand messaging, website copy, fundraising appeals, product positioning, sales pages, and marketing assets. The skill turns a confusing offer into a clear customer-centered story: the customer is the hero, the brand is the guide, the offer solves a real problem, and the next action is obvious.
This is a messaging-clarity skill. It does not validate whether a market exists, set paid-media budgets, or replace customer research.
Invoke this skill when the user asks:
Clear messaging beats clever messaging. The user must leave with copy that quickly answers: what is being offered, how it improves the customer's life, and what the customer should do next.
| Workflow | User question pattern | Inputs | Steps | Output | Should be subskill? |
|---|---|---|---|---|---|
| BrandScript creation | "Apply StoryBrand to my business" | Offer, customer, problem, proof, desired action | Fill all seven SB7 elements | Complete BrandScript | No — primary workflow |
| Website grunt test | "Review my homepage" | Existing copy or URL text | Test clarity, hierarchy, CTA, stakes, success | Rewrite and priority fixes | No — applies the same SB7 sequence |
| One-liner creation | "What is my pitch?" | Customer, problem, solution, result | Problem + solution + result | One-liner variants | No — narrow asset from SB7 |
| CTA and funnel design | "What should the CTA be?" | Buying stage, friction, trust level | Direct and transitional CTA mapping | CTA set and placement | No — Dimension 5 application |
| Asset rewrite | "Rewrite this email/ad/page" | Draft copy, audience, goal | Reframe customer as hero and brand as guide | Revised copy | No — channel-specific application |
Architecture decision: Keep this as a single-file skill. StoryBrand is one tightly coupled SB7 messaging workflow; BrandScripts, website reviews, one-liners, CTAs, and rewrites all reuse the same seven dimensions and usually share the same output assets. Splitting these into subskills would make routing heavier without improving decision quality.
Rule: The customer is the hero, not the brand.
Key questions:
Decision criteria:
Warning signals:
Agent instruction: Name the customer's concrete want before writing any brand copy. If the user provides many audiences or goals, ask them to pick the primary buyer for this pass.
Rule: Customers buy relief from internal frustration, not only solutions to external problems.
Key questions:
Decision criteria:
Warning signals:
Agent instruction: Diagnose all three problem levels and choose the one most likely to move the customer. Do not stop at feature-level pain points.
Rule: The brand must be the guide, not a competing hero.
Key questions:
Decision criteria:
Warning signals:
Agent instruction: Write one empathy line and one authority line. If proof is missing, mark it as a gap and suggest what evidence to collect.
Rule: A confused buyer does not move. A guide gives a simple path.
Key questions:
Decision criteria:
Warning signals:
Agent instruction: Produce a process plan for action and, when trust is low, an agreement plan that names guarantees, standards, or commitments.
Rule: Customers do not act unless challenged to act.
Key questions:
Decision criteria:
Warning signals:
Agent instruction: Always output both direct and transitional CTAs unless the channel only permits one.
Rule: Stakes make action meaningful, but fearmongering breaks trust.
Key questions:
Decision criteria:
Warning signals:
Agent instruction: Add one concise stakes statement, then quickly move to the success outcome.
Rule: The brand must paint the customer's successful future.
Key questions:
Decision criteria:
Warning signals:
Agent instruction: End major copy outputs with a before/after transformation and an aspirational identity statement.
Use this structure:
We help [customer] who struggle with [problem] get [solution] so they can [success].
For a complete messaging request, respond with:
## StoryBrand Diagnosis
- Customer:
- Primary desire:
- Main problem:
- Current clarity issue:
## BrandScript
1. Character:
2. Problem:
- External:
- Internal:
- Philosophical:
- Villain:
3. Guide:
- Empathy:
- Authority:
4. Plan:
5. Calls to action:
- Direct:
- Transitional:
6. Failure avoided:
7. Success:
## Copy Assets
- One-liner:
- Tagline options:
- Website hero:
- CTA set:
## Priority Fixes
1. ...
2. ...
3. ...
For a narrow rewrite, respond with:
## Revised Copy
...
## Why This Works
- Customer-as-hero shift:
- Problem clarity:
- CTA improvement:
## Remaining Gaps
- Proof needed:
- Customer decision needed:
When making substantive StoryBrand-method claims, cite the quote files if the user asks for sources or if the answer is a formal audit.
Quote files:
quotes/main-framework-quotes.md — SB7 rules, clarity, guide positioning, plan, CTA, stakes, transformation.quotes/storybrand-principles-quotes.md — broader StoryBrand principles and implementation reminders.Anchor mapping:
main-framework-quotes.md: #words-sell-things, #brain-drawn-to-clarity, #story-greatest-weapon, #customer-is-hero, #customer-looks-for-guide, #companies-sell-external, #trust-guide-with-plan, #call-to-action-required, #avoid-tragic-ending, #buying-transformation, #if-you-confuse-you-lose, #grunt-teststorybrand-principles-quotes.md: #story-organizes-information, #brain-survive-and-thrive, #story-makes-music, #think-different-lesson, #hero-in-a-hole, #three-levels-problems, #guide-positioning, #tidal-fatal-mistake, #story-gap-power, #conflict-gets-attention, #villain-focus, #plan-removes-confusion, #two-types-cta, #whats-at-stake, #aspirational-identity, #one-liner-formula, #website-hierarchyCitation format:
> "Author's exact words here."
>
> - [*Building a StoryBrand*, cited excerpt](https://github.com/simbajigege/book2skills/blob/main/skills/storybrand-messaging-framework/quotes/main-framework-quotes.md#customer-is-hero)
Use only exact quote text from the quote files. If no exact quote fits, cite the closest anchor and state that the analysis is a paraphrased application.
Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.
Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack of X doing Y".
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.
Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack.
A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.
Take simbajigege/storybrand-messaging-framework from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.