brand-storytelling
Skill9 starsChanged 6 months agoMITView on GitHub
Craft compelling company narrative, origin story, and pitch decks. Use for "what's our story" and investor/press narratives. For product positioning statement and taglines, use positioning-messaging instead.
4 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- scayver/marketing-skillstheir own version, first seen Oct 13, 2026
- FelipeAngeli/skillsedited, first seen Apr 10, 2026
- pedronauck/skillsedited, first seen Apr 3, 2026
- Layneformalized225/ai-cofounderedited, first seen Mar 22, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- pedronauck/skills★ 64994% same
- FelipeAngeli/skills★ 294% same
- Layneformalized225/ai-cofounder★ 198% same
Wrote their own version · 1
- scayver/marketing-skills★ 8same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository78 other files it gives its agents.
- anti-pattern-auditSkill
- business-investigationSkill
- ceo-weekly-reviewSkill
- cold-emailSkill
- community-buildingSkill
- company-intelSkill
- competitive-analysisSkill
- competitor-researchSkill
- composio-cliSkill
- conducting-user-interviewsSkill
- content-strategySkill
- copywritingSkill
- daily-recapSkill
- decision-playbookSkill
- designing-growth-loopsSkill
- discovery-debriefSkill
- email-sequenceSkill
- enterprise-salesSkill
- evening-recapSkill
- exa-code-searchSkill
- exa-company-researchSkill
- exa-lead-genSkill
- exa-people-researchSkill
- exa-personal-siteSkill
- exa-x-searchSkill
- feedback-trackerSkill
- find-email-by-nameSkill
- focus-keeperSkill
- founder-salesSkill
- fpf-problem-solvingSkill
- github-stars-monitorSkill
- google-calendarSkill
- grafana-monitoringSkill
- humanizerSkill
- hypothesis-trackerSkill
- idea-generatorSkill
- install-openclaw-to-digitaloceanSkill
- install-openclaw-to-hetznerSkill
- install-openclaw-to-ycSkill
- launch-marketingSkill
- lead-enrichmentSkill
- measuring-product-market-fitSkill
- meeting-prepSkill
- metrics-briefingSkill
- morning-briefSkill
- openclaw-guideSkill
- openclaw-user-onboardingSkill
- orthogonalSkill
- outreach-senderSkill
- person-lookupSkill
- ph-launch-timelineSkill
- pipeline-managerSkill
- positioning-messagingSkill
- positioning-workshopSkill
- posthog-analyticsSkill
- prepare-yc-workshopSkill
- pricing-strategySkill
- problem-definitionSkill
- product-hunt-launchSkill
- product-led-salesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 4 are common, 1 is distinctive, and 1 is very specific to this project.
4
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.
- Distinctive: line 9
Follow output preferences from USER.md (language, format, platform constraints).
- Common: line 19
When the user asks for help with brand storytelling:
- Common: line 21
Understand the context: - Ask who the audience is (investors, customers, employees) and what action they want to inspire
- Common: line 68
Starting with your company: - Start with the audience's problem or the world's change, not "We are..."
- Common: line 72
No stakes: - If nothing's at risk, there's no tension
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
[YOUR_PRODUCT] Context
Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.
Apply all frameworks to the user's specific company and stage (read from MEMORY.md).
Follow output preferences from USER.md (language, format, platform constraints).
For chat platforms: max 15 lines, no markdown tables, be concrete and actionable.
Brand Storytelling
Help the user craft compelling narratives that make their brand memorable using techniques from 30 product leaders and storytelling experts.
How to Help
When the user asks for help with brand storytelling:
- Understand the context - Ask who the audience is (investors, customers, employees) and what action they want to inspire
- Find the core story - Help identify the transformation, movement, or unique insight at the heart of the brand
- Structure the narrative - Apply proven frameworks to organize the story effectively
- Make it memorable - Help craft specific phrases, metaphors, and moments that stick
Core Principles
Lead a movement, don't just solve a problem
Andy Raskin: "This structure is about defining a movement—that's very different from 'I'm going to solve your problem.'" Frame your brand as the leader of a shift toward a new way of winning.
Story before product
Brian Chesky: "One of the first things we do is figure out what the story is. The story often dictates the product. A story is a helpful way to develop a cohesive product." Define the narrative before finalizing features.
Find the five-second moment
Matthew Dicks: "Every story is about a singular moment—I call it five seconds. A moment of transformation or realization. 98% of the story provides context to make that moment clear." Identify the single moment of change.
Start in the middle of the action
Merci Grace: "Every pitch should start in the middle of the action, like Mission Impossible. Tom Cruise is always doing crazy shit before the actual mission. It gets attention." Skip the boring setup—hook them immediately.
Problems beat successes
Jason Feifer: "Success stories aren't interesting. Problem-solving stories are. Frame your story around a specific challenge you faced and the counterintuitive way you solved it."
You're Obi-Wan, not Luke
Mike Maples Jr: "The customer is the hero (Luke Skywalker), the founder is the mentor (Obi-Wan) providing the tools. Position your product as the lightsaber—the tool the hero needs."
Make it repeatable
Lulu Cheng Meservey: "Make it memorable. Make people want to say it of their own volition. Use analogies, colorful mental images, jokes. Replace adjectives with anecdotes people can repeat at dinner."
Paint emotional pictures
Camille Ricketts: "Effective storytelling paints an emotional picture of the vision. Convey the emotional quality of the mission, not just technical details, to enlist hearts and minds."
Hook, message, celebration
Christina Wodtke: "A beginning, middle, and end. Intrigue with a hook—a mystery, secret, or surprise. The middle delivers the message. Always end with success and celebration."
Memify your insights
Yuhki Yamashata: "The goal is 'memification'—synthesize insights so they're catchy enough for execs to cite in meetings. Use metaphors to explain complex concepts."
Questions to Help Users
- "Who is your audience and what do you want them to do after hearing this?"
- "What's the transformation or realization at the heart of your story?"
- "What problem did you face that others can relate to?"
- "Can someone repeat your core message at a dinner party?"
- "Are you the hero of this story, or is your customer?"
Common Mistakes to Flag
- Starting with your company - Start with the audience's problem or the world's change, not "We are..."
- Feature lists instead of stories - Stories are about change; lists are forgettable
- Hero syndrome - Position yourself as the mentor, not the hero
- Vague vision - "Making the world better" isn't a story; be specific
- No stakes - If nothing's at risk, there's no tension
Deep Dive
For all 50 insights from 30 guests, see references/guest-insights.md
Related Skills
- positioning-workshop — full positioning exercise (do this before storytelling)
- positioning-messaging
- copywriting
- social-writer
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

