← ALL SKILLS
── SKILL
brand-voice-guide

Make every AI output sound like you, not like AI.

Sets your voice pillars, tone by context, a do and do-not word list, and sample lines the model can pattern-match, so the whole repo writes in your voice.

In plain English: “How should we sound?

Inside: The voice pillars, tone-by-context, the do and do-not list, and sample lines.

HOW TO USE THIS SKILL
1
In Claude Code (one command)
Copy the install line, paste it into your terminal, and restart Claude Code. The skill installs itself to ~/.claude/skills/ and runs automatically when it is relevant.
2
In Claude, ChatGPT, or a Project (no terminal)
Open the file, then upload it to your chat or paste its contents in. A skill is just a markdown file of instructions, so any capable AI can follow it.
New to skills? A skill is a plain-text file that teaches your AI a workflow. Point any capable assistant at it and it follows the steps, on your data.

Runs today on what you paste. Connect any of these and it pulls live, cross-references, and goes deeper, no code required. See how to connect in Claude or ChatGPT.

Runs in your AI
ClaudeChatGPTGeminiCopilot
Docs, repo & knowledge
NotionGoogle DriveConfluenceGitHub

Brand Voice and Tone: sound like you, not like AI

What this does

Turns "make it sound like us" into a guide a model can actually follow: the voice pillars, the tone by context, a do and do-not word list, and sample lines to pattern-match. Without this, every skill output drifts to generic AI voice. With it, the whole repo writes in your voice.

What you'll need (reads)

A few things you have already published that sound right (a post, an email, a page) and a couple that sound wrong. Your positioning from the Positioning skill, so voice and message agree. No connectors required.

The method

  1. Name 3 to 5 voice pillars. Adjectives with teeth: "plain, not corporate", "receipts over adjectives", "direct, no hedging". Each gets a one-line rule.
  2. Set the tone by context. How you sound in a cold email vs a nurture vs a landing page vs a support reply. Same voice, different dial.
  3. Write the do and do-not word list. The words and phrases you use, and the ones you never do (the AI tells, the corporate filler, the cliches). This is the fastest guardrail.
  4. Give sample lines. Two or three real lines that are unmistakably you, each next to its generic-AI counterpart, so the model can copy yours and avoid the other.
  5. State the one test. The single check any draft must pass to sound like you, for example "would I actually say this out loud?".

Failure points

  • Vague adjectives ("professional yet approachable") that no model can act on.
  • A do list with no do-not list, so the AI tells survive.
  • No sample lines, so "our voice" stays a feeling instead of a pattern.

The receipt (writes)

[your voice pillars, the do and do-not list, and 3 sample lines with their generic counterparts. This becomes the voice layer of context/positioning.md]

Next move

Hand the voice to the Context Pack so CLAUDE.md carries it into every session. Built GTM. Receipts only.

── GET NEW SKILLS IN YOUR INBOX

One operator-built skill a week. Free.