agentleFS
Fractal-TessFractal-Tess/agents/skills/unslop/SKILL.md

unslop

Skill1 starsChanged 3 months agoMITView on GitHub

Remove AI writing patterns from prose. Use for docs, READMEs, blog posts, any non-code text that should sound human. Triggers: "unslop", "humanize", "make this sound human", "clean up this writing", "edit for voice", "de-AI this text".

197 other projects use a version of this, 140 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use principle-never-block-on-the-human, greploop-apps 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.
  • jaydubya818Skill

    principle-never-block-on-the-human

    Apply when safe reversible implementation details can proceed inside scope.

    Also in 45 projects that use this

  • jaydubya818Skill

    greploop-apps

    Run greploop through @greptile-apps when the normal trigger rejects a large PR. Use only with the companion greploop skill.

    Also in 5 projects that use this

  • ianclearySkill

    principle-explain-the-number

    Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 30 projects that use this

  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 26 projects that use this

  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 15 projects that use this

  • +7 more from jaydubya818

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 193 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add soul (see next section)

    line 17

“Common” is measured: kept by at least 6 in 10 of the 193 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

Unslop

Edit text to remove AI patterns and add human voice.

Process

  1. Scan for the patterns below
  2. Rewrite — preserve meaning, match intended tone
  3. Add soul (see next section)
  4. Self-audit: "What makes this obviously AI generated?" Fix remaining tells.

Adding soul

Removing patterns is half the job. Sterile, voiceless writing is just as obvious.

  • Have opinions. React to facts instead of neutrally listing pros and cons.
  • Vary rhythm. Short sentences. Then longer ones that take their time. Mix it up.
  • Acknowledge complexity. "Impressive but also kind of unsettling" beats "impressive."
  • Use "I" when it fits. First person isn't unprofessional.
  • Let some mess in. Perfect structure feels algorithmic.
  • Be specific. Not "this is concerning" but "there's something unsettling about agents churning away at 3am."

Patterns to detect and fix

Content

  1. Significance inflation — "pivotal moment", "testament to", "evolving landscape", "setting the stage for", "indelible mark", "deeply rooted". Cut puffery, state what happened.
  2. Notability name-dropping — listing media outlets without context. Pick one, say what was said.
  3. Superficial -ing phrases — "highlighting...", "ensuring...", "reflecting...", "showcasing...", "fostering...". Delete or expand with real sources.
  4. Promotional language — "nestled", "vibrant", "breathtaking", "groundbreaking", "renowned", "stunning", "must-visit". Use neutral descriptions.
  5. Vague attributions — "Experts believe", "Industry reports suggest", "Some critics argue". Name the source or delete.
  6. Formulaic challenges — "Despite challenges... continues to thrive." Replace with specific facts.

Language

  1. AI vocabulary — Additionally, crucial, delve, enduring, enhance, fostering, garner, interplay, intricate, landscape (abstract), pivotal, showcase, tapestry (abstract), testament, underscore, vibrant. Replace with plain words.
  2. Copula avoidance — "serves as", "stands as", "boasts", "features". Just say "is" or "has".
  3. Negative parallelisms — "It's not just X, it's Y." State the point directly.
  4. Rule of three — forcing ideas into groups of three. Use the natural number.
  5. Synonym cycling — protagonist/main character/central figure/hero in one paragraph. Pick one, repeat it.
  6. False ranges — "from X to Y" where X and Y aren't on a meaningful scale. List topics directly.

Style

  1. Em dash overuse — avoid em dashes entirely. Use periods, commas, or parentheses. Em dashes are an AI tell.
  2. Colon overuse — colons are fine before a list or example. Not as mid-sentence connectors. "If you're coming from traditional automation: instead of registering event handlers, you describe conditions" adds nothing with the colon. Rewrite to let the point stand on its own without comparison framing. "Describing when the scheduler should fire works best as plain English." Same meaning, no crutch punctuation.
  3. Boldface overuse — don't bold every proper noun or acronym.
  4. Inline-header lists — "Performance: Performance improved..." Convert to prose.
  5. Title case headings — use sentence case.
  6. Decorative emojis — remove from headings and bullets.
  7. Curly quotes — replace with straight quotes.

Communication artifacts

  1. Chatbot phrases — "I hope this helps!", "Let me know if...", "Of course!", "Certainly!" Remove.
  2. Cutoff disclaimers — "While specific details are limited..." Find sources or remove.
  3. Sycophantic tone — "Great question! You're absolutely right!" Respond directly.

Filler

  1. Filler phrases — "In order to" → "To". "Due to the fact that" → "Because". "It is important to note that" → delete.
  2. Excessive hedging — "could potentially possibly be argued that it might" → "may".
  3. Generic conclusions — "The future looks bright." State specific plans or facts.

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.