SKILLEMALL.ai

AC deslop

Remove AI writing patterns from prose. Use this skill when writing, drafting, editing, reviewing, or revising any text to eliminate predictable AI tells, slop, and formulaic patterns. Trigger this skill whenever the user asks to "deslop", "de-AI", "make it sound human," "remove AI patterns," "remove AI tropes," "clean up AI writing," fix "slop," "deslop" text, or review prose for authenticity. Also use when the user asks you to write or draft anything and wants it to sound natural rather than AI-generated. Common use cases include scientific writing (manuscripts, abstracts, cover letters, grant narratives, discussion sections, peer review responses), blog posts, newsletters, memos, reports, and any other substantial prose.

every-app/open-seo Agent Skills author: every-app MIT 7 files body ≈ 1 936 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Remove AI writing patterns from prose.

As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

GeneratorWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
94
Run on models
none yet
Process rating
C
57/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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: 7. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 57/100

    • 0Result and completion. Does not say what the result is
    • 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
    • 30Running it twice. 8 mutating operations with no state check
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 26 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1936 tokens

    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)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +5Description quotes 6 example trigger phrases
    • +3Description length 732: enough signal without eating the budget
    • +4Structure: 17 headings
    • +3Step-by-step instructions: 26 items
    • +4Has examples (0 code blocks)
    • +4Reference files are cited in the instructions (4 of 4)
    • +1License stated

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