agentleFS
frankxaifrankxai/creator-skills/skills/brand/brand-voice/SKILL.md

brand-voice

Skill6 starsChanged 47 days agoMITView on GitHub

Apply and enforce brand voice across all content creation. Manages voice attributes, tone adaptation by channel, style rules, and terminology. Use when writing content, reviewing drafts, or defining brand voice for a new project. Loads voice config from CREATOR.md or creator-memory/voice.md.

60 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-sort, brand-discovery 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.
  • 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

  • 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

  • posteverywhereSkill

    agency-clients

    Work safely across several clients or brands in PostEverywhere. Use when the user manages social media for more than one client, brand or business, mentions a client by name, asks to switch clients, or when the connected accounts belong to different companies.

    Also in 4 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

  • posteverywhereSkill

    cross-post-video

    Post one video to several platforms with PostEverywhere, with the right title and caption for each. Use when the user wants to share a video, Reel, Short or TikTok across TikTok, Instagram Reels, YouTube Shorts, LinkedIn and Facebook Reels, or asks to "post this video everywhere".

    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

  • +5 more from posteverywhere

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 56 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write in a consistent voice — not just tone, but the specific fingerprint of how a creator communicates.

    line 8
  2. Distinctive:

    Before writing, check for voice config in this order:

    line 19
  3. Distinctive:

    If neither exists: ask user to describe their voice, or offer to initialize

    line 22
  4. Distinctive:

    Never: spiritual language, guru tone, lazy CTAs ("drop a comment below")

    line 66
  5. Distinctive:

    When writing, run this checklist:

    line 70
  6. Distinctive:

    Read the voice attributes from CREATOR.md

    line 71
  7. Distinctive:

    Check for anti-patterns (things this creator never says)

    line 73
  8. Distinctive:

    Verify tone matches the channel rules

    line 74
  9. Distinctive:

    Check terminology — any flagged words used?

    line 75
  10. Distinctive:

    Check for voice documentation in this priority order:

    line 87
  11. Very specific:

    If none found: ask the user to describe their voice, or run /creator-sprint

    line 91

“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

Write in a consistent voice — not just tone, but the specific fingerprint of how a creator communicates.

Voice vs. Tone

Voice is fixed. It's the personality — what the brand always sounds like. Tone is variable. It's the emotional inflection applied to the voice based on context.

A creator's voice stays consistent across channels. Tone adapts: more formal on LinkedIn, punchier on X, warmer in email.

Voice Loading

Before writing, check for voice config in this order:

  1. CREATOR.md — voice section (quick ref, covers 90% of cases)
  2. creator-memory/voice.md — full documentation with examples
  3. If neither exists: ask user to describe their voice, or offer to initialize

The 5 Voice Components

A complete voice profile covers:

1. Voice Attributes (3-5 maximum)

Each attribute defined as:

  • We are: what it means in practice
  • We are not: the misinterpretation to avoid
  • Sounds like: example sentence
  • Never sounds like: anti-example

Example for "Cool Authority":

  • We are: confident, precise, lets the work speak
  • We are not: arrogant, dismissive, or name-dropping
  • Sounds like: "[Specific result]. Here's what that teaches you about [topic]."
  • Never sounds like: "As a top AI architect, I know better than most that..."

2. Audience Definition

  • Who the primary audience is
  • What they already know (don't over-explain)
  • What they want from this creator
  • How they expect to be addressed (peer, student, collaborator)

3. Content Pillars

3-5 core themes the creator consistently covers. Every piece of content should belong to one. Defined with topic focus, audience, and core argument.

4. Tone Adaptation Rules

How the voice shifts by context while staying recognizably consistent.

ChannelTone shiftExample
Long-form blogEducational, complete, evidence-basedFull arguments, examples, conclusions
LinkedInProfessional, thought-provoking, personalFirst-person insight, business framing
X/TwitterDirect, punchy, opinionatedShort sentences, bold claims
EmailPersonal, warm, action-oriented"You" framing, clear next step
VideoConversational, energeticShorter sentences, visual language

5. Terminology Rules

Preferred and avoided terms. Examples:

  • "creators" not "influencers"
  • "ships" not "launches" (for product releases)
  • "AI music" not "generated music"
  • Never: spiritual language, guru tone, lazy CTAs ("drop a comment below")

Applying Voice to Content

When writing, run this checklist:

  1. Read the voice attributes from CREATOR.md
  2. Draft the opener — rewrite until it sounds like the creator
  3. Check for anti-patterns (things this creator never says)
  4. Verify tone matches the channel rules
  5. Check terminology — any flagged words used?

Red flags requiring revision:

  • Opener starts with "I" (usually weak, unless intentional personal story)
  • More than one "!" in a piece
  • "Amazing", "awesome", "incredible" (generic, not precise)
  • "In today's fast-paced world..." (stock opener, never use)
  • Passive voice where active works better
  • Hedging: "I think", "maybe", "possibly" (unless intentional)

Loading Voice Config

Check for voice documentation in this priority order:

  1. CREATOR.md in the current project (hot cache — covers 90% of requests)
  2. creator-memory/voice.md in the current project (full documentation)
  3. Project CLAUDE.md — look for a "Brand Positioning" or "Voice" section
  4. If none found: ask the user to describe their voice, or run /creator-sprint

See references/voice-frameworks.md for the full voice documentation template and attribute definition system.

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.