agentleFS
refpathrefpath/chatgpt-team/.agents/skills/unslop/SKILL.md

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

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

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
  1. Distinctive:

    Read the whole passage before editing.

    line 8
  2. Distinctive:

    Prefer natural sentences and useful paragraph structure.

    line 12
  3. Distinctive:

    Remove rhetorical question-and-answer patterns, strained contrasts, and decorative jargon when they obscure the point.

    line 13
  4. Distinctive:

    Keep useful explanations and examples.

    line 14

“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

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.

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.