CtrlK
BlogDocsLog inGet started
Tessl Logo

humanizer

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

65

Quality

78%

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 ./bundled_skills/humanizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and cleanly organized for a simple instruction skill, with the only weakness being a few justifying sentences that pad the otherwise tight rules.

Suggestions

Trim explanatory tail clauses like "Monotonous rhythm sounds robotic." and "They add nothing." so each rule is just the directive plus its concrete example.

DimensionReasoningScore

Conciseness

The body is mostly lean with concrete examples, but several trailing justifications ("Monotonous rhythm sounds robotic", "Formal writing avoids them. Human writing doesn't.", "They add nothing.") explain what Claude already knows and could be trimmed, so it lands at 'mostly efficient but could be tightened' rather than 'every token earns its place'.

2 / 3

Actionability

It gives copy-paste-ready specifics: exact phrases to avoid ("I'd be happy to help", "Certainly!"), concrete word swaps ("Use" not "utilise"), and a contrastive example ("Sales dropped 15% in March" vs. vague alternative), fully matching the 'specific examples; copy-paste ready' anchor for an instruction-only skill.

3 / 3

Workflow Clarity

This is a simple single-purpose style skill with no multi-step or destructive process; the rules are clearly categorized into Voice, Structure, Word Choice, and limits, which per the simple-skills note warrants a 3.

3 / 3

Progressive Disclosure

The body is under 50 lines, has no external references, and is organized into well-labeled sections, which per the guidelines lets progressive disclosure score 3 on well-organized sections alone.

3 / 3

Total

11

/

12

Passed

Description

72%

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 uses natural trigger terms with a clear niche, but it omits an explicit 'Use when...' clause and lists negations rather than multiple concrete positive actions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants writing that sounds less robotic, less corporate, or free of AI-speak.'

Complement the negations with one or two concrete positive actions (e.g. 'Rewrites responses to sound conversational and direct') to lift specificity.

DimensionReasoningScore

Specificity

It names the domain ("natural, human tone") and concrete things to avoid ("no AI-speak, no filler, no corporate fluff") but does not list multiple distinct positive actions, so it stops at the 'names domain and some actions' anchor rather than the 'lists multiple specific concrete actions' level.

2 / 3

Completeness

It clearly states what the skill does ("Write in a natural, human tone...") but has no explicit "Use when..." clause or equivalent trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like "human tone", "AI-speak", "filler", and "corporate fluff" are exactly what a user would say when they need this skill, matching the 'good coverage of natural terms' anchor; it is not jargon-heavy or overly generic.

3 / 3

Distinctiveness Conflict Risk

The anti-AI-speak / humanizing niche with distinctive trigger terms ("AI-speak", "corporate fluff") is unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor rather than the 'could overlap' level.

3 / 3

Total

10

/

12

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.

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