SKILLEMALL.ai

BB text-humanizer-Instruction-based

Detect and rewrite AI-generated writing patterns, em dashes, rule-of-three lists, sycophantic openers, hollow buzzwords like "delve" and "landscape", and replace them with direct, human-sounding prose.

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

Detect and rewrite AI-generated writing patterns, em dashes, rule-of-three lists, sycophantic openers, hollow buzzwords like "delve" and "landscape", and…

As a process B 77/100 · Nearly there — weak spots: inputs and preconditions, progress reporting

AnalyzerWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
71
Run on models
none yet
Process rating
B
77/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Result and completion w 14
60
the three weakest of ten parameters · all ten

How to improve

  1. 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 body-long SKILL.md body ≈ 6489 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "homepage"
  • note edit-residue the text marks something as outdated (lines 115): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 77/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 6489 tokens
  • 85Steps. 30 steps, 2 vague phrases
  • 100Tools and files. No external tools needed
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 5 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state

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 201: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 30 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)

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