CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brand-voice

Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.

67

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, highly actionable instruction skill: concrete sourcing rules, a specific collection workflow, an exact output schema held in a single well-placed reference file, and named hard bans. The only notable gaps are a couple of trimmable editorial lines and the absence of an explicit validation step for the generated voice profile.

DimensionReasoningScore

Conciseness

The body is dense and operational throughout (e.g. 'direct, compressed, concrete', 'parentheticals are for qualification, narrowing, or over-clarification'), with almost no explanation of concepts Claude already knows. A few editorial lines could be trimmed ('The point is not literary criticism. The point is operational reuse.'), which matches anchor 4's 'minor instances of over-explanation that could be trimmed' rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

The guidance is fully executable for an instruction-only skill: a 4-tier source priority list, numbered collection steps with concrete parameters (5-20 samples, 'use `x-api` to pull recent original posts'), a 9-item extraction checklist, named hard bans, and an output contract pointing to an exact schema in references/voice-profile-schema.md, which exists and provides a copy-paste-ready template. This matches anchor 5's fully executable, specific-examples-cover-common-cases.

5 / 5

Workflow Clarity

The sequence is coherent and clearly ordered (When to Activate -> Source Priority -> Collection Workflow -> What to Extract -> Output Contract -> Downstream Use), but there is no validation checkpoint confirming the produced VOICE PROFILE against the source set before reuse. Anchor 4's 'clear sequence with most checkpoints present; minor validation gaps' fits; the skill is not a destructive or batch operation, so the workflow-clarity cap does not apply.

4 / 5

Progressive Disclosure

The body is a clear, well-sectioned overview, and its single bundle reference ('Use the schema in [references/voice-profile-schema.md](references/voice-profile-schema.md)') is real, one level deep, clearly signaled at the point of need, and holds the bulk of the output template. This matches anchor 5's clear overview with well-signaled one-level-deep references and appropriate content split.

5 / 5

Total

18

/

20

Passed

Description

75%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 well-constructed description with a clear what, an explicit 'Use when...' clause, distinct niche framing, and concrete source-type keywords. The main weaknesses are a when-clause that covers only one of the skill's several use cases and missing common synonyms like 'brand voice' and 'tone'.

Suggestions

Broaden the 'Use when...' clause to cover the other stated use cases, e.g. 'Use when the user wants content, outreach, or launch posts in their own voice, or wants to match a known author's tone across X, LinkedIn, and email.'

Add common trigger synonyms such as 'brand voice', 'tone', and 'make this sound like me' so the description matches how users naturally phrase the request.

Consider mentioning the reusable output artifact ('produces a reusable VOICE PROFILE block') to sharpen the what and distinguish it from one-off style mimicry.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows') with enumerated inputs and outputs. It falls short of anchor 5's 'multiple specific concrete actions; comprehensive coverage' since the action verbs are limited to build and reuse.

4 / 5

Completeness

Explicitly answers both what (build and reuse a source-derived writing style profile) and when ('Use when the user wants voice consistency without generic AI writing tropes'). The when-clause is present and explicit but covers only the voice-consistency trigger, missing triggers for the outreach, launch-post, and channel-adaptation use cases, so anchor 4 ('when could be more explicit or specific') fits better than anchor 5.

4 / 5

Trigger Term Quality

Includes natural phrases users would say such as 'voice consistency', 'writing style profile', and 'generic AI writing tropes', plus source-type keywords (posts, essays, launch notes, docs, site copy). A few natural synonyms are missing (e.g. 'brand voice', 'tone', 'sound like me'), matching anchor 4's 'good keyword coverage; a few natural terms missing' rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

'Voice consistency' and 'generic AI writing tropes' carve a fairly distinct niche with a clear dedicated purpose, but the tail 'content, outreach, and social workflows' is broad enough to overlap with general content-writing skills, matching anchor 4's 'mostly distinct; minor overlap risk' rather than anchor 5's minimal conflict risk.

4 / 5

Total

16

/

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

affaan-m/ECC

Path

.agents/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.