CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

humanize

Strip AI-writing tells AND make prose clearer, stronger, and more concise. Use when editing or reviewing text to sound natural and human, or when writing or editing any prose humans will read: documentation, commit messages, pull request descriptions, error messages, UI copy, help text, comments, reports, or explanations. Detects and fixes AI patterns (inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, filler phrases) and applies Strunk's Elements of Style rules for clarity and concision (active voice, positive form, definite and concrete language, omitting needless words, parallel construction).

Quality

89%

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

85%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 an unusually actionable editorial procedure: every pattern has a before/after example, the workflow has explicit validation checkpoints and a feedback loop, and it avoids teaching concepts Claude already knows. Its weaknesses are a broken external reference (elements-of-style.md is absent from the bundle) and repetition of the no-fabrication rule that could be trimmed.

Suggestions

Ship elements-of-style.md with the skill or fix its path (e.g., references/elements-of-style.md): the body points to it in the Clarity and Concision section, but no such file exists in the bundle, so the one progressive-disclosure reference is a dead end.

State the never-invent-facts rule once in 'Your Task' and cut its restatements in sections 2, 5, 6, and Process step 3; the Process step 3 audit question alone re-enforces the constraint.

Consider moving the long-tail patterns (e.g., sections 12, 17, 19, 22) to a patterns reference file with the highest-frequency tells summarized in SKILL.md, so the body reads closer to an overview.

DimensionReasoningScore

Conciseness

The body is dense payload Claude does not already know (33 patterns with before/after pairs, false-positive guidance), but the never-invent-facts rule is repeated at least five times ('Never invent facts', 'Never invent one to make a sentence sound sourced', 'come from sources or the user, not from the rewrite', the Process step 3 audit question) and the em-dash sample exception is restated three times. This fits the 4 anchor ('minor instances of over-explanation that could be trimmed') rather than 5's 'every token earns its place'.

4 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: all 33 patterns carry verbatim Before/After pairs, section 14 gives an executable final check ('scan it for `—` and `–`. Any hit means the draft isn't done'), and the two audit questions are quoted word-for-word. Specific examples cover the common cases, matching the 5 anchor rather than 4, since no key execution detail is missing.

5 / 5

Workflow Clarity

'Process and Output' sequences draft, audit, final with explicit validation checkpoints (the two named audit questions and the em/en-dash scan) and a revise-to-address feedback loop, and each invocation mode states exactly what to deliver. This matches the 5 anchor ('clear sequence with explicit validation steps; feedback loops'); 4 would require a missing checkpoint, and none are absent.

5 / 5

Progressive Disclosure

Internal structure is well sectioned and the Strunk reference is clearly signaled with size guidance ('~30,000 tokens. Read it only when you are actively writing or editing prose'), but the referenced `elements-of-style.md` does not exist anywhere in the bundle (no references/ directory and no such file in this directory), so the single external reference is a dead end, and the full 33-pattern catalog is inlined in a roughly 450-line body. This fits the 3 anchor ('some structure but could be better organized; content that should be separate is inline') better than 4, whose references must be at least 'mostly clear' with only minor gaps.

3 / 5

Total

17

/

20

Passed

Description

88%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 that explicitly states both what the skill does and when to use it, with concrete enumerated capabilities and pattern lists. Its only weaknesses are a slightly broad trigger surface that could compete with general editing skills, and a few missing natural synonyms such as 'rewrite' or 'tone'.

DimensionReasoningScore

Specificity

Concrete actions are enumerated throughout: 'Strip AI-writing tells', 'make prose clearer, stronger, and more concise', 'Detects and fixes AI patterns (inflated symbolism, promotional language, superficial -ing analyses...)', and 'applies Strunk's Elements of Style rules for clarity and concision (active voice, positive form, definite and concrete language, omitting needless words, parallel construction)'. Multiple specific actions with comprehensive coverage matches the 5 anchor; 4 would require minor gaps, but both the pattern list and the style rules are itemized. The description uses third-person/imperative voice, so no person penalty applies.

5 / 5

Completeness

Both questions are answered explicitly: the 'what' ('Strip AI-writing tells AND make prose clearer, stronger, and more concise... Detects and fixes AI patterns... applies Strunk's... rules') and the 'when' via an explicit 'Use when editing or reviewing text... or when writing or editing any prose humans will read' clause with concrete trigger contexts. This matches the 5 anchor ('clearly and explicitly answers both what AND when with concrete trigger phrases') exactly.

5 / 5

Trigger Term Quality

Natural keywords are strong: 'editing', 'reviewing text', 'sound natural and human', plus a long enumeration of prose types ('documentation, commit messages, pull request descriptions, error messages, UI copy, help text, comments, reports, or explanations'). A few natural user phrasings such as 'rewrite' or 'tone' are absent, so this sits between the 4 anchor ('good keyword coverage; a few natural terms missing') and the 5 anchor's fully comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The AI-tell-removal niche ('AI-writing tells', 'AI patterns', 'sound natural and human', 'Strunk's Elements of Style') is clearly distinguishable from most skills, but the trigger surface 'any prose humans will read' with a nine-item enumeration is broad enough to overlap with general writing, editing, and documentation skills. This fits the 4 anchor ('mostly distinct; minor overlap risk with closely related skills') rather than 5's minimal conflict risk.

4 / 5

Total

18

/

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

joshmanders/dotfiles

Path

claude/skills/humanize/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.