Index of every page on this site: llms.txt
All skills
Run it yourself

Remove AI-generated "slop" from codebases by deleting redundant comments and unused code, tightening formatting, and normalizing styling patterns (e.g., Tailwind class consistency, Nuxt UI color tokens). Use when a user asks to clean up code, remove unnecessary comments, reduce unused imports/variables, or align Tailwind/Nuxt UI conventions.

Use this Skill: https://skilld.dev/gh/onmax/claude-config/unslop

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈88 tokens for metadata: the name and description. ≈896 when used: this file.

Description uses 4.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈352 characters, or 4.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Unslop

Overview

Eliminate low-signal artifacts from AI-generated code while preserving behavior and intent.

Workflow

  1. Triage the files

    • Scan each file for redundancy, dead code, and style inconsistencies.
    • Identify the UI framework (Vue/Nuxt) and styling system (Tailwind, Nuxt UI, plain CSS).
  2. Remove redundant commentary

    • Delete comments that restate the obvious (function names, prop names, component names).
    • Remove template comments in .vue/HTML/JSX unless they explain non-obvious UX or business logic.
    • Drop TODOs that add no actionable information (e.g., "TODO: add logic").
  3. Delete unused code paths

    • Remove unused imports, variables, props, computed values, watchers, and helpers.
    • Delete commented-out code blocks unless the user asks to keep them.
    • Prune branches that are never reached or are placeholders.
  4. Normalize styling conventions

    • Consolidate duplicated Tailwind utilities; prefer size-* over w-* h-* when equal.
    • Align class order and grouping with nearby components.
    • In Nuxt UI, prefer semantic tokens (e.g., color-success) over raw color classes.
  5. Validate output

    • Confirm behavior and UI output remain unchanged except for cleanup.
    • Keep any "why" commentary that preserves intent or constraints.

Decision Checklist

  • Is the comment telling me why? Keep.
  • Is the comment just paraphrasing code? Remove.
  • Is this code referenced anywhere? If not, delete it.
  • Would removing this change behavior or test expectations? If yes, keep or re-evaluate.

Comment Removal Heuristics

  • Remove: "Handle click", "Render header", "Fetch user" when the code is explicit.
  • Keep: "Workaround for Safari focus bug", "Required by backend contract", "Do not reorder due to animation timing".
  • Shorten: Replace a paragraph with a single line explaining the non-obvious constraint.

Tailwind & UI Normalization

  • Replace paired width/height with size utilities:
    • w-10 h-10 → size-10
    • w-6 h-6 → size-6
  • Keep consistent axis usage:
    • Use px-* + py-* or p-* consistently within the same component.
  • Favor semantic UI tokens in Nuxt UI:
    • color-green-500 dark:color-green-400 → color-success
    • Align with variant/color props when available.

File-Type Guidance

Vue/Nuxt (.vue)

  • Remove HTML comments inside templates unless they explain layout constraints.
  • Drop unused defineProps, defineEmits, or computed properties.
  • Remove unused ref/computed imports from Vue.

TypeScript/JavaScript

  • Remove unused imports and variables; collapse trivial one-use helpers.
  • Prefer direct inlining when helpers only wrap a single line.

CSS

  • Remove unused classes if not referenced in templates/components.
  • Consolidate duplicated declarations.

Output Expectations

  • Provide a clean diff that focuses solely on removal/normalization.
  • Avoid unrelated refactors or renames.
  • If behavior might change, explain the risk and avoid the change.

Examples

  • "Remove all useless comments in these components and trim unused imports."
  • "Clean up this Vue file: remove template comments and align Tailwind classes."
  • "Normalize Nuxt UI button colors to semantic tokens."
  • "Delete dead code and placeholders, but keep any workaround comments."

Guardrails

  • Keep comments that encode constraints, historical context, or known bugs.
  • Preserve references to tickets/issues if they explain a workaround.
  • Do not change runtime behavior, data flow, or UI output beyond cleanup.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The unslop skill is a code maintenance utility that removes redundant comments, unused code, and normalizes CSS styling. It does not contain any malicious patterns or security risks.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 0a85622. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated 9 months ago

README badge

README badge for onmax/claude-config/unslop