Name: ai-slop-cleaner
Author: zereight

Imported from zereight/gitlab-mcp (.github/skills/ai-slop-cleaner/SKILL.md). Install upstream with npx skills add zereight/gitlab-mcp --skill ai-slop-cleaner. Copyright stays with the author.

AI Slop Cleaner

Clean AI-generated code slop without changing behavior. Deletion-first workflow with regression safety.

When to Use

Code that works but feels bloated, repetitive, or over-abstracted
Duplicate logic, dead code, wrapper layers, boundary leaks
--review for reviewer-only mode (no changes, just findings)

When NOT to Use

New feature build or product change
Broad redesign
Behavior is unclear and untestable

Principles

Preserve behavior unless explicitly asked for changes
Delete before refactoring — removal is safest
Scope-bounded: only clean what was specified
Regression-safe: verify tests pass after every change

Slop Signals

Unnecessary wrapper functions
Duplicated logic across files
Over-abstracted single-use helpers
Dead code / unreachable branches
Excessive comments restating obvious code
Premature abstractions (used only once)

Workflow

Identify target files/scope
Run existing tests (baseline)
Apply deletions first (dead code, unused imports)
Simplify remaining code (reduce nesting, merge duplicates)
Re-run tests after each change
Report what was cleaned and verification results

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install ai-slop-cleaner and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "zereight-gitlab-mcp-ai-slop-cleaner", "kind": "skill", "name": "ai-slop-cleaner", "description": "Clean AI-generated code slop with regression-safe workflow. Activate when user says: deslop, anti-slop, AI slop, cleanup slop, clean up this code, remove bloat.", "publisher": "zereight", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Clean AI-generated code slop with regression-safe workflow. Activate when user says: deslop, anti-slop, AI slop, cleanup slop, clean up this code, remove bloat." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/zereight/gitlab-mcp", "path": ".github/skills/ai-slop-cleaner/SKILL.md", "ref": "HEAD", "url": "https://github.com/zereight/gitlab-mcp/blob/HEAD/.github/skills/ai-slop-cleaner/SKILL.md", "key": "zereight/gitlab-mcp/.github/skills/ai-slop-cleaner/SKILL.md" } }, "instructions": "# AI Slop Cleaner\n\nClean AI-generated code slop without changing behavior. Deletion-first workflow with regression safety.\n\n## When to Use\n- Code that works but feels bloated, repetitive, or over-abstracted\n- Duplicate logic, dead code, wrapper layers, boundary leaks\n- `--review` for reviewer-only mode (no changes, just findings)\n\n## When NOT to Use\n- New feature build or product change\n- Broad redesign\n- Behavior is unclear and untestable\n\n## Principles\n- Preserve behavior unless explicitly asked for changes\n- Delete before refactoring — removal is safest\n- Scope-bounded: only clean what was ", "cost": { "context_tokens": 295 } }

ai-slop-cleaner

About

AI Slop Cleaner

When to Use

When NOT to Use

Principles

Slop Signals

Workflow

Use it

Install ai-slop-cleaner and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews