agentleFS
OneWave-AIOneWave-AI/claude-skills/brand-voice-analyzer/SKILL.md

brand-voice-analyzer

Skill378 starsChanged 52 days agoMITView on GitHub

Analyzes a company's content to extract and codify their brand voice into a comprehensive style guide. Reads website copy, blog posts, emails, and social media to identify tone, vocabulary patterns, sentence structure, personality traits, and word preferences. Generates a brand-voice-guide.md and reviews new content against it.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask which content sources are available (URLs, files, directories, pasted text).

    line 22
  2. Distinctive:

    Ask about any known brand attributes, values, or existing guidelines.

    line 23
  3. Very specific:

    Run the full voice extraction across every dimension in references/voice-dimensions.md, citing source examples per the standards in …

    line 26
  4. Distinctive:

    Read the content to be reviewed.

    line 34
  5. Very specific:

    Run the review process and produce the scored output defined in references/review-mode.md.

    line 35
  6. Very specific:

    Read the current brand-voice-guide.md.

    line 40
  7. Distinctive:

    Use markdown headers (H1-H4), tables for comparative data, blockquotes for source quotes, code blocks only for literal reproduced text.

    line 49
  8. Distinctive:

    Never fabricate examples. Every quoted example must come from actual source content.

    line 53
  9. Distinctive:

    Never assert voice attributes without evidence.

    line 54
  10. Distinctive:

    When reviewing, be specific: cite the exact word, phrase, or structure and the guide section it touches.

    line 57
  11. Distinctive:

    Treat the guide as a living document and defer to the user's judgment on subjective calls.

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Analyzer

Ingest a company's existing content, reverse-engineer the voice behind it, produce a definitive brand voice guide any writer can follow, and review new content against an established guide.

Contents

  • references/voice-dimensions.md -- the seven-axis tone spectrum, vocabulary, sentence, personality, audience, and formatting dimensions to extract
  • references/guide-template.md -- required sections, quality standards, and pre-delivery checklist for brand-voice-guide.md
  • references/review-mode.md -- process and output format for scoring content against a guide
  • references/metrics.md -- quantitative and qualitative analysis techniques and citation standards
  • references/edge-cases.md -- handling for thin corpora, multiple voices, regulated industries, rebrands, plus interaction patterns

Workflow: Create a New Voice Guide

  1. Ask which content sources are available (URLs, files, directories, pasted text).
  2. Ask about any known brand attributes, values, or existing guidelines.
  3. Collect the corpus. Pull URLs with WebFetch, locate files with Glob/Read, find public content with WebSearch. Gather website copy, 5-10 blog posts, email campaigns, social posts, sales collateral, and support content. Document each source and its word count.
  4. Confirm corpus size. Require at least 3,000 words across 2+ content types. If smaller, flag the limitation and mark affected findings as lower confidence.
  5. Run the full voice extraction across every dimension in references/voice-dimensions.md, citing source examples per the standards in references/metrics.md.
  6. Present a summary of findings for validation before generating the guide.
  7. Generate the complete brand-voice-guide.md following references/guide-template.md. Verify it against that checklist before delivery.
  8. Offer to review a sample piece of content against the new guide.

Workflow: Review Content

  1. Locate or ask for the brand-voice-guide.md.
  2. Read the content to be reviewed.
  3. Run the review process and produce the scored output defined in references/review-mode.md.
  4. Present findings with actionable, guide-referenced fixes.

Workflow: Update an Existing Guide

  1. Read the current brand-voice-guide.md.
  2. Ingest the new content sources and run extraction on the new material.
  3. Compare findings against the existing guide.
  4. Propose specific updates with rationale.
  5. Apply approved changes with Edit.

Output Standards

  • Primary output: brand-voice-guide.md. For multiple brands: brand-voice-guide-[company-name].md. Deliver review output inline unless a file is requested.
  • Use markdown headers (H1-H4), tables for comparative data, blockquotes for source quotes, code blocks only for literal reproduced text. Bold key terms on first use. No emojis.

Operating Principles

  • Never fabricate examples. Every quoted example must come from actual source content.
  • Never assert voice attributes without evidence. If the data does not support a conclusion, say so.
  • Present findings as observations, not prescriptions, until the user validates them.
  • Distinguish voice (consistent: who we are) from tone (shifts by context: how we adapt) in every guide.
  • When reviewing, be specific: cite the exact word, phrase, or structure and the guide section it touches.
  • Treat the guide as a living document and defer to the user's judgment on subjective calls.

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.