Purpose: Give Claude a structured understanding of your brand voice, tone, visuals, and channel behaviour so every piece of content it produces sounds like your company — not like a chatbot wearing business casual.
Who this is for: Marketing teams, agency operators, brand managers, and anyone who has ever looked at Claude's output and thought "this is fine but it sounds like everyone else."
What you'll build: A modular skill — a folder containing a SKILL.md and supporting reference files — that Claude reads before writing anything for your brand. You upload it via Customize > Skills, and it auto-loads whenever you prompt for brand content. The skill has five core files, a reference corpus of your best work, and a QA rubric that catches drift before it reaches your audience.
Time estimate: 4–6 hours for the first build. 1–2 hours quarterly to maintain.
You need three things in place before any of this works.
1. A Claude account with Skills enabled. Skills are available on Pro, Team, and Enterprise plans. You upload them via Customize > Skills in Claude.ai — no special settings needed. On Team and Enterprise plans, an admin may need to enable Skills at the org level first. You do not need Code Execution turned on. Skills are instruction files Claude reads, not code it runs. If your skill later includes scripts (unlikely for a brand skill), you'd need it then. For now, don't worry about it.
2. Access to your existing brand materials. Style guides, tone docs, brand decks, founder manifestos, campaign briefs, customer support templates, social guidelines — whatever exists. Most of it will be scattered. That's normal. The first phase is gathering it.
3. A decision-maker in the room. Someone who can say "that sounds like us" and "that doesn't." If you're the founder, that's you. If you're an agency building this for a client, get a named approver before you start. Nothing kills a brand skill faster than building it to one person's taste and having another person reject it.
A Skill is a folder containing a SKILL.md file plus any supporting files (your brand foundation, voice guide, visual guidelines, etc.). You ZIP the folder and upload it via Customize > Skills in Claude.ai. Once uploaded, the skill appears in your skills list and can be toggled on or off.
Skills are not Projects. Projects are separate workspaces with their own knowledge files and system prompts. Skills are modular — they work across any conversation where they're enabled. Claude reads the skill's description and auto-loads it when your prompt matches what the skill is for. You don't need to mention the skill by name every time. If you ask Claude to "write a product launch email," and your brand skill's description includes "email campaigns," it loads automatically.
This is why the description in your SKILL.md matters so much. It's the trigger. Get it wrong and the skill never fires. Get it right and it shows up exactly when you need it.
One thing to know about triggering. Claude only consults a skill when the task feels complex enough to warrant it. A simple request like "write me a tagline" might get answered directly from Claude's general knowledge — the skill never loads. Longer, more specific requests ("write a 300-word product description for our new hydration serum, warm and confident tone, include three key ingredients") are much more likely to trigger the skill automatically. If you want to guarantee the skill fires, mention the brand by name in your prompt or reference something specific from the skill, like a register level. This isn't a flaw — it's how skills are designed. They're specialists, not background wallpaper.
Goal: Gather everything your brand has ever said, then sort it into what to keep, what to kill, and what to learn from.