CtrlK
BlogDocsLog inGet started
Tessl Logo

humanizer

Remove AI writing patterns to make documentation sound natural, specific, and human. Covers content patterns, language patterns, style patterns, and communication patterns.

62

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

Quality

Content

86%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 SKILL.md body is a tightly written, well-structured overview that delegates pattern detail to four clearly labeled reference files and includes a concrete self-check loop. Its only real gap is that the core 'rewrite' instruction is somewhat abstract, leaving actionability just short of fully executable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no padding, no explaining what AI writing is, and every line earns its place; the only mild redundancy is the 'Ensure the result sounds natural...' restatement, which still adds criteria.

5 / 5

Actionability

Concrete, executable guidance for an instruction-only skill — a numbered process, a specific self-check question ('what makes this obviously AI generated?'), and a reference table mapping categories to files; 'rewrite the problematic sections' remains slightly abstract, keeping it just below 5.

4 / 5

Workflow Clarity

A clear four-step sequence with a final anti-AI pass that acts as a feedback loop (ask, name tells, fix), and a closing quality checklist; this is an editing skill so the destructive/batch validation cap does not apply, but the checkpoints are implicit rather than fully explicit.

4 / 5

Progressive Disclosure

The body is a concise overview pointing to four real, one-level-deep reference files via a well-signaled table that labels exactly what each covers; navigation is easy and content is appropriately split, matching the bundle structure on disk.

5 / 5

Total

18

/

20

Passed

Description

58%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 gives a clear, concrete statement of what the skill does and its scope, but lacks an explicit 'when to use it' trigger clause, which limits its completeness and trigger-term coverage. Adding a 'Use when...' sentence would substantially improve activation behavior.

Suggestions

Append an explicit trigger clause, e.g. 'Use when editing AI-generated documentation, or when the user asks to humanize, de-AI, or naturalize text.'

Add natural synonyms users actually say ('humanize', 'make it sound less robotic', 'AI-generated text') to broaden trigger-term coverage.

Consider a second concrete action verb (e.g. 'Identify and remove...') to strengthen specificity beyond the single 'Remove' verb.

DimensionReasoningScore

Specificity

Names the concrete action 'Remove AI writing patterns' and enumerates the four covered pattern categories ('content patterns, language patterns, style patterns, and communication patterns'), giving comprehensive coverage of the domain with only a single action verb.

4 / 5

Completeness

The 'what' is clear ('Remove AI writing patterns to make documentation sound natural, specific, and human') but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Relevant keywords like 'AI writing patterns', 'documentation', 'natural', and 'human' appear, but common variations a user might say ('humanize', 'AI-generated text', 'make this sound less robotic') are missing.

3 / 5

Distinctiveness Conflict Risk

'Remove AI writing patterns' is a fairly distinct niche with low conflict risk, though it could marginally overlap with general editing or writing-improvement skills.

4 / 5

Total

14

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
kubb-labs/kubb
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.