storybrand-messaging
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", "messaging isnt resonating", "brand script", "StoryBrand framework", or "customer as hero". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.
What this skill does
# StoryBrand Messaging Framework
Framework for clarifying your message so customers will listen. Based on a fundamental truth: 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. When you position yourself as the hero, you compete with your customer. When you position yourself as the guide, you serve them.
## Scoring
**Goal: 10/10.** When reviewing or creating marketing copy or brand messaging, rate it 0-10 based on adherence to the principles below. A 10/10 means full alignment with all guidelines; lower scores indicate gaps to address. Always provide the current score and specific improvements 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 wants something. Every story begins with a hero who wants something. In your brand's story, the customer is the hero and your job is to define what they want. Be specific about that one desire.
**Why it works:** Opening a story gap — the distance between where a character is and where they want to be — creates tension that demands resolution. When you name a customer's desire clearly, they lean in because they feel understood and want to know how the gap gets closed.
**Key insights:**
- Open a story gap (desire creates tension that pulls people into the narrative)
- Focus on ONE desire per message (not a list — multiple desires dilute the story gap)
- The desire should relate to survival (physical, financial, relational, or spiritual)
- Aspirational identity is powerful ("become the leader everyone respects")
- Different segments may have different primary desires — create separate messaging for different roles, stages, and pain intensities
**Product applications:**
| Context | Application | Example |
|---------|-------------|---------|
| Homepage headline | State the customer's desire as the outcome | "You want a beautiful smile" (not "our dentistry is excellent") |
| Landing page | Lead with one desire per page | "You want to retire early" (not "we offer comprehensive financial planning") |
| Audience segmentation | Tailor the desire to each segment | CEO: "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]?"
- "You deserve [survival-level desire]..."
**Ethical boundary:** Never fabricate desires the customer does not actually hold. Ground the desire in real research, interviews, or observed behavior — not manufactured aspiration.
See: [references/brand-script.md](references/brand-script.md)
### 2. Has a Problem
**Core concept:** The hero faces a problem that stands in the way of getting what they want. Every story needs conflict. Define the problem at three levels — external, internal, and philosophical — and personify it with a villain that gives the problem a face.
**Why it works:** Companies tend to sell solutions to external problems, but customers buy solutions to internal problems. When you name how the problem makes them feel — confused, overwhelmed, embarrassed — you tap into the emotional driver that actually motivates purchasing decisions.
**Key insights:**
- External problems are tangible and surface-level ("my investments are scattered")
- Internal problems are emotional ("I feel confused and overwhelmed")
- Philosophical problems frame the injustice ("People shouldn't have to be experts to retire well")
- The villain personifies the problem — a good villain is specific and relatable, not abstract
- Most brands only address external problems, missing the internal problems that truly drive purchases
- Bad villain: "complexity" (abstract); Good villain: "Wall Street jargon designed to confuse you"
**Product applications:**
| Context | Application | Example |
|---------|-------------|---------|
| Problem section on website | Name all three levels of the problem | External: "Scattered tools." Internal: "You feel overwhelmed." Philosophical: "Teams deserve clarity." |
| Email nurture sequence | Lead with the internal problem | "Tired of feeling like you're guessing?" |
| Ad copy | Personify 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]..."
- "You've tried everything but [external problem] persists because [villain]..."
**Ethical boundary:** Never exaggerate problems to create unnecessary fear. Name real frustrations honestly; do not invent suffering the customer has not experienced.
See: [references/brand-script.md](references/brand-script.md)
### 3. And Meets a Guide
**Core concept:** Enter the guide — a character who has empathy AND authority. Your brand is the guide, not the hero. You demonstrate empathy by understanding the customer's pain, and authority by proving you can actually solve it. The balance of both is what earns trust.
**Why it works:** Customers are not looking for another hero — they are looking for a guide. Think Yoda, not Luke. When a brand expresses empathy, the customer feels seen. When the brand demonstrates authority (testimonials, logos, statistics), the customer feels safe. Together, these two qualities create the trust needed for a customer to engage.
**Key insights:**
- Empathy without authority makes you seem weak; authority without empathy makes you seem arrogant
- Demonstrate empathy with "we understand" language and by accurately describing their frustration
- Demonstrate authority with testimonials, client logos, statistics, awards, and years of experience
- Never tell your origin story as the centerpiece — that is hero behavior
- Brief, relevant credentials are fine; a multi-paragraph "our journey" story loses the customer
**Product applications:**
| Context | Application | Example |
|---------|-------------|---------|
| About page | Lead with empathy, then show credentials | "We know what it's like to feel lost in financial jargon. That's why 10,000 families trust us." |
| Homepage social proof | Combine empathy headline with authority logos | "You're not alone. Join 5,000+ teams who found clarity." + client logos |
| Sales call | Open 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]..."
- "In our experience working with [authority reference]..."
- "We've helped [number] [customers] achieve [result]..."
- "You don't have to figure this out alone..."
**Ethical boundary:** Never claim authority you have not earned. Testimonials must be real, statistics must be accurate, and credentials must be verifiable.
See: [references/sales-conversations.md](references/sales-conversations.md)
### 4. Who Gives Them a Plan
**Core concept:** The guide gives the hero a plan. Plans create clarity and reduce the fear of doing business with you. There are two types: a Process Plan (3-4 steps showing how to work with you) and an Agreement Plan (commitments you make to remove risk).
**Why it works:** Customers feel uncertain before making a purchase. A clear, simple plan acts as stepping stones across a creek — it shows them exactly how to get from where they are to where they want to be. Without a plan, the path feels murky and they stall. Plans reduce cognitive load and perceived risk.
**Key insights:**
- Process Plan: 3-4 numbered steps to work with you (e.g., "1. Schedule a call. 2. Get a custom plan. 3. Start seeing results.")
- Agreement Plan: commitments that remove fear (e.g., "100% satisfaction guaranteed", "Cancel anytime", "We'll never pressure you")
- Limit to 3Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".