agentleFS
lalulalilalulali/vespyr/.agents/skills/deslop/SKILL.md

deslop

Skill11 starsChanged 11 days agoMITView on GitHub

Core Deslop and Plain-Clarity Engine (alias for /humanize) — removes AI writing patterns, replaces fancy/thesaurus words with plain words, and eliminates circumlocution. Use when polishing prose, specs, docs, or drafts to strip AI slop and make text easy to understand.

129 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use control-cli, openseo-review-web-content and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ElyzeSolutionsSkill

    control-cli

    Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.

    Also in 6 projects that use this

  • JwuthriSkill

    openseo-review-web-content

    Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.

    Also in 4 projects that use this

  • automagik-devSkill

    genie-hacks

    Browse, search, and contribute community hacks — real-world patterns for provider switching, teams, skills, hooks, cost optimization, and more.

    Also in 3 projects that use this

  • automagik-devSkill

    workfly

    Discover a procedure and build its saved workflow — dynamic discovery, drafted script, adversarial verification, landed in the catalog.

    Also in 3 projects that use this

  • JwuthriSkill

    simple-issue-description

    Turn a rough bug report, feature request, support note, or pull request into a short, plain-language issue focused on the problem and desired behavior. Use when a contributor asks to simplify an issue, explain what a PR is for, create the corresponding issue for a PR, remove implementation detail from a report, or invokes /simple-issue-description.

    Also in 4 projects that use this

  • learnerLjSkill

    verify-this

    Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.

    Also in 6 projects that use this

  • +2 more from Jwuthri
  • +3 more from automagik-dev

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 127 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When the user invokes /deslop or asks to "deslop this", "strip the AI slop", "stop using fancy words", or "make this easier to understand".

    line 23
  2. Distinctive:

    Before shipping any PRD, specification, guide, lesson, or document to ensure every sentence passes the One-Read Windowpane Test.

    line 24
  3. Very specific:

    Follow the complete workflow in .agents/skills/humanize/SKILL.md:

    line 34
  4. Distinctive:

    Ask: *"What makes the draft still read like an LLM wrote it, use fancy words, or circle around the point?"*

    line 42

“Common” is measured: kept by at least 6 in 10 of the 127 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deslop: Core Anti-Slop & Plain-Clarity Engine

What this skill does

Direct entry point for the Vespyr Core Deslop & Plain-Clarity Engine (DNA 7 §6, alias for /humanize). Identifies and removes statistical AI writing tells, replaces pretentious or fancy vocabulary (utilize, elucidate, ameliorate, juxtaposition, ubiquitous, ephemeral, endeavor, commence) with simple everyday words (use, explain, fix, contrast, everywhere, brief, try, start), and eliminates circumlocution that circles around the point (came to the realization that -> realized, in the process of -> cut).

Operates on the 33-Pattern Catalog (references/patterns.md), the multi-locale lexicon (references/anti-slop-lexicon.json), and the deterministic linter (scripts/prose_linter.js).

When to use

  • When the user invokes /deslop or asks to "deslop this", "strip the AI slop", "stop using fancy words", or "make this easier to understand".
  • Before shipping any PRD, specification, guide, lesson, or document to ensure every sentence passes the One-Read Windowpane Test.
  • Standalone deterministic lint check: node .agents/skills/deslop/scripts/prose_linter.js --file <path>

Workflow

  1. Run the Deterministic Linter (if operating on a file):
    node .agents/skills/deslop/scripts/prose_linter.js --file <path>
  2. Execute the Full Humanize & Plain-Clarity Pass: Follow the complete workflow in .agents/skills/humanize/SKILL.md:
    • Determine or infer the target tone (Casual, Conversational, Professional, Formal, Technical, Persuasive, Warm, Witty, Neutral).
    • Purge Patterns 1–29 (significance inflation, superficial -ing tails, promotional language, vague attributions, AI vocabulary, copula avoidance, negative parallelisms, rule of three, em dash spam, filler phrases).
    • Purge Patterns 30–33 (Plain-Word Clarity & Anti-Circumlocution):
      • Replace fancy/thesaurus words with crisp, everyday words.
      • Collapse zombie nominalizations and roundabout wrapper phrases into direct verbs.
      • Rewrite foggy multi-clause abstractions so every sentence is understood on the very first read.
  3. Two-Step Adversarial Self-Audit:
    • Ask: "What makes the draft still read like an LLM wrote it, use fancy words, or circle around the point?"
    • Fix the remaining tells and present the final clean version.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.