Skip to main content
skill CX Codex

brand-voice-analyzer — Claude Code skill: setup and features

brand-voice-analyzer extracts tone, vocabulary, and structure from company copy to build a style guide and audit drafts against it.

MIT 281 installs ★ 440 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add OneWave-AI/claude-skills --skill brand-voice-analyzer -a claude-code
Open on GitHub

What brand-voice-analyzer does

This skill parses website copy, blog posts, newsletters, and social channels to isolate how an organization sounds. It tracks sentence length, vocabulary patterns, and tonal spectrums. The primary deliverable is a brand-voice-guide.md file backed by direct quotations from the source text rather than made-up samples.

Under the hood, it pairs tools like WebFetch, WebSearch, Glob, and Read to gather assets across URLs or local files. It also runs a dedicated review workflow: drafts are scored against the compiled guide, returning exact line references and concrete adjustments.

Reliable analysis requires at least 3,000 words across 2 or more content formats. Smaller sample sizes automatically lower the confidence score of the findings.

What it helps with

  • extract style guidelines from published blog posts and landing pages
  • score new drafts against an existing brand voice document
  • update brand guides when tone shifts across recent copy
  • pinpoint non-compliant phrasing and sentence structures

Example prompts for the agent

  • Analyze our site and newsletters to draft brand-voice-guide.md
  • Score draft.md against brand-voice-guide.md and list required fixes
  • Update brand-voice-guide.md using the files in /content/updates

How to install brand-voice-analyzer

1Skills CLI (Vercel)

npx skills add OneWave-AI/claude-skills --skill brand-voice-analyzer -a claude-code

2Manually: put the files in place

~/.claude/skills/brand-voice-analyzer/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/brand-voice-analyzer/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about brand-voice-analyzer

How to install brand-voice-analyzer in Claude Code?

Run npx skills add OneWave-AI/claude-skills --skill brand-voice-analyzer -a claude-code in your terminal. The file is placed at ~/.claude/skills/brand-voice-analyzer/SKILL.md.

What does brand-voice-analyzer do?

It extracts voice attributes, tone dimensions, and vocabulary patterns from source text, producing a reusable Markdown style guide.

What is the minimum corpus size needed for the analysis?

It expects at least 3,000 words spanning at least 2 distinct types of content.

Source text

SKILL.md · MIT
---
name: brand-voice-analyzer
description: 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.
tools: Read, Write, Edit, Glob, Grep, Bash, WebFetch, WebSearch
model: inherit
---

# 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.

© OneWave-AI · MIT · OneWave-AI/claude-skills

Similar skills

All skills for Marketing and content →

From the same set185

The whole set →
security-pentest-planner security-pentest-planner builds a penetration test plan for web applications: analyzes code, API routes, authentication and infrastructure configs, generates pentest-plan.md with concrete test cases. CX Codex +1 297installs tech-due-diligence tech-due-diligence scans the code of a company you plan to buy or fund and writes tech-dd-report.md, with risk ratings and a go/no-go verdict. CX Codex +1 294installs workflow-automator The workflow-automator skill turns a description of a manual business process into an automation plan. It produces a Markdown document with diagrams, tool suggestions, and implementation steps. CX Codex +1 285installs sow-generator sow-generator turns a project brief into a Statement of Work with scope, deliverables, milestones, and payment terms. Use it to prepare a consulting engagement document. CX Codex +1 284installs weekly-business-report weekly-business-report is a Claude Code skill that collects weekly KPIs from enabled sources, compares them with targets and prior weeks, and saves a report. It brings business figures into a shared weekly view. CX Codex +1 276installs client-health-dashboard client-health-dashboard builds a client health view from CRM and engagement data, then produces a risk-ranked report with scores, trends, and next actions. CX Codex +1 276installs hiring-scorecard Builds a structured hiring scorecard for any role with weighted competencies, interview questions, evaluation matrix, red/green flags, and reference check questions. CX Codex +1 268installs sub-agent-orchestrator sub-agent-orchestrator chains different agents so each step feeds the next, with the flow defined in YAML. Handles retries, timeouts and parallel branches. CX Codex +1 267installs

Project sponsors

Companies that keep this analytics open