ai-slop-cleaner

Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

Quality

55%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/ai-slop-cleaner/SKILL.md

Quality

Discovery

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a specific problem domain (AI-generated code quality) and hints at a methodology, but fails to provide concrete actions or explicit trigger guidance. It lacks the 'Use when...' clause critical for skill selection and uses somewhat niche jargon ('slop') that users may not naturally use.

Suggestions

Add a 'Use when...' clause with trigger terms like 'clean up AI code', 'remove code bloat', 'simplify generated code', 'refactor AI output'

List specific concrete actions such as 'removes dead code, simplifies over-engineered patterns, eliminates redundant comments, consolidates duplicate logic'

Include natural language variations users might say: 'messy code', 'bloated code', 'over-complicated', 'needs cleanup'

Dimension	Reasoning	Score
Specificity	Names the domain ('AI-generated code slop') and describes a general approach ('regression-safe, deletion-first workflow', 'reviewer-only mode'), but lacks specific concrete actions like 'remove unused imports', 'simplify nested conditionals', or 'eliminate dead code'.	2 / 3
Completeness	Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The rubric caps completeness at 2 for missing this, and the 'what' is also weak.	1 / 3
Trigger Term Quality	Includes some relevant terms like 'AI-generated code', 'slop', and 'deletion-first', but misses common variations users might say like 'clean up code', 'refactor', 'remove bloat', 'simplify', or 'code review'.	2 / 3
Distinctiveness Conflict Risk	The term 'AI-generated code slop' and 'deletion-first workflow' provide some distinctiveness, but 'clean code' could overlap with general refactoring or code review skills. The niche is somewhat defined but not sharply bounded.	2 / 3
	Total	7 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill with strong actionability and workflow clarity. The multi-pass cleanup workflow with explicit validation checkpoints is particularly well-designed. The main weakness is moderate verbosity—some sections repeat concepts and could be tightened without losing clarity.

Suggestions

Consolidate 'When to Use' and 'When Not to Use' into a single, tighter section or merge trigger conditions into the opening paragraph

Consider extracting the detailed 'Review Mode' and 'Ralph Integration' sections into separate reference files if this skill grows

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundancy—the 'When to Use' and 'When Not to Use' sections overlap with information elsewhere, and some bullet points could be tightened. The workflow steps are clear but slightly verbose.	2 / 3
Actionability	Provides concrete, specific guidance with clear workflow steps, explicit pass ordering (dead code → duplicates → naming → tests), specific smell classifications, and concrete usage examples. The quality gates and report structure are actionable.	3 / 3
Workflow Clarity	Excellent multi-step workflow with explicit sequencing, validation checkpoints ('Re-run targeted verification after each pass'), feedback loops ('If a gate fails, fix the issue or back out'), and clear pass-by-pass structure with verification requirements.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but it's a monolithic document with no references to external files for detailed content. The Ralph Integration and Review Mode sections could potentially be split out for better navigation in a larger skill ecosystem.	2 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: Yeachan-Heo/oh-my-claudecode
Commit: 48ffaac

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.