CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-slop-cleaner

Run an anti-slop cleanup/refactor/deslop workflow

59

Quality

67%

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 ./plugins/oh-my-codex/skills/ai-slop-cleaner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is a strong, well-structured instruction-only workflow: a clear regression-tests-first procedure with validation gates, a concrete report template, and good single-level organization. Its only real weakness is conciseness — a guidance-alignment section and a duplicated fallback-category list could be trimmed.

DimensionReasoningScore

Conciseness

The body is mostly dense and actionable, but the "GPT-5.6 Guidance Alignment" section restates general principles Claude already knows ("Keep outputs concise and evidence-dense", "Treat newer user instructions as...") and the fallback categories are listed in both step 3 and step 4, so it could be tightened past level 2.

2 / 3

Actionability

Though instruction-only with no code, the guidance is concrete and copy-paste ready: specific detection signals ("quick hacks, temporary workaround, swallowed errors"), an exact pass sequence, and a full report template; per the scoring notes absence of code is not penalized when guidance is this actionable.

3 / 3

Workflow Clarity

The numbered 1–7 procedure is clearly sequenced with explicit validation checkpoints — regression tests first, re-run verification after each pass, and a full quality-gates step (regression/lint/typecheck/scan) — matching the level-3 anchor of clear sequence with explicit validation and feedback loops.

3 / 3

Progressive Disclosure

No bundle files exist, so the skill is self-contained; it is organized into clearly signaled single-level sections (When to Use, Procedure, Output Format, Scenario Examples) with no nested references, which qualifies for level 3 per the simple/well-organized-skills note.

3 / 3

Total

11

/

12

Passed

Description

50%

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 terse and on-domain but stops at a level-2 profile across every dimension: it states what the skill does without an explicit use-when trigger, leans on niche jargon, and could collide with general refactor skills. Adding a trigger clause and more concrete actions would lift it.

Suggestions

Append an explicit trigger clause, e.g. ". Use when the user asks to 'cleanup', 'refactor', or 'deslop' AI-generated code, or when a path feels bloated, repetitive, or over-abstracted." to satisfy completeness at level 3.

Replace or augment the jargon-heavy "anti-slop/deslop" framing with concrete actions users say (e.g. "remove dead code and duplication, trim needless wrappers, reinforce regression tests") to improve specificity and trigger_term_quality.

Sharpen distinctiveness by naming the regression-tests-first, behavior-preserving angle so it does not read as a generic refactor skill.

DimensionReasoningScore

Specificity

Quotes "anti-slop cleanup/refactor/deslop workflow" name the domain and several actions, but stop short of listing multiple concrete actions like the level-3 anchor ("Extract text and tables..., fill forms, merge documents").

2 / 3

Completeness

The description states what ("Run an anti-slop cleanup/refactor/deslop workflow") but has no "Use when..." clause or equivalent trigger, so per the guidelines completeness is capped at 2 (what present, when missing/only implied).

2 / 3

Trigger Term Quality

"cleanup" and "refactor" are natural user terms, but "anti-slop" and "deslop" are niche jargon and common variations (e.g. "remove dead code", "deduplicate") are missing, matching the level-2 anchor of some relevant keywords but missing common variations.

2 / 3

Distinctiveness Conflict Risk

The "anti-slop" niche is somewhat distinctive, but "cleanup/refactor" would overlap with general refactoring and code-quality skills, matching the level-2 anchor of somewhat specific but could still overlap.

2 / 3

Total

8

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Yeachan-Heo/oh-my-codex
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.