CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

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

93%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, high-signal instructional skill: lean sections, concrete numeric guidance, a real and well-linked schema reference, and a clearly sequenced pipeline from source selection to downstream reuse. The only meaningful gap is the absence of an explicit validation checkpoint where drafted output is checked against the profile and Hard Bans.

DimensionReasoningScore

Conciseness

Lean, bullet-driven body with zero padding: "The point is not literary criticism. The point is operational reuse." and "Do not use generic platform exemplars as source material." — every line adds guidance Claude could not infer. No concept is over-explained; matches the "every token earns its place" anchor.

5 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: a ranked source priority, "Gather 5 to 20 representative samples", a nine-item extraction checklist, an output contract pinned to a concrete schema file, and an enumerated ban list ("'not X, just Y'", "'Excited to share'", "forced lowercase") with the instruction "Delete and rewrite any of these". Per the scoring notes, absence of code is not penalized when guidance is this specific.

5 / 5

Workflow Clarity

The pipeline is clearly sequenced: When to Activate → Source Priority → Collection Workflow → What to Extract → Output Contract → Downstream Use, with conditional checkpoints like "If the source set conflicts, call out the split instead of averaging it into mush". Not a 5 because there is no explicit validate-the-draft step (e.g., check output copy against the profile and Hard Bans before delivering), and the validation-ish rules live in the schema reference rather than the workflow itself. No destructive/batch cap applies.

4 / 5

Progressive Disclosure

Well-organized sections in a ~99-line body with exactly one reference, [references/voice-profile-schema.md](references/voice-profile-schema.md), clearly signaled via markdown link, one level deep, and verified present on disk with content matching what the body promises (a reusable VOICE PROFILE template). Content is appropriately split — the schema detail lives in the reference, not inline.

5 / 5

Total

19

/

20

Passed

Description

83%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 strong description with explicit what-and-when structure, third-person voice, and distinctive triggers. Its only weakness is breadth of synonyms ("tone", "brand voice", "write like") and slightly abstract phrasing of the reuse action.

DimensionReasoningScore

Specificity

Names several concrete actions with a broad input taxonomy: "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" — two distinct operations (build, reuse) with enumerated sources and target channels. Not a 5 because the actions stay at the level of profile construction/reuse without naming concrete sub-actions like extraction or validation.

4 / 5

Completeness

Explicitly answers both: what ("Build a source-derived writing style profile... then reuse that profile") and when ("Use when the user wants voice consistency without generic AI writing tropes") — a concrete, natural trigger clause, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Good natural trigger coverage: "voice consistency", "generic AI writing tropes", "posts, essays, launch notes, docs, or site copy", "content, outreach, and social workflows". Missing a few common synonyms a user might naturally say ("tone of voice", "brand voice", "write like me/this author"), so it sits between anchor 4 and 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (source-derived voice profiling) with distinctive trigger language like "voice consistency without generic AI writing tropes". Minor overlap risk with general content-writing/copywriting skills since "content, outreach, and social workflows" is broad, which keeps it below a 5.

4 / 5

Total

17

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.