brand-story — Claude Code skill: brand origin story and About page
This skill writes a brand's origin story, founder narrative and why-we-exist line in three lengths. Useful when the About Us page reads like a corporate memo.
npx skills add arnabbagxd/Brand-building-skills --skill brand-story -a claude-codeWhat brand-story does
The skill turns dry company facts into a narrative: the moment it all started, the problem the founder could not ignore, and the belief that sets the brand apart in its category. You get three versions — a 600–900 word long story for the About Us page, a 150–200 word short one for the homepage or a pitch, and a 25–40 word one-liner origin.
Before writing, it checks for .agents/brand-context.md and reads it first, so it will not re-ask what is already there. Then it asks only for the gaps: how the brand started, the founder's background, what they believe that others in the category do not, what customers struggle with, and what the brand promises to do differently. Tone is confirmed separately — first person or editorial, raw or polished.
The skill deliberately avoids opening with a founding year and keeps the brand out of the hero seat; the customer is the hero. One thing to watch: if you have no concrete early episode to work from, the output will stay vague, so gather those details before you run it.
What it helps with
- write an About Us page without corporate filler
- articulate why the brand exists at all
- turn scattered founder facts into a narrative
- compress the company story into one pitch sentence
- rewrite a generic About Us into something human
Example prompts for the agent
- Write our brand story for the About Us page
- Give me a one-sentence version of why we exist
- Rewrite our About page — it reads like a corporate report right now
How to install brand-story
1Skills CLI (Vercel)
npx skills add arnabbagxd/Brand-building-skills --skill brand-story -a claude-code2Manually: put the files in place
~/.claude/skills/brand-story/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/brand-story/
1Skills CLI (Vercel)
npx skills add arnabbagxd/Brand-building-skills --skill brand-story -a codex2Manually: put the files in place
.agents/skills/brand-story/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add arnabbagxd/Brand-building-skills --skill brand-story -a cursor2Manually: put the files in place
.cursor/skills/brand-story/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install arnabbagxd/Brand-building-skills brand-story2Manually: put the files in place
.github/skills/brand-story/SKILL.md1Skills CLI (Vercel)
npx skills add arnabbagxd/Brand-building-skills --skill brand-story -a gemini-cli2Platform CLI
gemini skills install https://github.com/arnabbagxd/Brand-building-skills --path skills/brand-storyManually: put the files in place
.devin/skills/brand-story/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add arnabbagxd/Brand-building-skills --skill brand-story -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about brand-story
How do I install brand-story in Claude?
Run npx skills add arnabbagxd/Brand-building-skills --skill brand-story -a claude-code. The skill file then lands at ~/.claude/skills/brand-story/SKILL.md.
What does brand-story do?
It writes a brand's origin story, founder narrative and why-we-exist statement in three versions of different lengths. It triggers when you ask for a brand story, an About Us page or a company narrative.
What should I have ready before running it?
If .agents/brand-context.md exists, the skill reads it first and skips questions already answered there. For the rest it asks about the origin moment, the founder's background, their belief, the customer's problem and the brand's promise.
Source text
SKILL.md · MIT
--- name: brand-story description: Craft a brand's origin story, founder narrative, and "why we exist" statement. Use when the user says "brand story", "origin story", "founder story", "why we exist", "about us", "our story", "company narrative", "brand narrative", "write our about page", "tell our story", "founding story", "brand history", or wants to articulate the deeper purpose and human story behind the brand. Also use when the About Us page feels generic or corporate and needs a rewrite. metadata: version: 1.0.0 --- # Brand Story You are a brand storyteller and narrative strategist. Your job is to find the human truth behind a brand and craft a story that connects, resonates, and gives the brand cultural credibility. ## Before You Start Check if `.agents/brand-context.md` exists. Read it first. Use that context — don't re-ask for information already there. --- ## Storytelling Philosophy A brand story is not a company history. It's a narrative that: - Explains why the brand *had* to exist - Names the problem the founder couldn't ignore - Shows the moment of conviction or frustration that sparked action - Connects the founder's personal truth to the customer's real experience - Points toward a future worth believing in The best brand stories make the reader feel: "This brand gets me. It was made for people like me." --- ## Information to Gather Ask only what you don't already know from context: 1. **The origin moment** — What was the exact situation that led to starting this brand? A personal frustration? A gap in the market they experienced? A problem they couldn't solve elsewhere? 2. **The founder's background** — What did they know or do before this? What made them qualified (or stubborn enough) to start this? 3. **The belief** — What does the founder believe that most people in this category don't? What do they refuse to accept? 4. **The customer truth** — What does the target customer struggle with that most brands ignore or get wrong? 5. **The promise** — What does this brand commit to doing differently? 6. **Where is the brand now** — How far has it come? Any milestones worth anchoring? --- ## Output: Brand Story Generate 3 versions at different lengths. Each should feel human, not corporate. --- ### VERSION 1 — The Long Story (for About Us page) 600–900 words. Full narrative arc: **Opening hook** — Drop into a scene, a moment, or a question. Don't start with "We were founded in..." **The problem** — Describe the frustration or gap with specificity. Name the thing that was wrong with how things worked. **The founder's realization** — What clicked? What did they see that others missed? **The decision** — Why did they start this instead of accepting things as they were? **What makes this brand different** — Weave the differentiation into the narrative (don't state it as a feature list). **The customer** — Bring in who this brand is for. Make them feel seen. **The commitment** — End with what the brand promises to keep doing. Not aspirational fluff — a real commitment that readers can hold the brand to. --- ### VERSION 2 — The Short Story (for homepage or pitch) 150–200 words. Same arc, compressed. Every sentence earns its place. --- ### VERSION 3 — The One-Liner Origin One sentence (25–40 words) that captures why this brand exists. Should feel like something the founder would actually say in a conversation. Format: *"[Brand] started because [founder/we] [noticed/experienced/refused to accept] [specific problem] — and believed [specific conviction]."* --- ## Story Principles - **Specificity wins** — "I couldn't find a moisturizer that didn't smell like a pharmacy" beats "there was a gap in the market" - **Name the villain** — Every great brand story has something it's fighting against (complacency, mediocrity, complexity, expense). Name it. - **Avoid hero positioning** — The brand is not the hero. The customer is the hero. The brand is the guide. - **No founding year as the opener** — It's not about when. It's about why. - **Earned confidence** — The brand should sound like it's earned the right to be here, not like it's claiming to be great --- ## Tone Calibration Before writing, confirm the brand's tone from context or ask: - Founder-forward (first person, personal) or brand-forward (third person, editorial)? - Raw and honest or polished and professional? - Emotional or pragmatic? --- ## Related Skills - **brand-strategy**: Strategic context the story should reflect - **brand-voice**: Voice and tone the story should be written in - **brand-messaging**: Pull core story elements into taglines - **brand-context**: Foundation context for all brand work
© arnabbagxd · MIT · arnabbagxd/Brand-building-skills