# Deslopify

> >-

- **Type:** Skill
- **Install:** `agentstack add skill-kriscard-skills-deslopify`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [kriscard](https://agentstack.voostack.com/s/kriscard)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [kriscard](https://github.com/kriscard)
- **Source:** https://github.com/kriscard/Skills/tree/main/skills/productivity/deslopify

## Install

```sh
agentstack add skill-kriscard-skills-deslopify
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Deslopify

Strip the patterns that mark text as AI-generated. Preserve all factual
content and the author's intended tone — change the delivery, not the message.

## The Slop Patterns

Scan for these before rewriting. The more you find, the more aggressive the
edit.

**Opening filler** (cut 80% of the time — start with the actual point):
- "In today's fast-paced world..."
- "It's important to note that..."
- "As we navigate the complexities of..."

**Hollow transitions**:
- "Furthermore,", "Moreover,", "Additionally," — usually just "Also," or delete
- "In conclusion," — end without announcing you're ending
- "It's worth noting that..." — just say the thing

**Emphasis inflation**:
- "Importantly,", "Crucially,", "Significantly," — earn emphasis with content
- "It goes without saying..." — then don't say it

**AI vocabulary** (replace with the plain word):
- "leverage" → "use"
- "utilize" → "use"
- "delve into" → "look at" or "explore"
- "in terms of" → restructure the sentence
- "moving forward" → cut
- "at the end of the day" → cut

**Excessive hedging**:
- "It seems that", "One might argue", "It could be said" — commit to the claim
  or cut it

**Nominalization** (convert to verb):
- "make a decision" → "decide"
- "provide assistance" → "help"
- "conduct an analysis" → "analyze"
- "have a discussion" → "discuss"

**Bullet lists where prose would be clearer**: not every list needs to be a
list. Three related sentences often read better as a paragraph.

**En-dash used as em-dash**: `–` should be `—` (or just a comma)

## What Good Looks Like

- Short sentences land hard. Longer ones build context. Vary them.
- Active voice: "We shipped X" not "X was shipped by the team"
- Specific beats general: "increased conversion by 18%" not "improved results"
- The first sentence is the most important — if it's filler, cut it

## Process

1. Read the full text
2. Identify which slop patterns appear
3. Rewrite: cut the filler, verb-ify the nominalizations, activate the passive
4. Present the revised version
5. Add a 2–3 line note on the key changes made (not a list of every single fix)

## Code Comment Mode

When the input is a diff (or the user asks to remove AI comments from code):

**What to remove:**
- Comments restating what code clearly does (`// increment counter` above `counter++`)
- Overly verbose explanations of obvious code
- Generic placeholders (`// TODO: implement`, `// Handle error`)
- Comments with AI phrasing ("This function...", "The following code...")
- Inline docs inconsistent with the file's existing comment style

**What to keep:**
- Doc comments for public APIs (JSDoc, docstrings)
- Comments explaining WHY (business logic, workarounds, edge cases)
- Comments matching the file's existing style and density
- License headers and attribution

**Hard constraint: DO NOT modify any code.** Only remove comments. No refactoring, no style changes, no removing try/catch or null checks. If you spot code slop, note it in the summary but leave it.

Output: report 1–3 sentences on what was removed and any code issues noticed but left unchanged.

## Hard Rules (Prose Mode)

- Never change factual content — only how it's expressed
- Never add new claims or examples not in the original
- Preserve the author's stance and intended audience
- If the text is mostly fine, say so — don't invent problems to fix

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [kriscard](https://github.com/kriscard)
- **Source:** [kriscard/Skills](https://github.com/kriscard/Skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-kriscard-skills-deslopify
- Seller: https://agentstack.voostack.com/s/kriscard
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.