agentleFS
calebnewtonusccalebnewtonusc/apply-kit/.claude/skills/no-slop-writing/SKILL.md

no-slop-writing

Skill0 starsChanged 36 days agoMITView on GitHub

Remove the patterns that make writing read as AI-generated or as generic application filler. Applies to drafts and to your own messages. Use when writing or reviewing any prose in this repo.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. mangue-dev/minddy★ 1same name
    2. atreya2011/agent-skills★ 0same name
    3. ynfra/ynoslop★ 0same name

    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 repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 8

    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:

    No closing aphorism: Delete the mic-drop line at the end.

    line 30
  2. Distinctive:

    No synonym cycling: If the right word is "org," say "org" three times.

    line 44
  3. Distinctive:

    If yes, it is filler, no matter how well written.

    line 76
  4. Distinctive:

    Run it on the opening sentence first.

    line 80
  5. Distinctive:

    When asked to scan rather than rewrite, report:

    line 84
  6. Distinctive:

    Every line with a machine tic, quoted, with the fix.

    line 86
  7. Distinctive:

    Every line that fails the portability test, quoted.

    line 87
  8. Distinctive:

    Do not rewrite unless asked.

    line 91

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

No slop

These rules apply to drafts, to files you create, and to your own messages to the applicant. Not only when asked.

Two separate problems get called "AI writing." One is the machine's tics. The other is application filler, which humans have produced without help for decades. Both make an answer skippable. Hunt both.

Machine tics

No em dashes. Colon, period, or comma. This one is nearly diagnostic on its own.

No binary contrast. "It's not X, it's Y." "The question isn't X, it's Y." Just state Y.

No throat-clearing. "Here's the thing." "Let me be clear." "To be honest." Open on the point.

No faux-insight setup. "What nobody tells you." "The part everyone misses." "Most people get this wrong." These flatter the writer. Make the claim stand alone.

No colon reveals. "The best part: it learns." Write it as a sentence.

No closing aphorism. Delete the mic-drop line at the end. End on the last concrete point.

No summary endings. "In conclusion." "Ultimately." "Overall." They just read it.

No importance puffery. "A testament to." "Underscores." "Speaks to." "Marks a pivotal moment." State the fact and let the reader judge.

No metadiscourse. "That matters more than it sounds." "The key point is." If it is clear, delete the aside.

No superficial -ing clauses. "...highlighting my commitment to collaboration." This is the single most common tell in application essays.

No synonym cycling. If the right word is "org," say "org" three times.

No rule of three by default. "Curious, driven, and collaborative." Real writing has uneven lists.

No dramatic fragments. "That's it. That's the whole thing."

Banned words: delve, foster, leverage, utilize, facilitate, empower, streamline, robust, seamless, cutting-edge, transformative, elevate, harness, meticulous, intricate, realm, tapestry, ever-evolving, myriad, testament, invaluable, pivotal.

Cut empty phrases: "it's worth noting," "at the end of the day," "when it comes to," "in today's world," "the reality is," "I am eager to."

Application filler

Different problem, same effect. These are true, positive, and worthless because everyone writes them.

  • "I am passionate about the intersection of X and Y."
  • "I hope to both learn from and contribute to this community."
  • "Your commitment to excellence resonates with me."
  • "This experience taught me the importance of communication."
  • "I thrive in fast-paced, collaborative environments."
  • "I would be honored to be part of such a driven group of individuals."
  • Any sentence naming a soft skill instead of showing it.

The portability test

The one test that catches everything. Could this sentence appear in another applicant's essay, to another org, unchanged?

If yes, it is filler, no matter how well written. Cut it or replace it with something that is only true here: a name, a number, a mechanism, a specific opinion someone could disagree with.

Run it on the opening sentence first. That is where filler does the most damage.

Detect mode

When asked to scan rather than rewrite, report:

  1. Every line with a machine tic, quoted, with the fix.
  2. Every line that fails the portability test, quoted.
  3. A count of banned words with locations.
  4. One judgment: does this read as the applicant, or as a competent stranger.

Do not rewrite unless asked. A scan the applicant acts on themselves teaches them the patterns. A silent rewrite does not.

Rewrite mode

Preserve their voice. The goal is their sentences with the tics removed, not your sentences. If they write short and blunt, keep it short and blunt. If they use a comma splice on purpose, leave it.

Fix the pattern, change nothing else. Then show a diff-style before and after for anything you touched, so they can veto it.

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.