CtrlK
BlogDocsLog inGet started
Tessl Logo

content-humanizer

Makes AI-generated content sound genuinely human — not just cleaned up, but alive. Use when content feels robotic, uses too many AI clichés, lacks personality, or reads like it was written by committee. Triggers: 'this sounds like AI', 'make it more human', 'add personality', 'it feels generic', 'sounds robotic', 'fix AI writing', 'inject our voice'. NOT for initial content creation (use content-production). NOT for SEO optimization (use content-production Mode 3).

66

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

The canonical home for this skill is content-humanizer in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 a well-sequenced, highly actionable guide with skill-specific knowledge (tell vocabulary, replacement tables, thresholds, before/after examples) rather than padding. Its main defect is bundle integrity: all three referenced files (two references, one script) do not exist, breaking both the progressive-disclosure navigation and the validation feedback loop.

Suggestions

Ship the referenced bundle files — create references/ai-tells-checklist.md, references/voice-techniques.md, and scripts/humanizer_scorer.py, or remove/inline the references; as delivered, every link and the scoring command is broken.

Add a fallback validation step for when the scorer script is unavailable (e.g., a manual tell-count heuristic per 500 words) so the 're-run and confirm the score moves' checkpoint always has an executable form.

Trim the rhetorical framing ('This is not a cleaning service...') and merge the Communication section into Output Artifacts to cut ~15-20 lines of token cost without losing guidance.

DimensionReasoningScore

Conciseness

Mostly efficient: the body teaches skill-specific knowledge Claude cannot be assumed to have (the AI-tell vocabulary, phrase-replacement table, rhythm patterns, scoring thresholds) rather than explaining known concepts. Minor trimming opportunities exist — the rhetorical framing ('This is not a cleaning service. You're not just removing "delve" and calling it a day.'), the Communication section overlapping the Output Artifacts table, and duplicated What+Why guidance in Mode 3 keep it below lean.

4 / 5

Actionability

Concrete, executable guidance throughout: an exact script invocation ('python3 scripts/humanizer_scorer.py draft.md --json') with decision thresholds (80+ / 60-79 / below 60), an AI-phrase → human-alternative replacement table, explicit before/after examples with named changes, and specific user questions to ask. Falls short of 5 because the scorer script referenced by the command is absent from the bundle, so the primary executable step cannot actually be run as shipped.

4 / 5

Workflow Clarity

Clear three-mode sequence (Detect → Humanize → Voice Injection) with guidance on running sequentially vs. jumping, a preflight context check, and a genuine feedback loop ('Re-run after humanizing; the score must move') plus a proactive-triggers section covering failure paths (missing voice context, over-editing risk). Not 5 because the validation checkpoint depends on the missing scorer script, and there is no fallback validation stated for when it is unavailable.

4 / 5

Progressive Disclosure

The structure is well designed on paper — SKILL.md stays an overview and points to references/ai-tells-checklist.md and references/voice-techniques.md with context for each — but the bundle contains no references/ or scripts/ directories, so both linked files and the scorer script are dangling references. Navigation fails in practice, and the inlined core tell list is content the missing checklist was supposed to carry. Between anchors 3 and 4; broken referenced paths pull it to 3.

3 / 5

Total

15

/

20

Passed

Description

90%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 strong description: explicit what/when structure, natural and varied trigger phrases, and explicit negative boundaries that route to sibling skills. The only gap is that it describes the outcome as a single transformation rather than enumerating the skill's several concrete operations.

DimensionReasoningScore

Specificity

The description names the domain ('AI-generated content') and one core transformation action ('Makes AI-generated content sound genuinely human') — matching the anchor for 1-2 concrete actions but not several. It does not list the multiple operations the skill actually performs (pattern detection, rhythm fixing, voice injection); those live only in the body. Not score 4 because it stops at a single action with a qualifier ('not just cleaned up, but alive'), which is a characterization rather than additional concrete actions.

3 / 5

Completeness

Explicitly answers both what ('Makes AI-generated content sound genuinely human') and when ('Use when content feels robotic, uses too many AI clichés, lacks personality...'), backed by concrete quoted trigger phrases. It even adds negative scope ('NOT for initial content creation', 'NOT for SEO optimization') with redirect targets, exceeding the anchor-5 example's clarity.

5 / 5

Trigger Term Quality

Comprehensive natural-language trigger coverage: 'this sounds like AI', 'make it more human', 'add personality', 'it feels generic', 'sounds robotic', 'fix AI writing', 'inject our voice', plus condition phrases ('uses too many AI clichés', 'reads like it was written by committee'). These are exactly the phrases a user would naturally say; no relevant synonym category is missing (file extensions don't apply to this content-domain skill).

5 / 5

Distinctiveness Conflict Risk

Clear niche (post-generation humanization of AI-flavored content) with distinct triggers, and explicit disambiguation from adjacent skills (content-production, content-production Mode 3). Minimal risk of triggering for the wrong skill.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

14

/

16

Passed

Repository
alirezarezvani/claude-skills
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.