SKILLEMALL.ai

AB humanizer

Humanize text: strip AI-isms and add real voice.

NousResearch/hermes-agent Hermes author: NousResearch MIT 2 files body ≈ 8 492 tokens Open the sourcegithub.com analyzed 2 d ago

Humanize text: strip AI-isms and add real voice.

As a process B 67/100 · Nearly there — weak spots: inputs and preconditions, execution cost, running it twice

ProcedureWriting and documentsSales and CRMAI and agentstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
B
67/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Running it twice w 4
30
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 body-long SKILL.md body ≈ 8492 tokens (recommended < 5000); move details to references/
  • note edit-residue the text marks something as outdated (lines 96, 163, 588): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 67/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 26 mutating operations with no state check
  • 40Execution cost. Instruction body is 8492 tokens: crowds the task out of the window
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Consistency. The Hermes dialect needs category and tags
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 75 steps
  • 100Result and completion. Output format and completion criterion are stated
  • 100Failures and branches. 1 branches, has a failure section
  • low 15 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)
  • +3Description length 48: 120–800 characters recommended
  • +2Single-language instructions
  • +4Structure: 55 headings
  • +3Step-by-step instructions: 75 items
  • +3Output format is stated explicitly
  • +4Has examples (0 code blocks)
  • +1License stated

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