CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

humanizer

Use on demand when the user requests Humanizer, asks to rewrite AI-sounding prose in the author's voice, or accepts that recommendation for a public or professional draft. Includes a Spanish/English communication profile. Recommend it in fitting prose tasks; ask before an unrequested broader rewrite.

Quality

80%

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

75%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-structured, policy-dense wrapper that respects the reader's competence, gives concrete decision rules with bilingual example phrasing, and includes an explicit claim-preservation validation loop. Weaknesses are mild: some duplication with the required reference file, workflow steps distributed across sections rather than sequenced in one place, and one referenced bundle path (upstream/instructions.md) that does not resolve within the provided skill directory.

DimensionReasoningScore

Conciseness

The body contains no explanations of concepts Claude already knows — every line is task-specific policy, decision rules, or file pointers — and copy-paste example phrases are given in both languages. It is not 5 because several rules duplicate guidance in the communication profile that step 1 already requires reading (e.g., claim preservation appears in both 'Preserve the author's claims, qualifications...' and the profile's 'Preserve facts, attribution, commitments...'), and a few dense negative-rule bullets could be merged or trimmed.

4 / 5

Actionability

For an instruction-only skill the guidance is mostly executable: exact file paths to read, an activation rule ('An explicit request... activates this skill... A recommendation alone does not'), concrete rerouting ('If the user asks for minimal cleanup, use `avoid-ai-writing`'), a private-claims checklist procedure, and ready-to-use example recommendation sentences in Spanish and English. It is not 5 because the core rewriting mechanics are delegated to 'Apply its pattern review and voice matching' — instructions stored in an upstream file the reader must load — and some rules ('Infer only what the text and conversation support') remain judgment-level rather than concrete steps.

4 / 5

Workflow Clarity

The sequence is clear and includes an explicit validation checkpoint with a fix-before-deliver loop: 'Before drafting, make a private checklist of the source's individual claims. After drafting, account for each... Restore any missing claim before delivery', plus 'Do not invent verification results'. It is not 5 because the workflow is assembled from three separate sections (Read and apply, Scope and output, Recommend/ask/proceed) rather than presented as one ordered process, leaving the reader to reconstruct the order of activation check, reference loading, checklist, drafting, verification, and delivery.

4 / 5

Progressive Disclosure

The body is a genuine overview wrapper with well-signaled, one-level-deep references — [communication profile](references/communication-profile.md) and [provenance](references/provenance.md) both exist in the bundle and each link explains what the file is for. It is not 5 because the referenced `upstream/instructions.md`, the file step 2 depends on, is not present in the bundle, so a referenced path does not resolve; provenance also points at out-of-bundle targets (`../LICENSE`, `skills-lock.json`) without in-skill navigation.

4 / 5

Total

16

/

20

Passed

Description

78%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 that explicitly answers both what the skill does and when to use it, with natural trigger phrasing and a clearly demarcated niche. Its main limitation is capability coverage — it names one core action plus a bundled profile rather than enumerating several concrete actions — and it does not distinguish itself from a closely related conservative-cleanup skill at the description level.

Suggestions

Add one or two more concrete capability phrases (e.g., 'returns one final version that preserves the author's claims and evidence') so the what-side moves beyond a single core action.

Name the adjacent cleanup workflow or add a distinguishing phrase (e.g., 'for light pattern cleanup prefer a conservative pass instead') to reduce overlap risk between this and sibling prose skills at the trigger level.

DimensionReasoningScore

Specificity

The description names the domain ("rewrite AI-sounding prose in the author's voice") plus one supporting feature ("Includes a Spanish/English communication profile"), which matches the anchor for 1-2 concrete actions without comprehensive coverage. It does not reach 4 because the remaining clauses ("Recommend it in fitting prose tasks; ask before an unrequested broader rewrite") are invocation policy rather than additional concrete capabilities.

3 / 5

Completeness

Both questions are explicitly answered: what it does ("rewrite AI-sounding prose in the author's voice... Includes a Spanish/English communication profile") and when to use it ("Use on demand when the user requests Humanizer, asks to rewrite AI-sounding prose in the author's voice, or accepts that recommendation..."). The explicit 'Use when' clause with concrete trigger phrases matches the 5 anchor; it is not 4 because the 'when' is specific and multi-trigger, not merely present.

5 / 5

Trigger Term Quality

Natural trigger phrases are present — "requests Humanizer", "rewrite AI-sounding prose", "in the author's voice", "public or professional draft" — phrased the way a user would actually ask. It falls short of 5 because common variations like "make this sound human", "sound like me", or "less robotic" are not covered.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (author-voice humanizing rewrite) with distinct triggers, but there is minor overlap risk with a closely related cleanup skill in the same space: a user asking to "avoid AI writing" or make text "sound less AI" could match this description even though the sibling skill handles conservative cleanup. It is above 3 because the author's-voice rewrite framing and the named skill make it far more specific than generic document or prose helpers.

4 / 5

Total

16

/

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

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

saski/arnesto

Path

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