CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

humanizer

Rewrite AI-sounding text so it reads like the writer without changing what it says. Use when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line closers, staged openers, forced triads, dashes everywhere, inflated claims, sales language, stock AI words, bold labels, or filler.

Quality

89%

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

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

An exceptionally actionable, well-sequenced editing skill: concrete before/after pairs for every pattern, an explicit validation loop, and clear mode handling. Its only real cost is size — the single-file catalog is heavy on the context window and a few rationale passages could be cut or split out.

DimensionReasoningScore

Conciseness

The body is dense and example-driven and assumes Claude's competence throughout (it never explains what a dash, triad, or em dash is). At roughly 500 lines, however, rationale passages such as 'Why AI text sounds the way it does' and the repeated multi-example Before/After blocks in stronger patterns are minor instances that could be trimmed, which is the anchor-4 fit rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Every one of the 26 patterns ships with concrete Before/After example pairs, explicit watch lists, and unambiguous rules (e.g. the §8 dash rule with named exceptions for code blocks, paths, and URLs). This is fully executable, copy-paste-quality guidance whose examples cover the common cases, matching anchor 5 for an instruction-only skill.

5 / 5

Workflow Clarity

'How to work' gives a clear four-step sequence (mark tells, draft, check, write final) with an explicit validation checkpoint in step 3: verify no fact, name, number, or claim was dropped, read the draft aloud, and re-search for the tells that most often survive a rewrite. Error handling is stated ('Treat a lost or changed claim as an error'), and mode-specific behavior (pasted, document, embedded) is defined — a clear sequence with validation and a feedback loop, matching anchor 5.

5 / 5

Progressive Disclosure

The file is well structured with a numbered, sectioned pattern catalog (A–F) that is easy to navigate, and it correctly avoids nested references by having none at all. It does not reach anchor 5 because the ~500-line catalog exceeds the simple-skill case and pattern groups (e.g. the word/phrase watch lists) could plausibly live in one-level-deep reference files, leaving minor organization gaps at anchor 4.

4 / 5

Total

18

/

20

Passed

Description

87%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 clearly states what the skill does and when to use it, backed by an unusually concrete list of trigger patterns. The only weakness is modest synonym coverage of natural user phrasings like 'make this sound human'.

DimensionReasoningScore

Specificity

The description names the core action ("Rewrite AI-sounding text so it reads like the writer without changing what it says") and enumerates ten concrete pattern categories ("not-X-but-Y contrasts, one-line closers, staged openers, forced triads, dashes everywhere..."). It lists several specific capabilities with only minor gaps, matching anchor 4 rather than 5 because the underlying action is a single rewrite operation rather than a comprehensive multi-action catalog.

4 / 5

Completeness

It explicitly answers both questions: what ("Rewrite AI-sounding text so it reads like the writer without changing what it says") and when ("Use when editing or reviewing prose for AI tells: ...") followed by concrete trigger phrases. This mirrors the anchor-5 example structure exactly; anchor 4 would require the 'when' clause to be less explicit than it is.

5 / 5

Trigger Term Quality

Phrases like "AI tells", "AI-sounding", "one-line closers", "forced triads", and "stock AI words" are terms users would naturally say when they need this skill. Coverage is good but misses common variations such as "make this sound human", "sound like me", or "humanize", so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (removing AI writing patterns from prose) with highly specific triggers like "not-X-but-Y contrasts" and "bold labels" that would not fire for any other skill. Overlap risk with general editing or formatting skills is minimal, matching anchor 5.

5 / 5

Total

18

/

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

skill_md_line_count

SKILL.md is long (501 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

n8n-io/n8n

Path

packages/frontend/editor-ui/src/experiments/recommendedSkills/content/humanizer/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.