JasonColapietro/suede-creator-skills / skills/suede-deslop
suede-deslop
VerifiedUse when asked "deslop this draft" or to audit finished prose before shipping. Suede Slop Stop Skills removes filler, false agency, formulaic rhythm, chat residue and misplaced formatting while preserving voice and protected facts. Returns edited prose and a 50-point score, or findings only. NOT FOR: rewriting the argument (use suede-copy), research orchestration (use suede-ship-copy), authorship detection, or certifying facts.
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.9 KB |
| SKILL.md | skill md | 13.0 KB |
| agents/openai.yaml | config | 579 B |
| references/editing-rules.md | markdown | 10.3 KB |
| references/kill-list.md | markdown | 18.0 KB |
| references/usage-contract.md | markdown | 883 B |
references/editing-rules.md
View on GitHub# Editing Rules
## The ten rules
### 1. Cut filler phrases
No throat-clearing before the point. No emphasis crutches that add weight without meaning. No adverbs doing work a specific fact should do.
The kill list, 27 highest-frequency offenders:
| Category | Kill | Fix |
|----------|------|-----|
| Opener | Here's the thing: | Start with the point |
| Opener | Let's be honest / Let's face it | Cut; say the honest thing |
| Opener | The truth is / The reality is | Cut; state it |
| Opener | It's worth noting that | Cut; note it |
| Opener | In today's fast-paced world | Cut the sentence |
| Opener | Picture this: / Imagine this: | Describe the scene directly |
| Opener | At its core / At the end of the day | Cut; make the core claim |
| Crutch | Let that sink in / Read that again | Cut; the sentence carries or it does not |
| Crutch | genuinely / truly / literally | Cut |
| Crutch | actually / really / very | Cut |
| Crutch | full stop / period (as emphasis) | Cut |
| Crutch | make no mistake | Cut |
| Jargon | leverage (as a verb) | use |
| Jargon | utilize | use |
| Jargon | delve into | cover, get into |
| Jargon | navigate (a challenge) | handle, work through |
| Jargon | landscape / ecosystem (abstract) | market, field, or the named thing |
| Jargon | journey (not travel) | process, or name the steps |
| Jargon | unlock / unleash | say what was blocked |
| Jargon | game-changer / tapestry | name the change, or the parts |
| Joiner | moreover / furthermore | cut, or "also" |
| Jargon | robust / seamless / powerful | name the capability or prove it |
| Jargon | elevate / empower / transform | say what changes, before and after |
| Adverb | incredibly / remarkably / surprisingly | cut, or give the number that surprises |
| Adverb | seamlessly / effortlessly | cut; show the step count |
| Adverb | fundamentally / essentially / ultimately | cut; the claim stands or it does not |
| Adverb | importantly / notably | cut; if it matters, the content shows it |
The table is the high-frequency cut. The full sweep, with forty-plus more phrases across every category, lives in [references/kill-list.md](kill-list.md); run it when the text goes to press, investors, or customers. Three categories the table compresses:
- **Adverbs, contextual rule.** Cut adverbs that merely intensify, soften, or
announce importance. Keep an adverb when it carries factual, technical,
legal, quoted, or voice-specific meaning.
- **Meta-commentary.** The piece moves; it never announces its own structure. Cut "Let me walk you through", "In this section, we'll", "As we'll see", "Plot twist:", "Hint:", "But that's another post", "X is a feature, not a bug".
- **Performative sincerity.** False intimacy and announced significance. Cut "I promise", "creeps in", "This is genuinely hard", "This is what X actually looks like", "actually matters". Show the difficulty; never claim it.
Bad: "Here's the thing: this is genuinely hard. Let that sink in."
Good: "This is hard."
---
### 2. Break formulaic structures
The patterns the model reaches for when it has nothing original to say. Each with its fix:
- **Binary contrast** ("It's not about speed. It's about precision.") | Fix: state the real claim directly. "Precision matters more than speed here."
- **"Isn't just" construction** ("This isn't just a tool, it's a platform.") | Fix: cut the setup; say what it is with one proof.
- **Negative listing** ("No setup. No config. No hassle.") | Fix: one positive sentence naming what the user does.
- **Dramatic fragment** ("One problem." / "And it worked.") | Fix: attach the fragment to the sentence it modifies.
- **Rhetorical setup** ("So what does this mean for you?" / "What if I told you...?" / "Think about it:") | Fix: delete the question; give the answer.
- **False agency** ("The data tells us" / "the decision emerges" / "the culture shifts" / "the market rewards") | Fix: name the person. "We measured." "I argue." If no one fits, use "you".
- **Triad rhythm** ("Faster. Cleaner. Better.") | Fix: two items, or a full sentence. Three-beat lists only when the count is really three.
- **Reveal fragment** ("[Noun]. That's it. That's the [thing].") | Fix: one complete sentence, no staged reveal.
- **Formulaic template** ("By the time X, I was Y." / "X that isn't Y") | Fix: drop the template; state the fact. "X is broken."
- **Permission grant** ("And that's okay.") | Fix: cut it; the reader did not ask.
Binary contrast alone has eleven spellings ("The answer isn't X. It's Y." / "It feels like X. It's actually Y." / "stops being X and starts being Y" and more); the full variant table is in [references/kill-list.md](kill-list.md).
Bad: "It's not about speed. It's about precision."
Good: "Precision matters more than speed here."
---
### 3. Prefer active voice when the actor matters
Name the actor when responsibility or causality matters. Keep passive voice when
the actor is unknown, immaterial, deliberately withheld, or conventional in the
technical context. Do not force a human subject into a sentence that does not
need one.
Bad: "The decision was reached after careful consideration."
Good: "The team decided after reviewing three options."
Bad: "Mistakes were made."
Good: "Name who made them."
---
### 4. Be specific
No vague declaratives. No lazy extremes. Name the specific thing.
Lazy extremes are every, always, never, everyone, everybody, nobody: false authority doing vague work. Vague declaratives announce weight without naming it: "The reasons are structural", "The stakes are high", "This is the deepest problem", "The consequences are real".
Bad: "The implications are significant."
Good: Name the implication.
Bad: "Everyone knows this."
Good: Name who knows it and what they know.
---
### 5. Put the reader in the room when the genre supports it
Specifics beat abstractions. In direct guidance, "you" often beats a vague
"people." Preserve third-person, academic, legal, or documentary register when
the source calls for it.
Bad: "Nobody designed this. It just happened."
Good: "You didn't sit down and decide to build this. It accumulated."
---
### 6. Vary rhythm
Mix sentence lengths. Two items often beat three. End paragraphs differently.
Follow the supplied house style for em dashes. For Suede public copy,
replace them with commas, parentheses, colons, or periods. Do not treat
punctuation as evidence of authorship.
Suede public copy also avoids promotional exclamation points; preserve
them in protected source spans or when the supplied house style calls for them.
Three consecutive sentences at the same length: break one. Every paragraph ending with a punchy one-liner: vary it. Staccato fragments stacked for effect: merge them. A question answered in the same breath: let it breathe or cut it. Hedging dressed as reassurance ("Not always. Not perfectly."): cut it.
Sentence starters count as rhythm. Wh- openers ("What makes this hard is...") read as a crutch: lead with the subject ("The constraint is..."). Paragraphs opening with "So": start with content. Sentences opening with "Look,": remove.
---
### 7. Trust the reader
State facts directly. Skip softening, justification, hand-holding. The reader is an adult.
Cut: "I want to be clear that..." / "It's important to note that..." / "As you might expect..."
Start with the content.
---
### 8. Cut quotables
If a sentence sounds like it was written to be screenshotted, rewrite it. Pull-quote prose is manufactured. Cut the performance.
---
### 9. Strip chat and draft leftovers
Delete these outright; nothing here needs rewriting. This is the most certain
rule in the skill, because a careful writer does not leave a chat wrapper or a
cutoff disclaimer in finished prose. Act on one sighting.
- **Assistant wrapper** ("Great question!", "Of course!", "Certainly!", "You're absolutely right", "I hope this helps", "Let me know if you'd like me to expand", "Want me to...?") | Fix: delete the wrapper; keep the content inside it.
- **Knowledge-limit disclaimer** ("as of my last update", "while specific details are limited", "in the available sources", "not widely documented") | Fix: state plainly what the source does not show, or cut the sentence.
- **Gap filled with a guess** ("Details are not public, suggesting she keeps a low profile. She likely studied...") | Fix: cut the guess. Name the gap; never present an inference as a fact.
- **Argument with no one** ("I'm not saying", "Don't get me wrong", "To be clear", "A tempting approach would be", "One might be tempted to", "You might think... but") | Fix: cut the defense. If it carries a real claim, state the claim. Keep an objection the text actually attributes and answers, and keep an option a reader would genuinely weigh.
- **Heading restated in the sentence below it** ("## Performance" followed by "Speed matters.") | Fix: delete the restatement; start with the content.
- **Writing about the version this replaced** ("This function was added to replace the previous approach of iterating through all items") | Fix: describe current behavior. Prior-version talk belongs in changelogs, release notes, and migration guides.
Bad: "Great question! Here's the overview. I hope this helps, let me know if you'd like me to expand on any section."
Good: "[the overview, and nothing else]"
---
### 10. Remove formatting applied by rule
Decoration on *every* item is the signal, not decoration anywhere. Templates and
visual editors produce clean formatting too, so weigh the pattern across the
whole document rather than one heading.
- **Bold as decoration** (bold on terms carrying no more weight than their neighbors) | Fix: remove the bold.
- **Bold-labeled list** (every bullet opening `**Label:**` and then restating the label) | Fix: turn it into prose when the labels carry no information of their own.
- **Title Case Headings** | Fix: sentence case.
- **Emoji, arrows, or rules as ornament** (an emoji on each bullet, arrows between items, a horizontal rule between every section) | Fix: strip the ornament; let the structure carry itself.
- **Title repeated as a heading under itself** | Fix: let the title stand once.
- **Curly quotes in a straight-quote context** | Fix: match the target format. *Weak alone;* most editors auto-curl.
- **Avoiding is, are, and has** ("serves as", "stands as", "functions as", "boasts", "features", "represents a") | Fix: use is, are, has.
Bad: "- **Security:** Security has been strengthened with end-to-end encryption."
Good: "The update adds end-to-end encryption."
---
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |