Skip to content
Back to skills

Unslop

ASecurity

Strip AI boilerplate, fluff words, and redundant single-use wrappers from code, text, analyses, and designs. Trigger via /unslop or when cleaning outputs.

  • 2 stars
  • 0 votes
  • 2 copies
  • 5 views
  • Added September 3, 2026
ai-agentstypescriptrustgogitapidatabasesecurity

Works with

  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 3, 2026

npx -y skills add ksprashu/agent-skill-forge --skill unslop --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Unslop?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Unslop
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/ksprashu-unslop/badge)](https://www.skillsdirectory.com/skills/ksprashu-unslop)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: unslop
description: Strip AI boilerplate, fluff words, and redundant single-use wrappers from code, text, analyses, and designs. Trigger via /unslop or when cleaning outputs.
---

# Unslop: Universal Anti-Bloat & Simplification Engine

Strip AI tells, defensive boilerplate, sterile prose, and unnecessary complexity across code, prose, system analyses, and visual designs.

---

## 🎯 Goal
Eliminate low-signal clutter while preserving 100% of functional behavior, meaning, and accuracy. Subtract before you add.

---

## πŸ“‹ Step-by-Step Workflow

1. **Detect AI Bloat**:
   * **In Code**: Paranoid internal type-checks, single-use wrapper classes, verbose restatement comments, over-nested conditionals.
   * **In Text / Prose**: Buzzwords (*delve*, *testament*, *tapestry*, *demystify*, *furthermore*), em-dashes (`β€”`), bolding the first 3 words of every bullet.
   * **In Analysis / Specs**: Fluffy pseudo-academic introductions, repetitive summaries, speculation without data.
   * **In Diagrams / UI**: Superfluous borders, excessive container nesting, gratuitous decorative shapes.
2. **Subtract First**: Delete or inline unnecessary abstractions, wrappers, and preamble before editing core logic.
3. **Flatten & Tighten**: Replace nested constructs with early returns; replace wordy sentences with direct statements.
4. **Verify Integrity**: Guarantee code tests pass, specs retain exact requirements, and prose retains factual substance.

---

## πŸ’‘ Concrete Examples Across Domains

### 1. Code Simplification
**Before (AI Slop):**
```typescript
class StringFormatterService {
  public static sanitizeAndTrim(input: string | null | undefined): string {
    if (input === null || input === undefined) return '';
    return input.trim().toLowerCase();
  }
}

export function processUsername(user: { name: string }) {
  const formatted = StringFormatterService.sanitizeAndTrim(user.name);
  return `user_${formatted}`;
}
```
**After (Unslopped):**
```typescript
export function processUsername(user: { name: string }) {
  return `user_${(user.name ?? '').trim().toLowerCase()}`;
}
```

### 2. Prose & Article Simplification
**Before (AI Slop):**
```markdown
In today's fast-paced digital landscape, it's crucial to delve into the tapestry of microservices. Furthermore, this innovative approach stands as a testament to modern architectural excellence.
```
**After (Unslopped):**
```markdown
Microservices separate system responsibilities into independently deployable units, reducing deployment blast radiuses.
```

### 3. Architecture & Analysis Simplification
**Before (AI Slop):**
```markdown
## Executive Strategic Overview
In this comprehensive analysis, we embark on a thorough exploration of database latency paradigms to unlock maximum synergies across our operational ecosystem...
```
**After (Unslopped):**
```markdown
## Problem & Metrics
Database p95 query latency currently spikes to 420ms under 1,000 req/s due to unindexed foreign keys on `orders.user_id`.
```

---

## 🚫 Hard Constraints

*   **NEVER** change public API signatures or return types.
*   **NEVER** delete security/validation checks at untrusted boundaries (HTTP inputs, user forms, file uploads).
*   **NEVER** remove comments explaining hardware quirks, non-obvious business rules, or concurrency locks.
*   **NEVER** alter the factual meaning or constraints of a specification or analysis.

Files in this skill

  • README.md810 B
  • SKILL.md3.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…