agentleFS
Sign inStart free
ASNNetworksASNNetworks/floh-skills/skills/brand-voice/SKILL.md

brand-voice

Skill0 starsChanged 4 months agoMITView on GitHub

Enforce a project's writing voice on any text the agent produces or edits — pronouns, forbidden punctuation, banned phrases, sentence rhythm. Use when writing or reviewing copy, marketing text, UI strings, documentation or commit messages for a project that has a defined voice.

57 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

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

  • 0

    Common

    Most of the 54 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Do not apply it to code comments or internal notes unless the project says so.

    line 17
  2. Distinctive:

    Punctuation the guide forbids comes back through rewriting: If a project bans em dashes, an agent that removes them in draft one …

    line 46

“Common” is measured: kept by at least 6 in 10 of the 54 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 voice guide that lives in a document gets read once. A voice guide that lives in a skill gets applied to every sentence the agent writes.

When to use this

Any time you write or edit prose that a reader outside the team will see: page copy, UI strings, emails, changelogs, documentation, social posts. Also when reviewing a pull request that touches user-facing text.

Do not apply it to code comments or internal notes unless the project says so.

How to run it

  1. Read the voice file. references/voice.md in this skill is the template. A project overrides it by putting its own VOICE.md at the repo root; that file wins on every rule it defines.
  2. Write the text.

  3. Check it before you hand it over.

    python3 scripts/check_voice.py <file-or-glob>

    The checker is mechanical: it catches the rules that can be caught mechanically (forbidden characters, banned phrases, pronoun drift). Everything it cannot catch is on you.

  4. Fix, do not annotate. A note saying "this uses 'we' but the guide says 'I'" is not the deliverable. The corrected sentence is.

The rules that get broken most

Pronouns drift under pressure. A solo operator writing "we offer" is the single most common failure, and it happens on the third paragraph, not the first: the writing slips into corporate register when the topic gets abstract. Reread specifically for this.

Punctuation the guide forbids comes back through rewriting. If a project bans em dashes, an agent that removes them in draft one reintroduces them in draft three while "improving flow". Run the checker on the final text, not the draft.

Hedging. "Kan helpen bij", "zou kunnen bijdragen aan", "is bedoeld om". If the thing works, say it works. If it does not, do not write about it yet.

The three-adjective sentence. "Een snelle, moderne en schaalbare oplossing" says nothing. One concrete claim beats three abstract ones.

What the checker cannot see

  • Whether the text is true. A perfectly on-voice sentence about a feature that does not exist is worse than an off-voice one about a feature that does.
  • Whether it is worth reading. Voice compliance is a floor.
  • Rhythm. Six sentences of identical length read as a machine wrote them, and no regex catches that. Read it aloud.

Files

  • references/voice.md — the template guide: pronouns, punctuation, banned phrases, register, and a worked before/after.
  • scripts/check_voice.py — mechanical checker. Exits non-zero on any violation, so it drops into CI.

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.

Check your setup, free