CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

humanizer

Write in a natural, human tone — no AI-speak, no filler, no corporate fluff.

Quality

83%

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

100%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 exemplary lean instruction skill: specific, example-driven rules organized into clear sections, with explicit boundary guidance on what the skill does not do. No bundle files are referenced or needed, and nothing is over-explained.

DimensionReasoningScore

Conciseness

Every rule is one or two terse lines with concrete example phrases ("'I'd be happy to help'", "'Use' not 'utilise'") and no padding or explanation of concepts Claude already knows — every token earns its place.

5 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: banned phrase lists, word-swap pairs, a quantified example ("Sales dropped 15% in March"), and explicit edge-case handling in the 'Does NOT Do' section, covering the common cases.

5 / 5

Workflow Clarity

This is a simple single-purpose skill — apply the voice/structure/word-choice rules to all responses — and that single action is unambiguous, so it qualifies for the simple-skill exception; it involves no destructive or batch operations requiring validation checkpoints.

5 / 5

Progressive Disclosure

At under 50 lines with no need for external references (none exist in the bundle), the well-organized sections (Voice Rules, Structure Rules, Word Choice, Does NOT Do) satisfy the simple-skill criterion for a top score.

5 / 5

Total

20

/

20

Passed

Description

61%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 concise and names a distinct, natural-language niche with several recognizable trigger terms, but it omits any explicit 'when to use this' guidance and only gestures at the concrete behaviors the skill actually teaches. Adding a use-when clause and a broader set of everyday synonyms would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to make writing sound more human, casual, or less corporate, or complains about AI-speak or filler."

Name one or two concrete behaviors from the body (e.g. frontloading the answer, swapping 'utilise' for 'use') so the description previews what the skill actually changes.

Broaden trigger synonyms to cover common user phrasings like "casual", "less formal", "friendlier", and "rewrite this".

DimensionReasoningScore

Specificity

Names the writing-tone domain and one concrete action ("Write in a natural, human tone") plus three specific exclusions ("no AI-speak, no filler, no corporate fluff"), but doesn't enumerate the concrete behaviors covered in the body (contractions, frontloading, word swaps), so it falls short of anchor 4's 'several specific actions'.

3 / 5

Completeness

The 'what' is clear (write in a natural, human tone), but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural terms users would actually say — "natural", "human tone", "AI-speak", "filler", "corporate fluff" — giving good keyword coverage; not 5 because common variations like "casual", "less formal", or "friendlier" are absent.

4 / 5

Distinctiveness Conflict Risk

The tone/style niche with distinct anti-patterns ("no AI-speak, no filler, no corporate fluff") is mostly distinguishable from other skills; only minor overlap risk with general writing or editing skills keeps it from a 5.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

siddsachar/row-bot

Path

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