CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cw-hemingway

Cuts ruthlessly. Flags every adjective, adverb, and unnecessary word. Demands you kill your darlings.

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 ./skills/cw-hemingway/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a strong, actionable instruction skill: concrete cut rules with examples, a per-word test, and a complete output template. It is well-structured and self-contained, with only minor conciseness and validation-checkpoint gaps.

DimensionReasoningScore

Conciseness

Mostly lean and skill-specific (concrete table, decision test, output template) with minor flourish that could be trimmed such as the 'Iceberg' section and the Purpose paragraph.

4 / 5

Actionability

Provides concrete before/after examples across eight cut categories, a three-question per-word decision test, and a complete copy-paste-ready output template that covers the common cases.

5 / 5

Workflow Clarity

Clear single-action flow with a feedback loop ('cut deeper or is this too lean?') and implicit validation via the Hemingway Test, but meaning-preservation is an implicit checkpoint rather than an explicit validation step.

4 / 5

Progressive Disclosure

Well-organized into clear sections and self-contained with no nested references; slightly over the 50-line simple-skill threshold with minor non-essential sections (Iceberg, Lessons placeholder).

4 / 5

Total

17

/

20

Passed

Description

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

The description is punchy and names a clear, specific niche, but it lacks any 'when to use' trigger guidance and mixes in second-person/figurative language that weakens specificity and trigger coverage.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when a draft feels bloated, overwritten, or drowning in adverbs and adjectives.'

Replace or augment 'Demands you kill your darlings' with a third-person concrete action and drop the second-person 'you' (e.g. 'Rewrites for maximum concision.') to satisfy the third-person voice requirement.

Broaden trigger-term coverage with natural synonyms users actually say: 'tighten prose', 'trim wordy text', 'make it more concise', 'cut fluff'.

DimensionReasoningScore

Specificity

Names the domain ('adjective, adverb, and unnecessary word') and two concrete verbs ('Cuts', 'Flags'), but the third action ('kill your darlings') is figurative; reduced by 1 for the second-person 'you' per the voice guideline.

2 / 5

Completeness

Clearly states what the skill does but has no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Contains relevant keywords ('adjective', 'adverb', 'unnecessary word', 'kill your darlings') but omits common natural variations users would say like 'tighten', 'trim', 'wordy', 'verbose', or 'concise'.

3 / 5

Distinctiveness Conflict Risk

Occupies a distinct niche (ruthless modifier-cutting / Hemingway style) with only minor overlap risk against general editing or grammar skills.

4 / 5

Total

12

/

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

EveryInc/compound-writing

Path

skills/cw-hemingway/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.