agentleFS
Sign inStart free
teemutuoteemutuo/super-intelligent-AI-setup/skills/01-brand-voice/SKILL.md

brand-voice

Skill0 starsChanged 6 months agoMITView on GitHub

Brand identity, voice calibration, and visual standards for any company. Drop this into your skills directory, fill in the placeholders, and Claude will write in your brand voice every time. Triggers on: writing, communication, presentation, document, deck, brand, tone, 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

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

  • 0

    Common

    Most of the 54 edited versions we read keep these.

  • 7

    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:

    Start every page with a small uppercase label above the bold heading

    line 50
  2. Distinctive:

    Use plain language. Glossary the jargon

    line 53
  3. Distinctive:

    No em dashes in text. Use commas, periods, or restructure

    line 57
  4. Distinctive:

    No emoji unless asked

    line 58
  5. Distinctive:

    No marketing superlatives ("revolutionary", "game-changing")

    line 59
  6. Distinctive:

    No filler like "delve", "in today's fast-paced world", "ever-evolving landscape"

    line 60
  7. Distinctive:

    When asked to draft a [[email / memo / slide / report]], always:

    line 64

“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 · Template

Replace every [[BRACKETED PLACEHOLDER]] with your company specifics. Keep the structure.

Core Identity

Company name: [[YOUR COMPANY]] Tagline: [[YOUR TAGLINE]] One-line positioning: [[WHAT YOU DO, FOR WHOM, AND WHY IT MATTERS]]

Voice Attributes

Choose three to five short words that describe how your brand sounds. Examples in a real-world brand: Ambitious, Humane, Joyful, Responsible. Use words that you would put on a poster.

  • [[ATTRIBUTE 1]]: [[ONE-LINE DEFINITION]]
  • [[ATTRIBUTE 2]]: [[ONE-LINE DEFINITION]]
  • [[ATTRIBUTE 3]]: [[ONE-LINE DEFINITION]]
  • [[ATTRIBUTE 4]]: [[ONE-LINE DEFINITION]]

Colors

TokenHexUsage
Primary accent[[#PRIMARY]]Headers, active indicators, key highlights
Secondary accent[[#SECONDARY]]Links, badges, info elements
Text#18181bBody text on light backgrounds
Page background#ffffffDefault page background
Subtle background#fafafaCard hover, alternating rows

Rule of two: pick one to two accent colors per page. Resist using all of them.

Typography

  • Body font: 'Inter', -apple-system, BlinkMacSystemFont, sans-serif
  • Anti-alias: always set -webkit-font-smoothing: antialiased
  • Weights: 400 body, 600 labels, 700 headings, 800 hero

What to Always Do

  • Start every page with a small uppercase label above the bold heading
  • Light theme as default. Dark only if user explicitly asks
  • Cite sources at the bottom of any data-heavy output
  • Use plain language. Glossary the jargon

What to Never Do

  • No em dashes in text. Use commas, periods, or restructure
  • No emoji unless asked
  • No marketing superlatives ("revolutionary", "game-changing")
  • No filler like "delve", "in today's fast-paced world", "ever-evolving landscape"

Sample Outputs

When asked to draft a [[email / memo / slide / report]], always:

  1. Lead with the headline message in one sentence
  2. Give the three reasons or facts that support it
  3. Close with the action or decision needed

This skill applies to any text output unless the user explicitly overrides it.

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