isatimur/de-slop / skills/de-slop
de-slop
VerifiedUse when prose reads like AI — to remove "AI slop" (empty hedging, listicle stems, smooth transitions that hide the absence of a claim, generic filler) and rewrite it into writing with a real point of view. Trigger on requests like "humanize this", "de-slop", "remove the AI slop", "make this sound less like AI / less like ChatGPT", "this reads like AI", or after generating prose that needs a quality pass. Detects, rewrites the fixable parts, self-scores against an embedded rubric, and iterates to a bar — preserving meaning exactly, flagging hollow spans instead of inventing claims, and reporting changes rather than overwriting.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.4 KB |
| references/examples.md | markdown | 8.6 KB |
| references/guardrails.md | markdown | 2.4 KB |
| references/rubric.md | markdown | 3.8 KB |
| references/slop-catalogue.md | markdown | 9.9 KB |
| scripts/build_adapters.py | script | 7.6 KB |
| scripts/flag_slop.py | script | 21.2 KB |
| scripts/setup-github.shexecutable | script | 2.0 KB |
references/guardrails.md
View on GitHub# Guardrails
Apply these to every rewrite. The goal is to remove slop, not to perform
"humanness." A rewrite that violates these is a failure even if it scores well.
## Fidelity (the prime rule)
- Preserve the original **meaning and claims exactly**. The rewrite says the same
thing the author meant — only clearer and without padding.
- You may **subtract** (hedging, filler, dead transitions) and **sharpen** (make
an existing claim concrete, surface the point that was buried).
- You may **not add** a claim, opinion, statistic, example, or stance that was not
already in the source. If the point isn't there, that's a HOLLOW span — flag it,
don't fill it.
- **No invented numbers, names, or mechanisms.** If the source never said
"microseconds," "Postgres," "JSON/CSV," or a similar specific, you may not put
it in the rewrite — even when it would sound sharper. Specificity without
source grounding is fabrication.
## Over-correction anti-patterns (never inject these)
The classic failure of "humanizer" tools is trading AI-slop for a louder slop.
Do not introduce any of:
- **Forced contrarianism / hot takes** — "Everyone says X, but they're wrong."
(unless the source actually argued this)
- **Em-dash theatrics** — dramatic dashes manufacturing emphasis the content
doesn't earn.
- **Fake first person** — "I've seen this a hundred times", "In my experience"
inserted into prose that had no author-presence.
- **"Let's be honest / let's be real / here's the thing"** — performed candor.
- **Manufactured stakes** — "In a world where…", "Now more than ever", "The
stakes have never been higher."
- **Rhetorical-question openers** — "What if I told you…?", "Ever wondered why…?"
- **Intensifier padding** — "genuinely", "truly", "honestly", "literally" as
flavor.
These are slop in a different costume. The bar is a *thinking* author, not a
*loud* one.
## Idempotence
- If a paragraph already scores **strong**, return it unchanged. The skill must do
nothing to good prose.
- Running the skill twice on the same text must produce the same result the second
time as the first (the first run's output is already at the bar).
## When in doubt
Prefer the smaller edit. The best de-slop is usually deletion of the hedge plus
nothing else. If you can't improve a sentence without inventing content, you've
found a hollow span — flag it and move on.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |