CtrlK
BlogDocsLog inGet started
Tessl Logo

humanizer

Humanize text: strip AI-isms and add real voice.

56

Quality

67%

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

Quality

Content

77%

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

The content is highly actionable with a clear, well-sequenced workflow and a strong feedback loop, but it is overlong for a single SKILL.md with redundant process sections and no external reference files to offload the pattern catalog.

Suggestions

Consolidate the overlapping 'Your task', 'Process', and 'Output Format' sections into a single workflow to remove repetition.

Move the 34-pattern catalog into a bundled reference file (e.g. references/PATTERNS.md) and keep SKILL.md as a concise overview with a one-level-deep pointer.

Trim the attribution and meta-commentary at the end to the essential provenance line to reduce token weight.

DimensionReasoningScore

Conciseness

The body is mostly efficient with genuinely non-obvious content (34 patterns plus worked examples), but it is ~630 lines with noticeable redundancy across the 'Your task', 'Process', and 'Output Format' sections, so it could be tightened rather than earning a fully lean 3.

2 / 3

Actionability

Each of the 34 patterns gives concrete 'Words/Signs to watch' plus a Before/After pair, and the full worked example (draft -> audit -> final) is copy-paste-ready executable guidance.

3 / 3

Workflow Clarity

The process is explicitly sequenced (identify -> rewrite -> preserve -> maintain voice -> add soul -> final pass) with an explicit self-audit feedback loop ('What makes the below so obviously AI generated?' -> revise -> final), matching the clear-sequence-with-feedback-loops anchor.

3 / 3

Progressive Disclosure

Sections are clearly organized, but no bundle files exist and the 630-line body is a monolith that could be split (e.g. the 34 patterns into a reference file), matching 'some structure but content that should be separate is inline'.

2 / 3

Total

10

/

12

Passed

Description

57%

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 distinctive but incomplete: it states the what clearly yet omits explicit when-to-use guidance and richer trigger-term coverage that the skill body actually contains.

Suggestions

Add a 'Use when...' clause naming the trigger phrases users actually say (e.g. 'Use when the user asks to humanize, de-AI, de-slop, or un-ChatGPT text').

Broaden trigger terms in the description to include common variations like 'de-AI', 'de-slop', and 'un-ChatGPT' rather than only 'Humanize'.

Consider listing a couple more concrete actions (e.g. 'rewrite drafts, match a voice sample, review prose before publishing') to raise specificity from a partial list to a comprehensive one.

DimensionReasoningScore

Specificity

The description names the domain ('Humanize text') and two concrete actions ('strip AI-isms and add real voice'), but stops short of listing multiple specific operations, matching the 'names domain and some actions but not comprehensive' anchor.

2 / 3

Completeness

It states what the skill does but lacks any 'Use when...' clause or explicit trigger guidance; per the rubric a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

'Humanize' is a natural term users say, but the description omits common variations the body itself lists ('de-AI', 'de-slop', 'un-ChatGPT'), so it has some relevant keywords while missing common variations.

2 / 3

Distinctiveness Conflict Risk

'Humanize text / strip AI-isms' is a clear, narrow niche with distinct triggers that is unlikely to overlap with or wrongly trigger other skills.

3 / 3

Total

9

/

12

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

12

/

16

Passed

Repository
NousResearch/hermes-agent
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.