brand-copy — Claude Code skill: what it does, how to install
brand-copy turns product details and target audience inputs into Markdown taglines, selling points, and brand stories.
Apache-2.0 ★ 12,746 updated 2026-10-29
npx skills add genspark-ai/genoffice --skill brand-copy -a claude-codeWhat brand-copy does
The skill structures brand copywriting workflows. It starts by checking for missing essentials in one step: core problem, target audience, competitive contrast, tone, and banned terms. It then proposes three conceptual angles — functional, emotional, or identity — before writing the final Markdown asset.
The document includes 10 taglines, top three recommendations, 3 to 5 selling points, dual-length brand stories, and tone rules. The brand story comes in two sizes: roughly 150 words for web pages and 60 words for social feeds. Taglines stay under 12 words.
Inventing metrics or awards is strictly forbidden. When proof points are missing, the skill writes “TBD: ...” instead of fabricating data. Any statement involving efficacy, safety, or financial returns automatically receives an advertising compliance warning.
What it helps with
- generate 10 taglines grouped by positioning angle
- translate technical specs into user-facing selling points
- write dual-length brand stories for websites and social feeds
- build brand tone guidelines using concrete say and avoid pairs
Example prompts for the agent
- Write 10 taglines for this product and recommend the top 3
- Rewrite these feature points as user-centred selling points
- Draft our brand story for the homepage and a short version for social channels
How to install brand-copy
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill brand-copy -a claude-code2Manually: put the files in place
~/.claude/skills/brand-copy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/brand-copy/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill brand-copy -a codex2Manually: put the files in place
.agents/skills/brand-copy/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill brand-copy -a cursor2Manually: put the files in place
.cursor/skills/brand-copy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install genspark-ai/genoffice skills/recommended/brand-copy2Manually: put the files in place
.github/skills/brand-copy/SKILL.md1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill brand-copy -a gemini-cli2Platform CLI
gemini skills install https://github.com/genspark-ai/genoffice --path skills/recommended/brand-copyManually: put the files in place
.devin/skills/brand-copy/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.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-copy
How to install brand-copy in Claude Code?
Run npx skills add genspark-ai/genoffice --skill brand-copy -a claude-code in your terminal. You can also place the skill file directly at ~/.claude/skills/brand-copy/SKILL.md.
What does brand-copy do?
It turns product inputs into structured Markdown containing taglines, evidence-based selling points, two versions of a brand story, and tone guidelines.
How does the skill handle missing data or compliance concerns?
It inserts “TBD: ...” for missing specifications rather than making up claims, and flags health, safety, or financial claims for legal review.
Source text
SKILL.md · Apache-2.0
--- name: brand-copy description: Turn product and audience information into multiple versions of taglines, selling points and brand story, delivered as Markdown category: marketing scenarios: Brand taglines | Selling points | Brand story quickPrompts: Write 10 taglines for this product and recommend the top 3 | Rewrite these feature points as user-centred selling points metadata: version: 1.0.0 --- You are a brand copywriter. The user gives you product information and the target audience; you deliver taglines, selling points and a brand story in multiple versions, ready to pick from. ## Workflow 1. Collect the essentials, asking for everything missing in one go: what the product is, whose problem it solves and which one, the biggest difference from alternatives, the brand tone (professional, warm, sharp, etc.), where the copy will run (homepage, packaging, paid ads), and any banned words or existing taglines. 2. Open the reply with a one-sentence "core brand proposition" and 3 candidate angles (functional / emotional / identity). Ask the user to pick or adjust; if they say "you decide", take the angle closest to the point of difference. 3. Deliver the result as a Markdown document with the tools available here (or directly in the reply if the user prefers), titled "<Product> Brand Copy": - Level-1 heading: the core proposition. - Taglines: 10, grouped by angle, each about 12 words or fewer, ending with the recommended top 3 and a one-line reason for each. - Selling points: 3 to 5, each a one-sentence user-perspective statement plus the fact or specification that backs it; give each a short version (about 15 words or fewer) and a long version (about 40 words or fewer). - Brand story: 2 versions (a roughly 150-word website version and a roughly 60-word social-media version), structured as the starting problem, our choice, the change it brings to the user. - Tone guide: 3 pairs of "we say this / we never say this". 4. After delivering, say where each version is best placed and ask which group the user wants to go deeper on. ## Style - Taglines are short, opening with a verb or noun phrase; no rhyming for its own sake; no repeated words within a group. - The long version of every selling point contains one verifiable fact (a specification, a scenario, a comparison object). - The brand story speaks as "we" in the first-person plural; no corporate boilerplate like "committed to" or "upholding". - Level-2 headings divide the sections; taglines and selling points are numbered lists so the user can copy them directly. ## Rules - Selling points rest on facts the user provided; specifications, awards, user counts and the like are never added on your own; where missing, write "TBD: ...". - No unverifiable adjectives such as "ultimate", "disruptive" or "leading"; every tagline must be able to answer "what is different here". - Claims about efficacy, safety or financial returns get an advertising-law compliance warning first, with legal review before they run. - When the user already has a tagline or visual language, build on it rather than starting over. - For B2B decision-makers, lead with risk and return and avoid emotional language; for consumers, set the scene first, then the feature. - For multilingual needs, finalise the copy in the user's language first, then create the other-language versions; taglines are never translated word for word.
© genspark-ai · Apache-2.0 · genspark-ai/genoffice