Best for
- "Help me create a BrandScript for my business."
- "Clarify my message."
- "Rewrite my homepage using StoryBrand."
simbajigege/book2skills/skills/storybrand-messaging-framework/SKILL.md
Use StoryBrand for "clarify my message", "rewrite my homepage", "create a BrandScript", "what is my one-liner", or "fix my CTA".
Decision brief
Use StoryBrand for "clarify my message", "rewrite my homepage", "create a BrandScript", "what is my one-liner", or "fix my CTA".
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/simbajigege/book2skills --skill "skills/storybrand-messaging-framework"Inspect the Agent Skill "storybrand-messaging-framework" from https://github.com/simbajigege/book2skills/blob/f90fa7a78e4c78c92312d06fd70f7d24282c937f/skills/storybrand-messaging-framework/SKILL.md at commit f90fa7a78e4c78c92312d06fd70f7d24282c937f. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
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 sub…
1. Apply the grunt test: what is offered, how it improves life, what to do next. 2. Audit hero headline, subheadline, CTA, problem section, guide proof, plan, stakes, success. 3. Rewrite the highest-impact sections first. 4. Give prioritized fixes, not a generic critique.
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.
Rule: The customer is the hero, not the brand.
Permission review
The documentation includes network, browsing, or remote request actions.
- [*Building a StoryBrand*, cited excerpt](https://github.com/simbajigege/book2skills/blob/main/skills/storybrand-messaging-framework/quotes/main-framework-quotes.md#customer-is-hero)Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 93/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 146 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
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.
Frequently asked questions
Use StoryBrand for "clarify my message", "rewrite my homepage", "create a BrandScript", "what is my one-liner", or "fix my CTA".
The source record exposes this install command: npx skills add https://github.com/simbajigege/book2skills --skill "skills/storybrand-messaging-framework". Inspect the command and pinned source before running it.
Static rules flagged network in the source; the page lists the matching lines and excerpts.
Alternatives
garrytan/gbrain
End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
wanshuiyin/Auto-claude-code-research-in-sleep
Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.
prowler-cloud/prowler
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance