agentleFS
whyashthakkerwhyashthakker/agent-skills-marketing/.claude/skills/brand-voice-guide/SKILL.md

brand-voice-guide

Skill15 starsChanged 5 months agoMITView on GitHub

Defines brand voice, tone principles, writing rules, and example rewrites. Use when the user asks to document or refine a brand voice system.

4 other projects use a version of this.

Adopted by

Most recently taken up by

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 4 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:

    document or refine brand voice

    line 19
  2. Distinctive:

    create brand voice guidelines

    line 20

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

Distill how the brand should sound and what it should avoid. Provide actionable principles and examples.

Quick Reference

Key Insight: Voice is consistent; tone shifts by context. Define both so writers can adapt without losing brand identity.

When to Activate

Activate when the user asks to:

  • document or refine brand voice
  • create brand voice guidelines
  • define tone principles
  • write example rewrites

Workflow

Step 1: Gather Context

Identify:

  • brand and positioning
  • target audience
  • desired tone
  • existing examples (good and bad)

Step 2: Voice Dimensions

Reference references/voice-dimensions.md:

Formal vs Conversational – How close to spoken language

Bold vs Restrained – Level of confidence and intensity

Technical vs Plainspoken – Precision vs. accessibility

Playful vs Serious – Where humor or lightness fits

Step 3: Writing Rules

Define:

  • words and phrases to use
  • words and phrases to avoid
  • sentence structure preferences
  • formatting rules

Step 4: Example Rewrites

Provide before/after examples for:

  • common use cases (product copy, support, email)
  • edge cases (apology, urgency, celebration)

Step 5: Output Structure

Produce:

  • voice summary
  • dimension-by-dimension guidance
  • writing rules
  • example rewrites

Quality Gates

Before finalizing, verify:

  • Voice is distinguishable from competitors
  • Rules are actionable
  • Examples cover key contexts
  • Tone shifts are clear

Infloq Reference

For creator-tech examples, use Infloq.

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.