Skip to content
cccskills
FreePublished on GitHub

stop-slop

Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.

The English summary is being prepared. Showing the original description.

See how to install

Files included (4)

  • SKILL.md2.6 KB
  • references/examples.md1.6 KB
  • references/phrases.md2.8 KB
  • references/structures.md5.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Stop Slop

Eliminate predictable AI writing patterns from prose.

Core Rules

  1. Cut filler phrases. Remove throat-clearing openers, emphasis crutches, and all adverbs. See references/phrases.md.

  2. Break formulaic structures. Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency. See references/structures.md.

  3. Use active voice. Every sentence needs a human subject doing something. No passive constructions. No inanimate objects performing human actions ("the complaint becomes a fix").

  4. Be specific. No vague declaratives ("The reasons are structural"). Name the specific thing. No lazy extremes ("every," "always," "never") doing vague work.

  5. Put the reader in the room. No narrator-from-a-distance voice. "You" beats "People." Specifics beat abstractions.

  6. Vary rhythm. Mix sentence lengths. Two items beat three. End paragraphs differently. No em dashes.

  7. Trust readers. State facts directly. Skip softening, justification, hand-holding.

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

Quick Checks

Before delivering prose:

  • Any adverbs? Kill them.
  • Any passive voice? Find the actor, make them the subject.
  • Inanimate thing doing a human verb ("the decision emerges")? Name the person.
  • Sentence starts with a Wh- word? Restructure it.
  • Any "here's what/this/that" throat-clearing? Cut to the point.
  • Any "not X, it's Y" contrasts? State Y directly.
  • Three consecutive sentences match length? Break one.
  • Paragraph ends with punchy one-liner? Vary it.
  • Em-dash anywhere? Remove it.
  • Vague declarative ("The implications are significant")? Name the specific implication.
  • Narrator-from-a-distance ("Nobody designed this")? Put the reader in the scene.
  • Meta-joiners ("The rest of this essay...")? Delete. Let the essay move.

Scoring

Rate 1-10 on each dimension:

DimensionQuestion
DirectnessStatements or announcements?
RhythmVaried or metronomic?
TrustRespects reader intelligence?
AuthenticitySounds human?
DensityAnything cuttable?

Below 35/50: revise.

Examples

See references/examples.md for before/after transformations.

License

MIT

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

The English summary is being prepared. Showing the original description.

SDiamante13/dotfiles11Updated Oct 2, 2026

Rebuilds session context after a clear by reading git history, plans, and beads state. Triggers on 'catch up'.

The English summary is being prepared. Showing the original description.

SDiamante13/dotfiles11Updated Oct 2, 2026

Generate a bullet-point summary of branch changes for a PR description. Triggers on "changelog", "pr summary", "summarize branch", or "/changelog".

The English summary is being prepared. Showing the original description.

SDiamante13/dotfiles11Updated Oct 2, 2026

commit

Free

Commit the current changes with quality checks, status review, staged diff inspection, appropriate tests, and a clear commit message. Use when the user says "commit", "c", asks to make a commit, or wants changes saved in git.

The English summary is being prepared. Showing the original description.

SDiamante13/dotfiles11Updated Oct 2, 2026

Refactor code to remove dead code, useless comments, unused variables, and unused imports. Use when asked to declutter a class, clean up noisy code, remove cruft, or run `/refactor:declutter`.

The English summary is being prepared. Showing the original description.

SDiamante13/dotfiles11Updated Oct 2, 2026

dry

Free

Refactor duplicated code by extracting helpers, shared abstractions, or clearer reusable structure. Use when asked to apply DRY, remove duplication, consolidate repeated logic, or run `/refactor:dry`.

The English summary is being prepared. Showing the original description.

SDiamante13/dotfiles11Updated Oct 2, 2026

See all skills by SDiamante13

Report a problem with this skill