CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brand-voice

Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples. Use this skill whenever the user wants to define how a brand sounds, write a voice and tone document, audit existing copy for voice consistency, train a team or AI assistant on brand voice, or refine the personality of brand writing. Triggers on brand voice, voice and tone, tone of voice, writing voice, brand personality, copy voice, voice document, voice guidelines, how should we write, voice training, voice audit. Also triggers when the user has copy that 'feels off' and the underlying issue is voice, even if not stated explicitly. On a voice consistency check, this skill owns defining and documenting the voice system; use `editorial-qa` when a specific draft needs checking against an existing system before it publishes.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A well-structured instruction skill: an actionable 4-layer framework with concrete counts and examples, a validated 9-step workflow, and clean two-file progressive disclosure verified against the actual bundle. The only weakness is minor redundancy with the reference bundle and a few rationale lines that could be trimmed.

Suggestions

Trim the Layer 1 rationale paragraph ('The "not" half is what saves writers from overshooting...') — it restates the 'Why the not Y matters' section already in references/voice-frameworks.md.

Cut the duplicate restatement after the tone table ('Voice stays consistent across all of these. Tone is what shifts.') since the section already opens with 'Voice is constant. Tone adapts to context.'

DimensionReasoningScore

Conciseness

The body is largely lean and instructional — counts, tables, and checklists rather than padded prose — but a few lines explain rationale Claude doesn't need or duplicate the reference bundle: "The 'not' half is what saves writers from overshooting. 'Confident' alone produces swagger..." restates voice-frameworks.md's 'Why the not Y matters' section, and "Voice stays consistent across all of these. Tone is what shifts." repeats the section's opening claim. This fits anchor 4 ('Efficient; minor instances of over-explanation that could be trimmed') — better than 3 because the padding is a handful of lines, not sections.

4 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: exact counts ("Pick 3 to 5 attributes", "List 8 to 15 contexts", "The floor is 15 paired examples" with a stated practical ceiling of 25), a 14-row tone-shift table, a 7-section output format, and a worked attribute-pairing list. This matches anchor 5's 'specific examples cover the common cases' — the rubric's code-vs-instruction note says executable guidance without code is not penalized.

5 / 5

Workflow Clarity

The 9-step workflow is clearly sequenced with an entry-point decision (step 1 delegates to the 'Choosing a framework' section in references/voice-frameworks.md, which exists) and an explicit validation loop: step 7's stress test scores output '1 to 5 against each attribute' with failure interpretation ('anything scoring below 3... Below 3 means the doc is incomplete, not that the copy needs another pass'). This matches anchor 5 ('explicit validation steps; feedback loops').

5 / 5

Progressive Disclosure

SKILL.md is an overview of the method with exactly two one-level-deep references, both real files (references/voice-document-template.md and references/voice-frameworks.md), each clearly signaled with its purpose, plus a dedicated 'Reference files' section. Content splitting is deliberate — the template owns the content-type list ('one list to maintain rather than two that drift apart'). This matches anchor 5 ('Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'); the inline tone table and attribute pairs are core method patterns, not misplaced reference material.

5 / 5

Total

19

/

20

Passed

Description

100%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.

An exemplary description: it states what the skill produces, gives an explicit 'Use this skill whenever...' clause, lists natural trigger terms with synonyms, and even disambiguates the closest sibling skill. All four dimensions sit at the top anchor.

DimensionReasoningScore

Specificity

"Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples" names the domain and enumerates five concrete deliverable components, with additional actions ("audit existing copy for voice consistency, train a team or AI assistant on brand voice, or refine the personality of brand writing"). This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage' — not 4, since coverage of the skill's actions is comprehensive rather than having minor gaps.

5 / 5

Completeness

The description explicitly answers both questions: 'what' via "Develop or document a complete brand voice and tone system covering..." and 'when' via "Use this skill whenever the user wants to..." plus an explicit trigger-term list. This matches the anchor 'Clearly and explicitly answers both what AND when with concrete trigger phrases'; a score of 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

"Triggers on brand voice, voice and tone, tone of voice, writing voice, brand personality, copy voice, voice document, voice guidelines, how should we write, voice training, voice audit" provides comprehensive natural-term coverage including synonyms users would actually say. It stays at 5 rather than dropping to 4 because no common variation (audit, training, document, personality, tone) is missing; file extensions are inapplicable to a non-file skill.

5 / 5

Distinctiveness Conflict Risk

The skill has a clear niche (defining and documenting brand voice) and explicitly resolves the nearest conflict: "On a voice consistency check, this skill owns defining and documenting the voice system; use `editorial-qa` when a specific draft needs checking against an existing system before it publishes." This matches anchor 5 ('Clear niche with distinct triggers; minimal conflict risk') — the disambiguation goes beyond the minor-overlap profile of a 4.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

rampstackco/claude-skills

Path

skills/brand-voice/SKILL.md

Reviewed

Table of Contents

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.