CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

72%

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

Fix and improve this skill with Tessl

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

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.

A well-organized, checklist-style guidelines skill with concrete do's/don'ts, vocabulary substitutions, and contrasting examples. Its weaknesses are the absence of any apply-and-verify workflow for checking copy against the rules, and a footer full of time-sensitive metadata (date, version, model list) that adds tokens without operational value.

Suggestions

Add a short application workflow, e.g., 1) draft the copy, 2) check it against the Do's/Don'ts lists, 3) scan for Avoid Terms and substitute Preferred Terms, 4) re-verify before delivering.

Remove or relocate the time-sensitive footer (Last Updated date, Claude Code Version, Compatible Models list) — version numbers and dates go stale and add token cost without guiding behavior.

Tighten the Brand Identity section (mission/values) or trim redundant rules to reduce body length toward the lean single-file ideal.

DimensionReasoningScore

Conciseness

The body is mostly lean checklists ('Keep sentences under 20 words', 'Use active voice: ...') with no conceptual over-explanation. However, the footer embeds time-sensitive information outside any deprecated/old-patterns section — '**Last Updated**: August 4, 2026', '**Claude Code Version**: 2.1.220', and a 'Compatible Models' list — which the guidelines explicitly penalize. This matches anchor 3 ('mostly efficient but includes some unnecessary content that could be tightened') rather than anchor 4's only-minor trimmable excess.

3 / 5

Actionability

As an instruction-only skill, the guidance is concrete: explicit do's and don'ts, term substitutions with preferred/avoid pairs ('Use "use" not "utilize"', 'Agent (not "bot")'), and a good/bad example pair with explanations of why each works. It matches anchor 4 ('mostly executable guidance with minor gaps'), falling short of anchor 5 only because the examples cover a single case and no application procedure is given.

4 / 5

Workflow Clarity

The skill presents reference rules but never sequences how to apply them — there is no step for evaluating draft copy against the do's/don'ts, checking vocabulary substitutions, or verifying the final output, i.e., no validation checkpoint. This fits anchor 3 ('sequence present but checkpoints missing or implicit' — here the single task is discernible but unvalidated) and the skill is neither destructive nor batch, so no hard cap applies; it cannot reach 5 because the single action is not made unambiguous by any apply/verify step.

3 / 5

Progressive Disclosure

The content is appropriately contained in one file (no external references needed, and none are referenced), organized under clear headers (Brand Identity, Tone of Voice, Writing Guidelines, Vocabulary, Examples). This lands at anchor 4 ('good structure; most content appropriately placed; minor organization gaps'): the body is slightly long for a single file and the trailing metadata block clutters otherwise clean navigation, keeping it below anchor 5.

4 / 5

Total

14

/

20

Passed

Description

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

A solid description with an explicit and natural 'Use when...' trigger clause covering multiple user phrasings. Its main weakness is that the capability statement is a single general action ('ensure communication matches guidelines') without concrete operations, which limits specificity and completeness.

Suggestions

Enumerate concrete actions in the capability statement, e.g., 'Review, revise, and generate copy against brand voice, tone, and vocabulary guidelines.'

Add common synonyms users might say to the trigger clause, such as 'copywriting', 'messaging', or 'brand guidelines'.

Clarify the scope of 'all communication' (e.g., emails, docs, release notes, landing pages) to sharpen both specificity and distinctiveness.

DimensionReasoningScore

Specificity

"Ensure all communication matches brand voice and tone guidelines" names the domain (brand voice/tone) and one general action (ensure compliance), but lists no concrete operations such as reviewing, rewriting, or checking copy against specific criteria. This matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') and is below anchor 4, which expects several specific actions; it is above anchor 2 because the domain and action are stated, not merely generic.

3 / 5

Completeness

Both 'what' ("Ensure all communication matches brand voice and tone guidelines") and 'when' ("Use when creating marketing copy... or when users mention brand voice, tone, or writing style") are present and explicit. It falls below anchor 5 because the 'what' is a single general action rather than a list of concrete capabilities, matching anchor 4 ('both present; when could be more explicit or what could be more specific').

4 / 5

Trigger Term Quality

The 'when' clause includes natural phrases users would say: 'creating marketing copy, customer communications, public-facing content', 'brand voice, tone, or writing style'. Good coverage matching anchor 4, but a few natural synonyms are missing (e.g., 'copywriting', 'messaging', 'brand guidelines', 'tone of voice'), which keeps it below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Triggers like 'brand voice', 'tone', 'marketing copy' carve a fairly distinct niche with minimal overlap risk against unrelated skills. 'All communication' and 'writing style' leave minor overlap with general writing/editing skills, matching anchor 4 ('mostly distinct; minor overlap risk with closely related skills') rather than anchor 5's fully distinct niche.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

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.