storybrand-messaging-framework

Name: storybrand-messaging-framework
Author: simbajigege

4installs21forks

How to install storybrand-messaging-framework?

simbajigege/book2skills/storybrand-messaging-framework

$npx -y skills add simbajigege/book2skills --skill storybrand-messaging-framework

Installs into the current project.

Summary

Use StoryBrand for "clarify my message", "rewrite my homepage", "create a BrandScript", "what is my one-liner", or "fix my CTA".

Files · 1

View on GitHub

SKILL.md

1	# StoryBrand Messaging Framework
2
3	## Overview
4
5	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.
6
7	This is a messaging-clarity skill. It does not validate whether a market exists, set paid-media budgets, or replace customer research.
8
9	## When to Use This Skill
10
11	Invoke this skill when the user asks:
12
13	- "Help me create a BrandScript for my business."
14	- "Clarify my message."
15	- "Rewrite my homepage using StoryBrand."
16	- "Does this pass the grunt test?"
17	- "What is my one-liner?"
18	- "Am I positioning myself as the hero or the guide?"
19	- "Write a better CTA, tagline, landing page, email, ad, or pitch."
20
21	## Core Principle
22
23	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.
24
25	## Workflow Inventory
26
27	\| Workflow \| User question pattern \| Inputs \| Steps \| Output \| Should be subskill? \|
28	\|---\|---\|---\|---\|---\|---\|
29	\| BrandScript creation \| "Apply StoryBrand to my business" \| Offer, customer, problem, proof, desired action \| Fill all seven SB7 elements \| Complete BrandScript \| No — primary workflow \|
30	\| 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 \|
31	\| One-liner creation \| "What is my pitch?" \| Customer, problem, solution, result \| Problem + solution + result \| One-liner variants \| No — narrow asset from SB7 \|
32	\| 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 \|
33	\| 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 \|
34
35	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.
36
37	## The SB7 Framework
38
39	### DIMENSION 1: A Character
40
41	Rule: The customer is the hero, not the brand.
42
43	Key questions:
44
45	- What does the customer want?
46	- Can the desire be stated in one clear sentence?
47	- Is the copy centered on the customer's ambition rather than the company's story?
48
49	Decision criteria:
50
51	- One primary desire is visible above all secondary messages.
52	- The customer's current state and desired future state create a story gap.
53	- Company history and internal language are removed unless they prove guide authority.
54
55	Warning signals:
56
57	- The copy opens with company history, credentials, or founder story before naming the customer's want.
58	- Multiple audiences or desires compete in the same headline, pitch, or page section.
59	- The offer is framed as what the company does rather than what the customer gets.
60
61	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.
62
63	### DIMENSION 2: Has a Problem
64
65	Rule: Customers buy relief from internal frustration, not only solutions to external problems.
66
67	Key questions:
68
69	- What is the external practical problem?
70	- What internal frustration, fear, delay, embarrassment, or uncertainty does it create?
71	- What philosophical "this should not be this hard" statement makes the stakes feel meaningful?
72	- What force can be named as the villain without attacking a person?
73
74	Decision criteria:
75
76	- The copy includes external, internal, and philosophical problem language.
77	- The villain is a problem source such as complexity, waste, risk, or confusion.
78	- The emotional problem is specific enough to make the buyer feel understood.
79
80	Warning signals:
81
82	- The message lists features without naming the buyer's practical problem.
83	- The copy uses generic pain words such as "stress" or "frustration" without context.
84	- The villain is a person or customer group rather than the obstacle the offer helps defeat.
85
86	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.
87
88	### DIMENSION 3: Meets a Guide
89
90	*Rule:

People who liked this also viewed

6 picks

Type

storybrand-messaging-framework

4installs21forks

View on GitHub

How to install storybrand-messaging-framework?

simbajigege/book2skills/storybrand-messaging-framework

$npx -y skills add simbajigege/book2skills --skill storybrand-messaging-framework

Installs into the current project.

Summary

Use StoryBrand for "clarify my message", "rewrite my homepage", "create a BrandScript", "what is my one-liner", or "fix my CTA".

Files · 1

View on GitHub

SKILL.md

1	# StoryBrand Messaging Framework
2
3	## Overview
4
5	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.
6
7	This is a messaging-clarity skill. It does not validate whether a market exists, set paid-media budgets, or replace customer research.
8
9	## When to Use This Skill
10
11	Invoke this skill when the user asks:
12
13	- "Help me create a BrandScript for my business."
14	- "Clarify my message."
15	- "Rewrite my homepage using StoryBrand."
16	- "Does this pass the grunt test?"
17	- "What is my one-liner?"
18	- "Am I positioning myself as the hero or the guide?"
19	- "Write a better CTA, tagline, landing page, email, ad, or pitch."
20
21	## Core Principle
22
23	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.
24
25	## Workflow Inventory
26
27	\| Workflow \| User question pattern \| Inputs \| Steps \| Output \| Should be subskill? \|
28	\|---\|---\|---\|---\|---\|---\|
29	\| BrandScript creation \| "Apply StoryBrand to my business" \| Offer, customer, problem, proof, desired action \| Fill all seven SB7 elements \| Complete BrandScript \| No — primary workflow \|
30	\| 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 \|
31	\| One-liner creation \| "What is my pitch?" \| Customer, problem, solution, result \| Problem + solution + result \| One-liner variants \| No — narrow asset from SB7 \|
32	\| 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 \|
33	\| 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 \|
34
35	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.
36
37	## The SB7 Framework
38
39	### DIMENSION 1: A Character
40
41	Rule: The customer is the hero, not the brand.
42
43	Key questions:
44
45	- What does the customer want?
46	- Can the desire be stated in one clear sentence?
47	- Is the copy centered on the customer's ambition rather than the company's story?
48
49	Decision criteria:
50
51	- One primary desire is visible above all secondary messages.
52	- The customer's current state and desired future state create a story gap.
53	- Company history and internal language are removed unless they prove guide authority.
54
55	Warning signals:
56
57	- The copy opens with company history, credentials, or founder story before naming the customer's want.
58	- Multiple audiences or desires compete in the same headline, pitch, or page section.
59	- The offer is framed as what the company does rather than what the customer gets.
60
61	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.
62
63	### DIMENSION 2: Has a Problem
64
65	Rule: Customers buy relief from internal frustration, not only solutions to external problems.
66
67	Key questions:
68
69	- What is the external practical problem?
70	- What internal frustration, fear, delay, embarrassment, or uncertainty does it create?
71	- What philosophical "this should not be this hard" statement makes the stakes feel meaningful?
72	- What force can be named as the villain without attacking a person?
73
74	Decision criteria:
75
76	- The copy includes external, internal, and philosophical problem language.
77	- The villain is a problem source such as complexity, waste, risk, or confusion.
78	- The emotional problem is specific enough to make the buyer feel understood.
79
80	Warning signals:
81
82	- The message lists features without naming the buyer's practical problem.
83	- The copy uses generic pain words such as "stress" or "frustration" without context.
84	- The villain is a person or customer group rather than the obstacle the offer helps defeat.
85
86	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.
87
88	### DIMENSION 3: Meets a Guide
89
90	*Rule:

People who liked this also viewed

6 picks

Type