brand-voice

Ensure all communication matches brand voice and tone guidelines. Use when creating marketing copy, customer communications, public-facing content, or when users mention brand voice, tone, or writing style.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./03-skills/brand-voice/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-organized, actionable brand-voice reference with concrete rules, vocabulary swaps, and worked good/bad examples, but it reads as a passive style sheet rather than a workflow — no apply-then-verify sequence — and carries time-sensitive footer metadata that slightly dilutes conciseness.

Suggestions

Reframe the guidance as a short workflow with a verification step, e.g. 'When drafting communication: (1) apply the Do's and preferred vocabulary, (2) scan for Don'ts and avoided terms, (3) re-read for tone before finalizing.'

Move or remove the time-sensitive footer metadata ('Last Updated', 'Claude Code Version', 'Compatible Models') — these add tokens and will go stale; if needed, relocate version info to a deprecated/changelog section.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient bullet lists that avoid over-explaining known concepts, but it includes obvious value restatements ('Make complex things simple', 'Rock-solid execution') and a footer with time-sensitive metadata ('Last Updated: August 4, 2026', 'Claude Code Version: 2.1.220', 'Compatible Models') outside any deprecated section, which the guidelines penalize — matching anchor 3.	3 / 5
Actionability	Concrete, specific guidance is provided throughout — Do's/Don'ts with worked examples ('Claude generates reports' not 'Reports are generated by Claude'), preferred/avoid vocabulary with explicit replacements, and good/bad examples with rationale — making it mostly executable for an instruction skill, just short of anchor 5 since application remains judgment-based.	4 / 5
Workflow Clarity	The content is a passive reference (rules, vocabulary, examples) with no explicit process sequence or validation checkpoint such as 'review your draft against the Don'ts list', so despite being a simple single-purpose skill the lack of any framed workflow or verification step places it at anchor 3.	3 / 5
Progressive Disclosure	The single ~75-line file is well-organized with clear section headers (Overview, Brand Identity, Writing Guidelines, Vocabulary, Examples) and no nested references, sitting just above the 50-line simple-skill threshold with only minor organization gaps from the metadata footer — matching anchor 4.	4 / 5
	Total	14 / 20 Passed

Description

65%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has a strong, explicit 'Use when...' trigger clause with natural, well-chosen keywords and a clear niche, but its 'what' is vague — 'ensure all communication matches' states a goal rather than concrete actions, capping specificity and completeness at the mid-high range.

Suggestions

Replace the generic verb 'Ensure all communication matches' with concrete actions, e.g. 'Rewrites and reviews marketing copy, customer communications, and public-facing content to align with brand voice and tone guidelines.'

Add a few natural trigger synonyms such as 'brand guidelines', 'messaging', or 'brand style' to broaden keyword coverage toward comprehensive.

Dimension	Reasoning	Score
Specificity	The phrase 'Ensure all communication matches brand voice and tone guidelines' names the domain but the action ('ensure...matches') is a generic goal rather than concrete operations like rewrite, review, or transform, matching anchor 2 over anchor 3 which requires 1-2 concrete actions.	2 / 5
Completeness	Both 'what' ('Ensure all communication matches brand voice and tone guidelines') and an explicit 'when' with concrete triggers are present, but the 'what' is a single generic action — weaker than anchor 5's multi-action example — placing it at anchor 4.	4 / 5
Trigger Term Quality	Natural trigger terms 'marketing copy, customer communications, public-facing content, brand voice, tone, writing style' cover what users would say with good synonym coverage, but a few natural variations are missing so it sits just below anchor 5's comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Brand voice and tone form a clear niche with distinct triggers, with only minor overlap risk against general writing or marketing skills via 'writing style' and 'marketing copy', matching anchor 4 rather than the minimal-conflict anchor 5.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: luongnv89/claude-howto
Path: 03-skills/brand-voice/SKILL.md
Commit: 1c04dbf

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.