← ClaudeAtlas

brand-voice-guidelisted

Extract a brand's voice from its real writing and build a structured voice directory a team (or an AI agent) can write from consistently. Harvests existing content — homepage, blog, posts, emails, changelog — into voice-core rules, per-channel guidance, and a writing standard whose Avoid section names the banned words and voice-killing patterns, each grounded in verbatim samples. Interviews the user only to fill what the samples can't answer. Use whenever the user says "brand voice", "voice guide", "tone of voice", "voice and tone", "brand voice guide", "define our voice", "extract our voice", "style guide", "voice standard", or wants to document how their brand sounds so content stays on-brand at scale. Works across industries and channels. Builds the guide; it does not police drafts — that is the job of a separate content-quality-check skill.
esmefong/gtm-skills · ★ 0 · Data & Documents · score 72
Install: claude install-skill esmefong/gtm-skills
# Brand Voice Guide Extract how a brand actually sounds from what it has actually written, and turn it into a directory that a copywriter, a new hire, or a Claude agent can produce on-brand content from. This skill is opinionated about one thing: **a voice guide is extracted from real writing, not invented from adjectives.** "We're bold, human, and authentic" describes nothing. A verbatim line the brand wrote, and a rule named from it, describes everything. The output is a **directory of reference files** (not a single essay), so it can be consulted modularly at the moment of writing — the voice-core rules always, the relevant channel file for the piece at hand. It mirrors the structure a production content system consults before generating a word. ## What this builds (and what it doesn't) - **It builds** the voice directory: `voice-core.md` (the character), `writing-standard.md` (the concrete rules — a *Do* half and a severity-tagged *Avoid* half), per-channel files, `real-examples.md`, plus light `about-company.md` / `icp.md` context. - **It does not check drafts.** Governing new content against the guide (AI tells, template language, brand-rule violations) is the job of a separate `content-quality-check` skill. This skill produces the standard that skill enforces — the *Avoid* section of `writing-standard.md` is the part it reads. ## Inputs (harvest first, ask only for the gaps) The skill is harvest-first: it extracts as much as possible from existing writing