agentleFS
jonathanmalkinjonathanmalkin/jules/.claude/skills/stop-slop/SKILL.md

stop-slop

Skill65 starsChanged 7 months agoMITView on GitHub

Structural audit for AI writing patterns. Catches paragraph-level tells that word-level checks miss: false agency, binary contrasts, dramatic fragmentation, narrator-from-a-distance, formulaic rhythm. Scores on 5 dimensions (35/50 threshold). Use on content pipeline output before publishing. Invoke with /stop-slop.

49 other projects use a version of this, 38 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use banner-design, emails 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.
  • lithStudySkill

    banner-design

    Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.

    Also in 4 projects that use this

  • roerohanSkill

    emails

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

    Also in 3 projects that use this

  • MicrosoftSkill

    ui-styling

    Guide for the visual style, structure, and shared building blocks used by Semantic Link Labs interactive UI tools (HTML widgets and anywidget-based widgets). Use this when adding a new interactive UI, modifying an existing one, or adding shared visual components.

    Also in 4 projects that use this

  • lithStudySkill

    brand

    Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

    Also in 4 projects that use this

  • yologdevSkill

    social

    Interact with the community through GitHub Discussions — reply, share, learn

    Also in 3 projects that use this

  • JetBrainsSkill

    slides

    Create and edit presentation slide decks (`.pptx`) with PptxGenJS and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding charts/diagrams/visuals, or diagnosing layout issues such as overflow, overlaps, and font substitution.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 3 are common, 5 are distinctive, and 2 are very specific to this project.

  • 3

    Common

    Most of the 48 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do NOT run on: Jules conversational output, internal docs, code comments, quick replies.

    line 27
  2. Very specific:

    Break formulaic structures: No binary contrasts ("Not X.

    line 31
  3. Distinctive:

    Use active voice: Every sentence needs a subject doing something.

    line 35
  4. Common:

    Be specific: No vague declaratives ("The reasons are structural").

    line 37
  5. Common:

    Put the reader in the room: No narrator-from-a-distance.

    line 39
  6. Common:

    Cut quotables: If it sounds like a pull-quote, rewrite it.

    line 45
  7. Distinctive:

    No formulaic article structure: Don't default to: intro hook, context, 3-5 body sections, takeaway, CTA.

    line 47
  8. Distinctive:

    Commit or don't claim: No hedging every other sentence with "might," "could potentially," "it remains to be seen." Either make the claim or …

    line 49
  9. Distinctive:

    Before delivering prose, scan for:

    line 53
  10. Distinctive:

    When invoked as an audit:

    line 86

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

Stop Slop: Structural AI Pattern Audit

<!-- Source: hardikpandya/stop-slop (fetched 2026-03-24), with cherry-picks from blader/humanizer and mshumer/unslop blog-writing profile. Snapshot, not auto-updated. -->

Eliminate structural AI writing patterns from prose. This skill focuses on paragraph-level and structural tells that survive word-level editing. Voice-Profile.md handles banned words/phrases. This handles the architecture of the writing.

When to Use

  • Content pipeline output (articles, Reddit posts, X threads) before publishing
  • As part of /write-article Stage 5 review panel
  • In content agent humanize mode as Pass 3 (structural audit)
  • Manual invocation via /stop-slop on any draft

Do NOT run on: Jules conversational output, internal docs, code comments, quick replies.

Core Rules

  1. Break formulaic structures. No binary contrasts ("Not X. Y."), negative listings, dramatic fragmentation, rhetorical setups. See references/structures.md.
  2. Kill false agency. Inanimate things don't perform human actions. "The complaint becomes a fix" = no. "The team fixed it" = yes. Name the human actor.
  3. Use active voice. Every sentence needs a subject doing something. No passive constructions hiding the actor.
  4. Be specific. No vague declaratives ("The reasons are structural"). Name the specific thing.
  5. Put the reader in the room. No narrator-from-a-distance. "You" beats "People." Specifics beat abstractions.
  6. Vary rhythm. Mix sentence lengths. Two items beat three. End paragraphs differently. No em dashes. No staccato fragmentation stacking.
  7. Trust readers. State facts directly. Skip softening, justification, hand-holding.
  8. Cut quotables. If it sounds like a pull-quote, rewrite it.
  9. No formulaic article structure. Don't default to: intro hook, context, 3-5 body sections, takeaway, CTA. Vary. No "Final thoughts" or "Key takeaways" headers. No rhetorical questions as section transitions.
  10. Commit or don't claim. No hedging every other sentence with "might," "could potentially," "it remains to be seen." Either make the claim or drop it.

Quick Checks

Before delivering prose, scan for:

  • Inanimate thing doing a human verb? Name the person.
  • "Not X, it's Y" binary contrast? State Y directly.
  • Three consecutive sentences match length? Break one.
  • Paragraph ends with punchy one-liner? Vary it.
  • Any "here's what/this/that" throat-clearing? Cut to the point.
  • Narrator-from-a-distance ("Nobody designed this")? Put the reader in the scene.
  • Formulaic structure (hook, context, 3 body sections, takeaway)? Vary it.
  • Rule-of-three construction? Use two items or one.
  • Synonym cycling (protagonist, main character, central figure)? Just repeat the clearest word.
  • "Serves as" / "stands as" / "features" instead of "is" / "has"? Use the simple copula.
  • False range ("from X to Y" where the scale is meaningless)? List topics directly.
  • Sentence lengths clustering in 10-20 word range? Calculate SD of word counts per sentence. SD < 8 = metronomic (AI tell). [Your Name]'s writing: SD 9-14.

Scoring Rubric

Rate 1-10 on each dimension:

DimensionQuestion
DirectnessDoes it state things or announce them? Is it making points or building up to them?
RhythmDo sentence lengths vary naturally, or is the cadence metronomic? Any staccato stacking? Burstiness check: Calculate the standard deviation of sentence word counts across the draft. Human writing typically has SD > 8 words ([Your Name]'s samples: SD 9-14). Flag if SD < 8 as "metronomic uniformity" and cap Rhythm score at 6/10 regardless of other rhythm qualities. Report the SD value in the audit output.
TrustDoes it respect reader intelligence, or does it soften, justify, and hand-hold?
AuthenticityDoes it sound like a specific human wrote it, or like median-internet-text?
DensityIs every sentence doing work, or is there cuttable filler?

Threshold: 35/50. Below 35: surface specific failing patterns with suggested rewrites. The human reviewer must explicitly approve or revise before publication.

Calibration note: 35/50 was calibrated against [Your Name]'s published articles (scored 38-44) and raw voice samples (scored 40-47). Adjust if publishing standards change.

Output Format

When invoked as an audit:

## Stop-Slop Audit

**Score: [N]/50** (Directness: X | Rhythm: X | Trust: X | Authenticity: X | Density: X)
**Burstiness:** Sentence length SD = X.X words (threshold: 8.0 | [Your Name] baseline: 9-14)

### Findings

[List each structural pattern found, with line reference and severity]

### Suggested Rewrites

[For each finding, show the original and a rewritten version]

### Verdict

PASS (score >= 35) / REVISE (score < 35, with specific items to address)

References

  • references/phrases.md — Phrase-level patterns to cut (deduplicated against Voice-Profile.md)
  • references/structures.md — Structural anti-patterns with examples
  • references/examples.md — Before/after transformations

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.