deslop-en/SKILL.md
Remove AI writing patterns from English prose. Covers blog posts, technical docs, social copy, release notes, scientific writing. Trigger: deslop, de-AI, make it sound human, remove AI patterns, fix slop, polish, rewrite, sound natural
npx skillsauth add ninehills/skills deslop-enInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Remove announcement phrases. State content directly.
❌ Here's the thing: / The truth is, / Let me be clear / It turns out / I'm going to be honest / Can we talk about / Here's the kicker / Here's where it gets interesting ✅ State the point without preamble.
Kill all -ly words. Softeners, intensifiers, hedges — all of them.
❌ really, just, literally, genuinely, honestly, simply, actually, deeply, truly, fundamentally, inherently, inevitably, interestingly, importantly, crucially, quietly, remarkably, arguably, certainly
Also cut these filler phrases:
❌ At its core / In today's [X] / It's worth noting / It bears mentioning / Notably / At the end of the day / When it comes to / In a world where / The reality is
Every sentence needs a human subject doing something. Inanimate objects don't perform human verbs.
❌ "the complaint becomes a fix" → Someone fixed it. ❌ "a bet lives or dies in days" → Someone kills or ships the project. ❌ "the decision emerges" → Someone decides. ❌ "the culture shifts" → People change behavior. ❌ "the data tells us" → Someone reads the data and concludes. ❌ "the market rewards" → Buyers pay for things.
✅ Name the actor. "The team fixed it that week" beats "the complaint becomes a fix." If no specific person fits, use "you" or "we."
The most common AI tell. Creates false drama by framing everything as a surprising reframe.
❌ "It's not X — it's Y." / "Not because X. Because Y." / "The question isn't X. It's Y." / "It feels like X. It's actually Y." / "stops being X and starts being Y" ✅ State Y directly. "The problem is Y." Drop the negation entirely.
Listing what something is not before revealing what it is.
❌ "Not a X. Not a Y. A Z." / "It wasn't X. It wasn't Y. It was Z." / "Not ten. Not fifty. Five hundred." ✅ State Z directly.
Asking a question nobody was asking, then answering it for dramatic effect.
❌ "The result? Devastating." / "The worst part? Nobody saw it coming." / "What if I told you..." ✅ State it directly: "The result was devastating."
Overuse of the rule-of-three pattern.
❌ "Products impress people; platforms empower them. Products solve problems; platforms create worlds. Products scale linearly; platforms scale exponentially." ✅ Use two items or one. A single tricolon is fine. Back-to-back tricola are pattern recognition failure.
Repeating the same sentence opener multiple times.
❌ "They assume that users will pay... They assume that developers will build... They assume that ecosystems will emerge..." ✅ Vary sentence openings. Combine related points.
Sentence fragments for manufactured emphasis.
❌ "[Noun]. That's it. That's the [thing]." / "He published this. Openly. In a book. As a priest." / "Platforms do." ✅ Use complete sentences. Trust content over presentation.
Self-referential asides that announce structure instead of moving forward.
❌ "In this section, we'll explore..." / "As we'll see..." / "Let me walk you through..." / "The rest of this essay explains..." / "And so we return to where we began." ✅ Delete. Let the essay move without announcing itself.
Replace pompous alternatives to "is" or "are" with the simple copula.
❌ serves as / stands as / marks / represents / constitutes / boasts (as 'has') / features (as 'has') ✅ is / are / has
These add no meaning.
❌ Full stop. / Period. / Let that sink in. / This matters because. / Make no mistake. / Here's why that matters. ✅ Delete.
Phrases that assume the reader needs a teacher.
❌ Let's break this down. / Let's unpack this. / Let's dive in. / Think of it as... / Imagine a world where... ✅ State the information directly.
Tacking "-ing" phrases onto sentences for shallow analysis.
❌ "contributing to the region's rich cultural heritage" / "highlighting its importance" / "underscoring the need" ✅ If the analysis applies to literally any subject, it adds nothing. Delete it or replace with specific evidence.
Using "from X to Y" where no real spectrum exists between X and Y.
❌ "From innovation to implementation to cultural transformation." ✅ Only use "from X to Y" when there's a real, identifiable midpoint on a real scale.
Numbered points disguised as continuous prose.
❌ "The first wall is the absence of a free API... The second wall is the lack of delegated access..." ✅ If a list is genuinely needed, use a list. Don't disguise it as prose paragraphs.
Listing every source that covered the topic to prove it deserves to be written about.
❌ "Her views have been featured in Forbes, TechCrunch, Wired, and The New York Times..." ✅ Mention sources only where they naturally belong in the narrative. Don't recite a press list.
Hiding behind unnamed authorities.
❌ "Experts argue..." / "Many believe..." / "Studies show..." / "It is widely regarded..." / "Observers note..." ✅ Name the source, or don't invoke one at all.
A formulaic challenges-and-future-prospects ending.
❌ "Despite its industrial prosperity, Korattur faces challenges typical of urban areas... With its strategic location and ongoing initiatives, Korattur continues to thrive." ✅ Name specific problems with specific evidence. Don't follow with vague optimism about "ongoing initiatives."
Simulated self-awareness or manufactured sincerity.
❌ "And yes, I'm openly..." / "This is not a rant; it's a diagnosis" / "I promise" / "They exist, I promise" / "creeps in" ✅ Delete.
AI cycles through synonyms to avoid repeating words, even when repetition is clearer.
❌ "Soviet artistic constraints... non-conformist artists... their creativity... state-imposed artistic norms... the artistic aspirations..." ✅ Repeat words when clarity demands it. "The Soviet government told artists what they could and couldn't paint. Yankilevsky painted what he wanted anyway."
Assuming the reader needs a dumbed-down metaphor.
❌ "Think of it as a Swiss Army knife." / "Think of it like a highway system for data." ✅ Explain the concept directly unless the analogy carries real explanatory weight.
Every list item starting with a bolded keyword followed by a colon.
❌
- **SEO:** Traditional methods for improving visibility...✅ Write as prose. If a list is genuinely needed, keep it simple without bold headers and colons.
AI uses em dashes (—) where humans use commas, parentheses, or periods.
❌ More than one em dash per 500 words is a tell. ✅ Use periods and start new sentences. Use commas for asides.
| Avoid | Use | |-------|-----| | serve as / stand as / marks / represents | is / are | | boasts / features (as 'has') | has | | leverage / utilize | use | | harness | use / apply | | streamline | simplify | | navigate (challenges) | handle / address | | unpack | explain / examine | | deep dive | analysis / examination | | delve | examine / look at / explore | | robust | strong / solid / reliable | | paradigm | model / system / approach | | synergy | cooperation / combined effect | | ecosystem | system / field / community | | landscape | situation / field / area | | tapestry | mix / combination / range | | crucial / pivotal / vital | important / key | | profound / indelible / paramount | significant (or delete) | | showcase | show / display | | underscore / highlight | point out / show | | foster / cultivate | encourage / build | | garner | get / receive | | bolster | support / boost | | facilitate | help / enable | | consequently / thus / hence | so | | furthermore / moreover / additionally | also / and | | nonetheless / nevertheless | still / but |
Hard ban (never use):
Before:
Here's the thing: building reliable distributed systems is genuinely hard. It's not about making individual components bulletproof — it's about designing for partial failure from the ground up. Let that sink in. The implications are significant.
After:
Distributed systems break in predictable ways. Network partitions, clock drift, and GC pauses each create failure modes that unit tests can't catch. We found three patterns that helped: timeouts with jitter, circuit breakers, and idempotent writes.
Before:
The FluSight initiative serves as a foundational framework for influenza forecasting in the United States, contributing to public health preparedness and underscoring the importance of collaborative forecasting efforts.
After:
The FluSight initiative coordinates influenza forecasting across dozens of modeling groups in the United States. Since 2013, it has standardized targets, submission formats, and evaluation metrics.
Before:
It's worth noting that these findings have important implications for how we navigate the challenges of forecast ensembling moving forward. Despite these challenges, this work contributes meaningfully to the growing body of literature, highlighting the need for continued evaluation and underscoring the importance of robust benchmarking.
After:
If individual model rankings are unstable across geography and time, ensemble methods that weight models by past performance may not improve on equal-weight approaches.
Before:
In today's rapidly evolving genomic landscape, single-cell RNA sequencing has fundamentally reshaped how we think about cellular heterogeneity. This paradigm shift has far-reaching implications for our understanding of disease.
After:
Single-cell RNA sequencing reveals cell-type-specific expression patterns that bulk methods average out. In tumor samples, this distinction matters: rare resistant subpopulations visible in single-cell data disappear in bulk profiles.
Five dimensions, rate 1-10 each. Revise if below 35/50.
| Dimension | Question | |-----------|----------| | Directness | Statements or announcements? | | Rhythm | Varied or metronomic? | | Trust | Respects reader intelligence? | | Authenticity | Sounds human or AI-generated? | | Density | Anything cuttable remaining? |
deslop-zh:Chinese de-AI writing (Chinese-specific patterns: summary tags, contrast formulas, jargon, punctuation, spacing rules)development
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
tools
UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn/ui MCP for component search and examples.
data-ai
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
tools
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.