SKILLEMALL.ai

AC reddi-humanizer

Fork of humanizer by biostartechnology — enhanced for technical blog writing. Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. Enhancements over original: personality/soul injection guidance, technical writing patterns, voice guide integration, stronger "soulless writing" detection.

modbender/skill-library-mcp Agent Skills author: modbender MIT 2 files body ≈ 4 447 tokens Open the sourcegithub.com analyzed 2 d ago

Fork of humanizer by biostartechnology — enhanced for technical blog writing.

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

GeneratorSales and CRMWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
C
55/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

    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

    • note frontmatter-key unknown frontmatter key "attribution"

    Process rating: all ten parameters 55/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. 13 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 70Execution cost. Instruction body is 4447 tokens
    • 85Steps. 37 steps, 1 vague phrases
    • 100Tools and files. Tools declared in frontmatter
    • 100Consistency. Name and required fields are in place
    • 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

    • +4Description does not say when NOT to use the skill (false activations)
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 2 example trigger phrases
    • +3Description length 669: enough signal without eating the budget
    • +4Structure: 40 headings
    • +3Step-by-step instructions: 37 items
    • +3Output format is stated explicitly

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