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.

65

Quality

79%

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

Fix and improve this skill with Tessl

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

Quality

Content

75%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 concise, well-structured instruction skill with concrete workflows, extraction guidance, and a properly split-out schema reference. Adding an explicit validation/confirmation checkpoint in the workflow would lift workflow_clarity toward 5.

Suggestions

Add an explicit validation step to the Collection Workflow (e.g., confirm the profile matches source samples before reuse) to strengthen workflow_clarity.

Trim declarative framing sentences like 'The point is not literary criticism. The point is operational reuse.' to nudge conciseness to 5.

Surface a one-line 'verify the referenced schema exists before drafting' note near the Output Contract to make progressive disclosure fully self-checking.

DimensionReasoningScore

Conciseness

Lean, bullet-driven body that assumes Claude's competence and avoids explaining concepts Claude already knows; minor declarative framings like 'The point is not literary criticism. The point is operational reuse.' could be trimmed, so not a 5.

4 / 5

Actionability

Provides concrete, specific guidance — ordered Source Priority, a 5-step Collection Workflow, an extraction checklist, a Hard Bans list, and an Output Contract pointing to a real schema file; instruction-only skill with no executable code, so 5 is not reached.

4 / 5

Workflow Clarity

The Collection Workflow is a clear numbered sequence with ordered source precedence and persistence/downstream rules; validation checkpoints are only implicit and this is not a destructive/batch operation, so it stays at 4 rather than 5.

4 / 5

Progressive Disclosure

Well-organized sections with a clearly signaled, one-level-deep reference to the real file references/voice-profile-schema.md; bulk schema detail is correctly split out, with only minor organization gaps keeping it from 5.

4 / 5

Total

16

/

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, third-person description that clearly states both capability and trigger conditions with concrete source types and reuse surfaces. Minor additional natural synonyms would push trigger and distinctiveness scores higher.

DimensionReasoningScore

Specificity

Names the domain (writing style profile) and multiple concrete actions ('Build a source-derived writing style profile... then reuse that profile across content, outreach, and social workflows') with a strong source list; stops short of the fully comprehensive 5-anchor enumeration of distinct actions.

4 / 5

Completeness

Explicitly answers both what ('Build a source-derived writing style profile... reuse that profile across...') and when ('Use when the user wants voice consistency without generic AI writing tropes') with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Good coverage of natural user-facing terms ('voice consistency', 'content, outreach, and social workflows', 'posts, essays, launch notes, docs, or site copy'); a few common synonyms or channel extensions are missing, so not a 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche ('writing style profile', 'voice consistency') with distinct triggers and low conflict risk; minor overlap with general content skills keeps it just below 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.

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