agentleFS
0xelitesystem0xelitesystem/agent-skill-blueprints/skills/brand-voice/SKILL.md

brand-voice

Skill2 starsChanged 7 months agoMITView on GitHub

Apply a configured brand voice and tone guide to drafts, rewrites, and edits. Use whenever the user wants text edited to match their team's voice, asks for tone adjustments, or wants drafts brought into compliance with a style guide. Triggers on "rewrite in our voice", "apply our tone", "edit this draft", "make this sound like us", "fix the voice", or any rewrite request where consistency with a brand style is the goal. Always read references/brand-voice.md before making edits, and use this skill rather than free-form rewriting when style consistency matters.

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

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 55 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read references/brand-voice.md in full before editing anything.

    line 12
  2. Distinctive:

    Run the rewrite pass below.

    line 14
  3. Distinctive:

    Check it against the voice attributes in the reference file.

    line 21
  4. Distinctive:

    Check it against the banned-words list.

    line 22
  5. Distinctive:

    Check it against the preferred-phrasings list.

    line 23
  6. Distinctive:

    Default-AI patterns that creep in (em-dashes, "not just X but Y", tricolon abuse)

    line 40
  7. Very specific:

    If references/brand-voice.md is missing, or contains only the placeholder template with no user content, do not guess at the voice.

    line 60

“Common” is measured: kept by at least 6 in 10 of the 55 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

Applies a configured voice and tone guide to drafts. The voice itself lives in references/brand-voice.md so it can be customized without touching the skill logic.

Workflow

  1. Read references/brand-voice.md in full before editing anything.
  2. Identify the input: a draft pasted by the user, an uploaded file, or a section of an existing document.
  3. Run the rewrite pass below.
  4. Output the rewritten version, then a short audit of what changed.

Rewrite pass

For each paragraph in the input:

  • Check it against the voice attributes in the reference file.
  • Check it against the banned-words list.
  • Check it against the preferred-phrasings list.
  • Rewrite if any check fails. Leave alone if all pass.
  • Preserve the original meaning and key facts. Only change how it is said.

What to preserve

  • Numbers, dates, names, quotes (exact)
  • Section structure (headings, ordering, list items)
  • Technical accuracy (do not soften precise language into vague language)
  • Length within plus or minus 15% unless the user asked for shorter or longer

What to change

  • Word choice that violates the banned-words list
  • Sentence rhythm that conflicts with the stated voice (e.g., long flowing prose when the voice is "punchy")
  • Formality level (casual versus formal)
  • Filler and hedging that is not in the voice
  • Default-AI patterns that creep in (em-dashes, "not just X but Y", tricolon abuse)

Output format

Render in two parts:

## Rewritten

<the full rewritten text>

## Changes

- <one-line summary of the most important change>
- <next change>
- (up to 5 total)

When the reference file is missing or empty

If references/brand-voice.md is missing, or contains only the placeholder template with no user content, do not guess at the voice. Tell the user the reference file needs content first, and offer to interview them with three specific questions:

  1. What three adjectives describe your voice? (e.g., direct, warm, technical)
  2. What words or phrases do you ban?
  3. Paste two sentences in your voice and two that fail.

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.