AC humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Combines Wikipedia's "Signs of AI writing" guide with 2025-2026 forensic detection research. Covers: perplexity/burstiness metrics, Unicode artifacts, 24+ AI vocabulary patterns, structural tells, and surgical humanization techniques. Includes detection benchmarks for GPT-4o, Claude, Gemini models.
As a process C 64/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6611 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 64/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 24 mutating operations with no state check
- 40Consistency. Frontmatter name (humanizer) differs from the folder (deai-ify)
- 60Failures and branches. 2 branches
- 70Execution cost. Instruction body is 6611 tokens
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 129 steps
- 100Result and completion. Output format and completion criterion are stated
- low 16 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 431: enough signal without eating the budget
- +4Structure: 60 headings
- +3Step-by-step instructions: 129 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.