CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-slop-cleaner

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

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ai-slop-cleaner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

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

The content is a well-structured, actionable, and concise workflow for an instruction-only cleanup skill, with explicit validation feedback loops that satisfy the destructive-operation bar. The only notable gap is the inlined UI/design checklist, which could be externalized for cleaner progressive disclosure.

Suggestions

Consider moving the UI/Design Reviewer Checklist into a dedicated reference file (e.g. references/ui-design-checklist.md) and linking to it from the Workflow section to tighten the main body.

Add one or two concrete example verification commands or a small example report template to raise actionability from 4 to 5.

Tighten the slight overlap between 'Scoped File-List Usage' and 'Ralph Integration' to reduce redundancy and push conciseness toward 5.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with no padded conceptual explanations; a few minor trims remain (some self-referential posture lines and slight overlap between the Scoped File-List and Ralph Integration sections), keeping it just below 5.

4 / 5

Actionability

As an instruction-only skill it gives concrete, specific guidance (smell taxonomy, numbered passes, quality gates, report fields, review checklist) with only minor gaps; it stops short of copy-paste-ready commands, which is legitimate since the project toolchain is unknown.

4 / 5

Workflow Clarity

The six-step workflow is clearly sequenced with explicit validation checkpoints and feedback loops ('Re-run targeted verification after each pass', gate-failure handling), satisfying the destructive-operation validation requirement that would otherwise cap this dimension.

5 / 5

Progressive Disclosure

Structure is clean and well-signaled across sections with no external bundle files needed, but the inlined UI/Design Reviewer Checklist is a sizable tangential block that could plausibly live in its own reference, leaving a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

66%Weight 40%Scale 1-5

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 is specific and has a fairly distinct niche with natural trigger phrasing, but it lacks an explicit 'Use when...' clause, which caps completeness. Adding concrete invocation triggers would push it toward the top anchors.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user says deslop/anti-slop/AI slop or asks to clean up bloated, repetitive, or over-abstracted code without changing behavior.'

Surface natural trigger synonyms ('deslop', 'anti-slop', 'cleanup') directly in the description rather than only in the body.

Optionally enumerate a couple more concrete actions (remove dead code, consolidate duplication, strip needless wrappers) to raise specificity toward 5.

DimensionReasoningScore

Specificity

Names the domain ('AI-generated code slop') plus several concrete workflow traits ('regression-safe, deletion-first workflow', 'reviewer-only mode'); not a 5 because it does not enumerate multiple discrete verbs like the top anchor.

4 / 5

Completeness

The 'what' is clear (clean AI slop via a regression-safe deletion-first workflow with a reviewer-only mode), but there is no explicit 'Use when...' clause, so per the rubric cap completeness is held at 3.

3 / 5

Trigger Term Quality

'AI slop' and 'code slop' are natural user phrases, but common invocation synonyms like 'deslop', 'anti-slop', or 'cleanup' appear only in the body, not the description, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

The 'AI-generated code slop' niche plus 'deletion-first'/'reviewer-only' qualifiers distinguish it from most skills, with only minor overlap risk against a generic code-cleanup or refactor skill.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Yeachan-Heo/oh-my-claudecode
Reviewed

Table of Contents

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.