unslop
Skill0 starsChanged 2 months agoMITView on GitHub
Cut AI tells from any writing. Must always apply.
197 other projects use a version of this, 137 of them edited.
Adopted by
Most recently taken up by
- shiwenbin1617/pstackedited, first seen Nov 16, 2026
- MetrolistGroup/Metrolistedited, first seen Nov 15, 2026
- mostafaalagamy/Metrolistedited, first seen Nov 15, 2026
- backnotprop/pstackedited, first seen Nov 15, 2026
- titouannwtt/claude-toolstheir own version, first seen Nov 15, 2026
- asarelcastellanos/claude-workbenchedited, first seen Nov 15, 2026
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.
jaydubya818Skillprinciple-never-block-on-the-human
Apply when safe reversible implementation details can proceed inside scope.
Also in 45 projects that use this
jaydubya818Skillgreploop-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
ianclearySkillprinciple-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
bnemaSkillsetup-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
ianclearySkillpoteto-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
Other versions197 projects use a version of this.
Word for word · 0
None found.
Edited · 137
- MetrolistGroup/Metrolist★ 14k43% same
- mostafaalagamy/Metrolist★ 14k43% same
- tester-army/e2e★ 14k39% same
- jaredpalmer/kev★ 9.8k46% same
- backnotprop/pstack★ 4.2k43% same
- michaelshimeles/rstack★ 1.4k37% same
- michaelshimeles/skills★ 1.4k37% same
- VladSez/easy-invoice-pdf★ 1.1k45% same
- moeru-ai/xsai★ 66743% same
- chinmay-sawant/gopdfsuit★ 60736% same
127 more not listed
Wrote their own version · 60
- heydamir/unslop★ 17ksame name
- theclaymethod/unslop★ 1.1ksame name
- Silo-Server/silo-server★ 899same name
- nodetool-ai/nodetool★ 637same name
- mshumer/unslop★ 551same name
- mxyhi/ok-skills★ 511same name
- savannahfeder/agentbox★ 419same name
- MohamedAbdallah-14/unslop★ 192same name
- alexj11324/Mikka★ 87same name
- asavvin-pixel/unslop★ 61same name
50 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- rules/AGENTS.mdAGENTS.md
- kurokoSkill
- tayoriSkill
- xerjSkill
- aesthetic-readme-craftSkill
- cli-builderSkill
- codebase-digestSkill
- git-release-craftSkill
- git-repo-craftSkill
- karakuriSkill
- python-clean-codeSkill
- rust-clean-codeSkill
- rust-style-pythonSkill
- systematic-code-verificationSkill
- compose-clean-codeSkill
- bash-clean-codeSkill
- tui-designSkill
- frontend-designSkill
- web-design-guidelinesSkill
The file
We split this skill into the rules it gives an agent
4 rules. 2 are common, 1 is distinctive, and 1 is very specific to this project.
2
Common
Most of the 192 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
Em dash overuse: Avoid em dashes entirely. Use periods or commas only (no parentheses, no en dashes, no hyphen-as-dash substitutes).
- Common: line 42
Boldface overuse: Don't bold every proper noun or acronym.
- Common: line 44
Title case headings: Use sentence case.
- Very specific: line 45
Decorative emojis: Remove from code comments, commit messages, and inline prose.
“Common” is measured: kept by at least 6 in 10 of the 192 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.
Files
Unslop
Karakuri override — Rule 18: Decorative emojis are ALLOWED in README headings and bullet feature lists (required by
aesthetic-readme-craft). Remove emojis only from code comments, commit messages, and inline prose.
Edit text to remove AI patterns.
Process
- Scan for the patterns below.
- Rewrite. Preserve meaning, match intended tone.
Patterns to detect and fix
Rule numbers are stable ids that other skills cite. A removed rule leaves a gap.
Content
- Superficial -ing phrases. "highlighting...", "ensuring...", "reflecting...", "showcasing...", "fostering...". Delete or expand with real sources.
- Vague attributions. "Experts believe", "Industry reports suggest", "Some critics argue". Name the source or delete.
Language
- AI vocabulary. Additionally, crucial, delve, enduring, enhance, fostering, garner, interplay, intricate, landscape (abstract), pivotal, showcase, tapestry (abstract), testament, underscore, vibrant. Replace with plain words.
- Fancy ways to say "is". "serves as", "stands as", "boasts", "features". Just say "is" or "has".
- "Not just X, but Y." State the point directly instead.
- Rule of three. Forcing ideas into groups of three. Use the natural number.
- Synonym cycling. Protagonist, main character, central figure, hero all in one paragraph. Pick one, repeat it.
- False ranges. "from X to Y" where X and Y aren't on a meaningful scale. List topics directly.
Style
- Em dash overuse. Avoid em dashes entirely. Use periods or commas only (no parentheses, no en dashes, no hyphen-as-dash substitutes). If a thought needs separation, end the sentence or use a comma.
- 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.
- Boldface overuse. Don't bold every proper noun or acronym.
- Inline-header lists. The tell is a bold label and colon that restates the line: "Performance: Performance improved...". Convert those to prose. A bold lead-in that ends in a period, names the item, and is followed by genuinely new detail ("Schema in TypeScript. Tables live in one file.") is fine, not a tell.
- Title case headings. Use sentence case.
- Decorative emojis. Remove from code comments, commit messages, and inline prose. Exception: README headings and feature bullet lists (see Karakuri override above).
- Curly quotes. Replace with straight quotes.
Communication artifacts
- Chatbot phrases. "I hope this helps!", "Let me know if...", "Of course!", "Certainly!", "Found the smoking gun!" Remove.
- Sycophantic tone. "Great question! You're absolutely right!" Respond directly.
Filler
- Filler phrases. "In order to" becomes "To". "Due to the fact that" becomes "Because". "It is important to note that" gets deleted.
- Excessive hedging. "could potentially possibly be" — pick one hedge or delete.
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
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.

