CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

humanizer

Remove signs of AI-generated writing from text. Use after drafting to make copy sound more natural and human-written. Based on Wikipedia's "Signs of AI writing" guide.

Quality

81%

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

85%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-structured instruction skill: every pattern is defined by concrete trigger phrases and demonstrated with a before/after rewrite, and the workflow embeds a genuine self-audit feedback loop. The main improvements are removing the duplicated task/process sections and splitting the pattern catalog into a reference file so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body is dense and example-driven: each of the 24 patterns gets a watch-for phrase list and a tight Before/After pair, with almost no explanation of concepts Claude already knows. It is not a 5 because the "Your Task" and "Process" sections largely duplicate each other (identify, rewrite, audit, present appears twice), and the Invocation code block restates slash-command mechanics, so some tokens could be trimmed.

4 / 5

Actionability

Guidance is fully concrete and copy-paste ready for an instruction-only skill: specific watch-for phrase lists per pattern (e.g. "stands/serves as, is a testament/reminder"), Before/After rewrites for every pattern, a fixed Output Format template (Draft Rewrite / AI Audit / Final Version / Changes Made), and a complete worked example from input to final version. This matches the anchor for fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

The process is an explicit sequence with a built-in validation feedback loop: draft, then "Ask: 'What makes this still obviously AI generated?'", list remaining tells, revise based on the audit, and present the final version. This matches the anchor for clear sequencing with explicit validation and error-recovery loops; the operation is non-destructive, so no batch-operation cap applies.

5 / 5

Progressive Disclosure

Section structure is good (grouped categories, numbered patterns, clear headers), but the entire ~390-line skill is one flat file with no bundle files at all; the 24-pattern catalog (~250 lines of reference material) is inlined in SKILL.md where a split (patterns in references/, process and examples in the body) would match the anchor for content that should be separate sitting inline. It is above anchor 2 because what is present is well organized and easy to navigate, not buried.

3 / 5

Total

17

/

20

Passed

Description

70%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 concise, third-person description that explicitly states what the skill does and when to use it, with a credible source attribution. Its main gaps are limited action enumeration and missing the natural trigger phrasings ("humanize", "sounds robotic/AI") that would let it fire reliably.

Suggestions

Add user-mention triggers to the when clause, e.g. "Use after drafting, or when the user asks to humanize text, make writing sound natural, or remove AI/robotic tone."

Name the core transformations more concretely, e.g. "identifies and rewrites 24 common AI writing patterns (promotional language, significance inflation, em dash overuse) and injects natural voice".

Include the skill's own trigger word "humanize" in the description so the command name matches a term users actually say.

DimensionReasoningScore

Specificity

"Remove signs of AI-generated writing from text" and "make copy sound more natural and human-written" name the domain plus two concrete actions, matching the anchor for 1-2 concrete actions that is not comprehensive. It is not a 4 because no further specific actions or transformations are listed, and not a 2 because the actions are concrete rather than generic.

3 / 5

Completeness

Both parts are explicit: the "what" ("Remove signs of AI-generated writing from text") and a "when" clause ("Use after drafting"). It is not a 5 because the trigger guidance is tied only to the drafting workflow and lacks concrete user-mention triggers (e.g., "when the user asks to humanize text or says it sounds AI-generated"), and it is clearly above anchor 3 since the "when" is explicitly stated rather than implied.

4 / 5

Trigger Term Quality

Natural terms users would say are present: "AI-generated writing", "natural", "human-written", "copy", "drafting". It falls short of comprehensive coverage (anchor 5) because common phrasings like "humanize", "make it sound human/less robotic", or "ChatGPT-style" are missing, but it is well above the generic-keyword anchors.

4 / 5

Distinctiveness Conflict Risk

"Remove signs of AI-generated writing" carves out a clear niche with distinct triggers, giving minimal conflict risk with unrelated skills. It is not a 5 because the description does not mention its signature trigger word ("humanize", the skill's own name and slash command), leaving slight overlap risk with general editing/rewriting skills.

4 / 5

Total

15

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

coumbassaabdoulaye01-del/borther-Code-by-code

Path

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