SKILLEMALL.ai
GitHub ↗ RU Sign in

BC Humanizer

Remove signs of AI-generated writing from text. Detects and fixes 24 common AI patterns including inflated symbolism, promotional language, superficial analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and sycophantic tone. Based on Wikipedia's "Signs of AI writing" guide maintained by WikiProject AI Cleanup.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 2 files body ≈ 5 561 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Remove signs of AI-generated writing from text.

As a process C 56/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

GeneratorSales and CRMtype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
54
Run on models
none yet
Process rating
C
56/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • 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 name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 5561 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "languages"
  • note frontmatter-key unknown frontmatter key "attribution"
  • note edit-residue the text marks something as outdated (lines 55, 127, 422): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 56/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 21 mutating operations with no state check
  • 40Consistency. Frontmatter name (Humanizer) differs from the folder (runesleo-humanizer)
  • 70Execution cost. Instruction body is 5561 tokens
  • 85Steps. 55 steps, 1 vague phrases
  • 100Tools and files. Tools declared in frontmatter
  • 100Result and completion. Output format and completion criterion are stated
  • low 11 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)
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 366: enough signal without eating the budget
  • +4Structure: 40 headings
  • +3Step-by-step instructions: 55 items
  • +3Output format is stated explicitly

Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.