CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-voice

Shape prose so it sounds like Braden, with conversational precision, rhythm, humor, and earned poetic turns. Use for substantial drafting or revision, an ear pass, and explicit voice or tone work in prose, UI copy, documentation, or messages. Do not use to reopen wording selected for exact use.

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

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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-crafted instruction-only skill body: lean, judgment-dense prose with concrete tests and worked examples, a clear rehear-and-revise feedback loop, and clean one-level-deep disclosure of the spoken-destination material. Remaining gaps are minor — a few aphoristic restatements and some abstract directives that resist direct execution.

DimensionReasoningScore

Conciseness

The body assumes Claude's intelligence throughout — no filler explaining what prose or voice is, and nearly every sentence carries an editorial judgment. A few abstract summarizing lines ('Neither roughness nor polish is a virtue by itself', 'Recognition matters more than grammatical perfection') restate nearby points and could be trimmed. Matches the 4 anchor: efficient with minor over-explanation; not 5 because of those few redundant aphoristic closers.

4 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: the deletion test ('would removing it preserve meaning, movement, and human posture?'), 'Read connected passages at speaking speed', a worked example ('"And then there's just a lot of Asian food" can earn its own paragraph'), a specific transformation warning ('changing "I would argue" into "I wonder whether" can weaken the thought'), and explicit punctuation rules ('Avoid en dashes; default away from em dashes'). Mostly executable with minor gaps — some directives remain abstract ('Hear what the writing is doing, then judge it by what this piece needs'), so 4 rather than 5; well above pseudocode-level guidance, so not 3.

4 / 5

Workflow Clarity

A coherent editorial sequence is present: find the expression, hear the whole passage under four named tests, 'rehear the passage under that correction and revise at the scope it illuminates', reread in context, then after a whole-piece pass 'check that the opening, strongest concrete detail, and ending still serve the same thought'. The rehear-and-revise step is an explicit feedback loop. Scored 4 not 5 because checkpoints are embedded in prose rather than laid out as explicit, ordered steps with validation gating; not 3 because the sequence and recovery loop are both clearly stated. No destructive/batch validation cap applies to prose editing.

4 / 5

Progressive Disclosure

The body is well-sectioned with clear headers, and the single bundle file is a well-signaled, one-level-deep reference that exists and is on point: 'For work intended to be heard, read [spoken destinations](references/spoken-destinations.md) for the extra judgments a listener's experience requires.' Core craft lives in SKILL.md while listener-specific material is appropriately split out with no nested references — the 5 anchor. Not 4 because navigation is unambiguous and the split is clean.

5 / 5

Total

17

/

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: explicit what and when, distinctive personal-voice niche, a useful negative boundary, and good natural trigger coverage. Its only weaknesses are a slightly abstract umbrella verb ('Shape prose') and a few missing common synonyms for triggering revision work.

DimensionReasoningScore

Specificity

The description enumerates several specific capabilities and modes — 'conversational precision, rhythm, humor, and earned poetic turns', 'substantial drafting or revision, an ear pass, and explicit voice or tone work in prose, UI copy, documentation, or messages' — though the umbrella action 'shape prose' leaves minor coverage gaps. Not 5 because the actions are attributes of one shaping verb rather than a comprehensive list of distinct operations; not 3 because it goes well beyond naming a domain with 1-2 actions.

4 / 5

Completeness

It explicitly answers both questions: the 'what' ('Shape prose so it sounds like Braden, with conversational precision, rhythm, humor, and earned poetic turns') and the 'when' ('Use for substantial drafting or revision, an ear pass, and explicit voice or tone work...'), plus a negative trigger boundary ('Do not use to reopen wording selected for exact use'). Clearly matches the 5 anchor with concrete trigger phrases; 4 would require the 'when' to be less explicit than it is.

5 / 5

Trigger Term Quality

Natural phrases a user would say are present with synonyms — 'drafting or revision', 'an ear pass', 'voice or tone work', 'UI copy', 'documentation', 'messages'. Not 5 because common variants users would naturally say, such as 'rewrite', 'edit', or 'style', are missing; not 3 because coverage is good rather than partial.

4 / 5

Distinctiveness Conflict Risk

Distinctive triggers like 'sounds like Braden', 'an ear pass', and 'voice or tone work' carve a clear niche, but 'substantial drafting or revision' broadly overlaps general writing and editing skills. Mostly distinct with minor overlap risk — the 4 anchor; not 5 because of that drafting/revision breadth, not 3 because the named voice and ear-pass triggers are unmistakable.

4 / 5

Total

17

/

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
EpicenterHQ/epicenter
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.