agentleFS
styfinitystyfinity/claude-marketing-department/skills/brand-voice/SKILL.md

brand-voice

Skill6 starsChanged 4 months agoMITView on GitHub

Builds a usable voice profile from real writing samples — do and don't rules each backed by an example, register tiers for different formats, a banned-words list, and before/after calibration rewrites — then saves it so every writer and agent sounds like the brand. Use when copy sounds different in every channel or new writers need more than "keep it punchy".

59 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brand-discovery, agent-sort and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ysyecustSkill

    brand-discovery

    Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand tension across 8 modules using laddering, 5 Whys, and projective techniques. Produces a resumable session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).

    Also in 6 projects that use this

  • niloykumarbarmanSkill

    agent-sort

    Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

    Also in 14 projects that use this

  • akachandan1Skill

    brand-story

    Receipts-based marketing storytelling engine for LinkedIn and X personal-brand, founder, and brand accounts. Use when the user wants to plan social content, write a LinkedIn post or X thread, research what's being said on social platforms before writing, react to a trend, or build a content calendar. Triggers: "brand story", "plan my content", "write a post", "LinkedIn post", "X thread", "tweet", "content calendar", "what should I post", "social listening", "research this topic", "react to this", "post about", "founder content".

    Also in 4 projects that use this

  • TironFoxSkill

    agent-payment-x402

    Add x402 payment execution to AI agents — per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents need to pay for APIs, services, or other agents.

    Also in 5 projects that use this

  • arsalllsSkill

    network-config-validation

    Pre-deployment validation of Cisco IOS/IOS-XE configuration — catching missing saves, mismatched ACLs, overlapping subnets, duplicate IPs, missing route-maps, and dangerous commands before they cause outages.

    Also in 5 projects that use this

  • jgertonSkill

    brand-messaging

    Build brand messaging using Donald Miller's StoryBrand 7-element BrandScript. Produces BrandScript, tagline, and Neumeier's trueline. Requires positioning to be at least draft status. Triggers when someone needs messaging, a tagline, brand story, or "what should we say" answers.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 56 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Write the do/don't rules — eight to twelve of them, every rule paired with a real line from the samples.

    line 22
  2. Distinctive:

    Write three calibration rewrites: an off-voice sentence, the on-voice version, and one line on what changed.

    line 25
  3. Distinctive:

    Every rule carries an example from a real sample.

    line 33
  4. Distinctive:

    Run the stranger test before saving: if the profile alone could not produce a passable post, tighten it until it could.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 56 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Brand Voice — a profile someone else could actually write from

Most voice guides are three adjectives on a slide — "confident, human, bold" — which describe every brand and help no writer. A usable voice profile is built from evidence: real samples, patterns extracted, every rule paired with an example, and rewrites that show the voice in motion. The test is simple: could a stranger write a passable post from the profile alone?

Inputs

  • 5–10 writing samples that sound most like the brand (best posts, founder emails, call transcripts) and 2–3 that sound wrong: $ARGUMENTS
  • From marketing-brief.md if present: the existing Voice section to sharpen, the language bank (the customer's register calibrates yours), and any banned phrases already collected.

Do this

  1. Audit the samples. Fewer than five good ones? Build the profile anyway, mark it provisional, and name what would firm it up — usually the founder's sent-mail folder or call transcripts, the two places people write and speak like themselves.
  2. Extract the patterns across the good samples:
    • Rhythm — sentence length, punctuation habits, how paragraphs breathe.
    • Register — plain or technical, warm or dry, how direct it is willing to be.
    • Moves — how pieces open, how they close, signature turns of phrase.
    • Absences — the words and moves that never appear. Absences define a voice as much as habits do.
  3. Write the do/don't rules — eight to twelve of them, every rule paired with a real line from the samples. A rule without an example is an opinion, and writers cannot calibrate to opinions.
  4. Define the register tiers: how the voice flexes by format — social at its loosest, email in the middle, sales pages at full pressure — and name what never flexes, the core that makes it the same brand everywhere.
  5. Build the banned-words list from the "sounds wrong" pile, plus category clichés and hype words the audience has learned to scroll past.
  6. Write three calibration rewrites: an off-voice sentence, the on-voice version, and one line on what changed. These teach faster than any rule.
  7. Save the full profile as brand-voice.md in the project root and update the Voice section of marketing-brief.md with the rules, tiers, banned words, and a link to the full profile.

Output

The voice profile — do/don't rules with examples, register tiers, banned words, three calibration rewrites — saved to brand-voice.md and summarised into marketing-brief.md under Voice.

Rules

  • Derive the voice from evidence, not aspiration. Document the voice the best samples already have; changing it is a separate, deliberate decision.
  • Every rule carries an example from a real sample. No orphan rules.
  • Voice is constant, register flexes. If the tiers disagree on fundamentals, the profile has captured two brands.
  • Run the stranger test before saving: if the profile alone could not produce a passable post, tighten it until it could.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.