Marketing Os
Yuzzyuk/marketing-os
A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.
Clarify brand messaging using narrative structure that positions the customer as hero.
$ npx skills add wondelai/skills --skill storybrand-messaging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wondelai/skills storybrand-messaging --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "storybrand-messaging" agent skill from https://github.com/wondelai/skills/tree/main/storybrand-messaging into .claude/skills/storybrand-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "storybrand-messaging", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/wondelai/skills/tree/main/storybrand-messagingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add wondelai/skills --skill storybrand-messaging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wondelai/skills storybrand-messaging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/storybrand-messaging .agents/skills/storybrand-messaging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "storybrand-messaging" agent skill from https://github.com/wondelai/skills/tree/main/storybrand-messaging into .agents/skills/storybrand-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "storybrand-messaging", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wondelai/skills --skill storybrand-messaging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wondelai/skills storybrand-messaging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/storybrand-messaging .cursor/skills/storybrand-messaging && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "storybrand-messaging" agent skill from https://github.com/wondelai/skills/tree/main/storybrand-messaging into .cursor/skills/storybrand-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "storybrand-messaging", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/wondelai/skills.git --path storybrand-messaging--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add wondelai/skills --skill storybrand-messaging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wondelai/skills storybrand-messaging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/storybrand-messaging .gemini/skills/storybrand-messaging && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "storybrand-messaging" agent skill from https://github.com/wondelai/skills/tree/main/storybrand-messaging into .gemini/skills/storybrand-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "storybrand-messaging", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install wondelai/skills storybrand-messagingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add wondelai/skills --skill storybrand-messaging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/storybrand-messaging .github/skills/storybrand-messaging && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "storybrand-messaging" agent skill from https://github.com/wondelai/skills/tree/main/storybrand-messaging into .github/skills/storybrand-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "storybrand-messaging", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wondelai/skills --skill storybrand-messaging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wondelai/skills storybrand-messaging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/storybrand-messaging .opencode/skills/storybrand-messaging && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "storybrand-messaging" agent skill from https://github.com/wondelai/skills/tree/main/storybrand-messaging into .opencode/skills/storybrand-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "storybrand-messaging", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
storybrand-messagingClarify 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. 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.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c172996. It shows what the files ask for, not the result of running them.
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.
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.
Links to these hosts (documentation or services it may open):
amazon.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from wondelai/skills at commit c172996, republished under its MIT licence (© wondelai). 1,889 words, ~3,701 tokens.
.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.Clarify your message so customers will listen. Customers don't buy the best products — they buy the ones they can understand the fastest.
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.
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.
Every compelling story follows the same pattern. Use this structure for all messaging:
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:
Product applications:
| Context | Application | Example |
|---|---|---|
| Homepage headline | Desire as outcome | "You want a beautiful smile" (not "our dentistry is excellent") |
| Landing page | One desire per page | "You want to retire early" |
| Segmentation | Tailor desire per segment | CEO: "Scale without chaos" vs. IC: "Do your best work without friction" |
Copy patterns:
See: references/brand-script.md — fill out the BrandScript worksheet here when you need to draft all seven elements for a client from scratch.
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:
Product applications:
| Context | Application | Example |
|---|---|---|
| Website problem section | Name all three levels | External: "Scattered tools." Internal: "You feel overwhelmed." Philosophical: "Teams deserve clarity." |
| Email nurture | Lead with internal problem | "Tired of feeling like you're guessing?" |
| Ad copy | Personify the villain | "Stop letting confusing software steal your evenings." |
Copy patterns:
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:
Product applications:
| Context | Application | Example |
|---|---|---|
| About page | Empathy 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 proof | Empathy headline + 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:
See: references/sales-conversations.md — open when scripting a sales call or discovery session; covers discovery questions, objection handling, and full SB7 sales scripts.
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:
Product applications:
| Context | Application | Example |
|---|---|---|
| Website plan section | 3-step process with icons | "1. Book a demo. 2. Get onboarded. 3. See results in 30 days." |
| Pricing page | Agreement plan reduces anxiety | "No contracts. Cancel anytime. 30-day money-back guarantee." |
| Email CTA | Reference the plan | "Getting started is simple — just three steps." |
Copy patterns:
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:
Product applications:
| Context | Application | Example |
|---|---|---|
| Homepage | Direct CTA above the fold, repeated | "Get Started Free" in header and after each section |
| Blog post | Transitional CTA at the end | "Download our free checklist" |
| Single Direct CTA per message | One "Schedule Your Call" button |
Copy patterns:
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.
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:
Product applications:
| Context | Application | Example |
|---|---|---|
| Landing page stakes section | Brief failure scenario before CTA | "Without a clear message, you'll keep losing customers to competitors they understand faster." |
| Email subject line | Light urgency | "Are you leaving revenue on the table?" |
| Sales conversation | Name cost of inaction | "What happens to your team if nothing changes in 6 months?" |
Copy patterns:
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:
Product applications:
| Context | Application | Example |
|---|---|---|
| Homepage success section | Specific after picture | "Imagine opening your inbox to qualified leads every morning — no cold outreach required." |
| Case study | Before/after with numbers | "Before: 2% conversion rate. After: 11% in 90 days." |
| Testimonials | Customers describe their success | "I finally feel like I know where every dollar is going." |
Copy patterns:
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").
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.
| Mistake | Why It Fails | Fix |
|---|---|---|
| Being the hero | Competes with customer | Position as guide |
| Multiple messages | Confuses people | One clear message per asset |
| Clever > clear | People don't decode messaging | Choose clarity always |
| Feature-focused | Customers buy transformation | Lead with outcomes |
| No clear CTA | No direction = no action | Ask for the sale |
| No stakes | No urgency = no motivation | Paint failure picture |
| Starting with "We" | Self-focused | Start with customer's problem |
| Question | If No | Action |
|---|---|---|
| Can a caveman grasp the offer in 5 seconds? | Message too complex | Simplify to one desire, one outcome |
| Is the customer clearly the hero? | Brand competes with customer | Rewrite from customer's perspective |
| Is the internal problem named, not just external? | Missing the emotional driver | Add "how it feels" language |
| Do you show empathy AND authority? | Trust gap | Add "we understand" + proof points |
| Is there a clear 3-step plan? | Path feels risky | Add Process + Agreement plans |
| Is there one obvious CTA? | Nobody acts | Add prominent, repeated Direct CTA |
| Do you show success AND failure stakes? | No narrative tension | Paint both outcome pictures |
For the complete methodology and worksheets:
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
SKILL.md and 6 other files (references) in storybrand-messaging of wondelai/skills.
Open the folder on GitHubat commit c172996
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Storybrand Messaging this skillwondelai/skills | 2.4k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Marketing OsYuzzyuk/marketing-os | 540 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Marketing Campaignaffaan-m/ECC | 277k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Marketingericrisco/rsc-harness | 180 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Smscoreyhaines31/marketingskills | 54k | 1 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Yao Positioning Skillyaojingang/yao-open-skills | 1.3k | — | ~805 | Automated safety check: Pass | MIT |
Yuzzyuk/marketing-os
A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.
affaan-m/ECC
End-to-end marketing campaign planning and execution. An agent skill from affaan-m/ECC.
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…
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.
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…
ericosiu/ai-marketing-skills
Run Karpathy-style autoresearch optimization on any content.
wondelai/skills
Navigate the technology adoption lifecycle from early adopters to mainstream market.
wondelai/skills
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models.
wondelai/skills
Run a structured 5-day process to prototype, test, and validate product ideas with real users.
wondelai/skills
Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment).
wondelai/skills
Diagnose and fix retention problems using behavior design (B=MAP).
wondelai/skills
Design products and pricing around validated willingness to pay, from Ramanujam & Tacke's "Monetizing Innovation".
Categories
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.
Storybrand Messaging fits situations like: the user mentions brand message; storyBrand framework; customer as hero; my messaging isnt resonating.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Storybrand Messaging is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: amazon.com. This is read from the text; nothing was executed.
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.
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.
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.
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.
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.