unslop
Skill0 starsChanged 2 months agoMITView on GitHub
Edit prose for clear, natural technical writing by removing filler, repetition, inflated claims, and awkward phrasing while preserving meaning. Use for an editorial pass, not automatic code or terminology replacement.
197 other projects use a version of this.
Adopted by
Most recently taken up by
- alastairlundy/skillstheir own version, first seen Nov 8, 2026
- sanjaibalajee/skillstheir own version, first seen Nov 8, 2026
- ku5ic/claude-kittheir own version, first seen Nov 8, 2026
- augchan42/inkstonetheir own version, first seen Nov 8, 2026
- caidanw/skillstheir own version, first seen Nov 8, 2026
- runkids/my-skillstheir own version, first seen Nov 8, 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 · 0
None found.
Wrote their own version · 197
- tester-army/e2e★ 13ksame name
- heydamir/unslop★ 12ksame name
- jaredpalmer/kev★ 9.8ksame name
- backnotprop/pstack★ 3.8ksame name
- michaelshimeles/rstack★ 1.4ksame name
- michaelshimeles/skills★ 1.4ksame name
- VladSez/easy-invoice-pdf★ 1.1ksame name
- Silo-Server/silo-server★ 899same name
- moeru-ai/xsai★ 667same name
- nodetool-ai/nodetool★ 615same name
187 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 repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- elixir-docsSkill
- feature-planSkill
- independent-reviewSkill
- multi-repo-changeSkill
- package-readinessSkill
- parallel-deliverySkill
- safe-refactorSkill
- security-reviewSkill
- stack-elixirSkill
- stack-nextjsSkill
- stack-phoenix-liveviewSkill
- stack-rustSkill
- stack-svelteSkill
- systematic-debuggingSkill
- technical-writingSkill
- ui-validationSkill
- worktree-integrationSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 193 edited versions we read keep these.
4
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
- Distinctive: line 8
Read the whole passage before editing.
- Distinctive: line 12
Prefer natural sentences and useful paragraph structure.
- Distinctive: line 13
Remove rhetorical question-and-answer patterns, strained contrasts, and decorative jargon when they obscure the point.
- Distinctive: line 14
Keep useful explanations and examples.
“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.
Files
Edit for clarity
Read the whole passage before editing. Establish its audience and the claims, qualifications, and instructions that must survive.
- Replace vague praise with a concrete fact when supported; otherwise remove it.
- Cut introductions that delay the point, repeated conclusions, and sentences that add no information.
- Prefer natural sentences and useful paragraph structure. Use lists for parallel items or steps; avoid turning every sentence into a heading or bullet.
- Remove rhetorical question-and-answer patterns, strained contrasts, and decorative jargon when they obscure the point.
- Keep useful explanations and examples. Shorter is not automatically clearer; do not pad or compress to a word-count target.
- For comments, explain intent, constraints, or a non-obvious decision rather than narrating syntax.
Preserve code, commands, identifiers, technical terms, quoted text, numbers, units, links, uncertainty, and requirement words unless the assignment includes a verified correction. Do not run global banned-word replacements or weaken test assertions as a prose cleanup.
Compare the edited passage with the original: does it still promise the same behavior under the same conditions? If a claim appears unsupported, verify it from source or flag it; do not silently make it sound certain. Report substantive changes or unresolved claims when useful, without a ritual account of every stylistic edit.
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.

