CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remove-ai-slops

Removes AI-generated code smells from branch changes or an explicit file list behind regression tests, including junk tests (prose pins, source greps, copied inventories, mock echoes), each proven by its class's rule before a cut. Use when the user asks to clean up, deslop, remove AI-slop patterns, or prune tests from recent changes.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%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.

A rigorous, highly actionable cleanup procedure with an exceptional validation workflow (behavior locked by tests, gates, revert loops, escalation), undermined by monolithic structure and internal duplication. The Phase 3/Phase 4 repetition and the absence of any bundle files keep conciseness and progressive disclosure at mid-pack despite the operational strength of the rest.

Suggestions

Split the ~60-line category-9 test rules and the Phase 4 worker prompt template into references/ files (e.g., references/testing-rules.md, references/worker-prompt.md) and link to them from the body, so the Categories section stays scannable and the skill practices the progressive disclosure it would demand of reviewed code.

State the safest-to-riskiest order rule and the deletion ladder once (Phase 3) and have the Phase 4 worker prompt reference 'the ladder and order rule defined above' instead of restating them verbatim, cutting meaningful duplication.

Break the Phase 4b paragraph into a short list (one bullet per proof protocol: mutation invocation, serialization rule, restore rule, failure fallback) so each rule is individually readable rather than packed into one run-on sentence.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive rather than explanatory — it does not teach concepts Claude already knows — but it is noticeably repetitive and could be tightened: the safest-to-riskiest order rule appears twice verbatim (Phase 3 and again in the Phase 4 task prompt), the deletion ladder is restated inside the worker prompt after being fully defined in Phase 3, and paragraphs like the Phase 4b proof protocol are single-sentence walls that pack several rules together. This lands between 'efficient with minor trims' (4) and 'noticeably verbose' (2), matching 'mostly efficient but includes some unnecessary duplication that could be tightened' (3).

3 / 5

Actionability

Guidance is largely executable: the `git diff $(git merge-base main HEAD)..HEAD --name-only` scope command, the `awk` LOC measure, `bun run .../check-test-junk.ts`, the full `mutation-proof.ts` flag syntax including quoting caveats, a copy-paste task() invocation template, and a complete report format. Not 5: key paths are unresolved placeholders ('<programming skill dir>', 'programming/references/testing/junk-classes.md') that depend on an external skill not bundled here, so the reader cannot execute them as-is from this skill alone.

4 / 5

Workflow Clarity

Phases 0-6 are clearly sequenced with explicit validation checkpoints and feedback loops for what is a destructive batch operation: regression tests must be green before any removal (Phase 2), five named quality gates with N/A reporting (Phase 5), a revert-and-re-run loop on failure with a three-strike escalation to the user (Phase 6), and serial mutation proofs with byte-exact restore (Phase 4b). This matches the top anchor: clear sequence, explicit validation, error-recovery loops, and checklists.

5 / 5

Progressive Disclosure

Section headers are clear and well-ordered (Categories, Quality Gates, Process, Output Format, Anti-Patterns), but this is a ~350-line monolith with no bundle files at all — the detailed category-9 test rules, the worker prompt template, and the report template are all inlined when they could live in references/, and the only file pointers (programming skill scripts and testing tables) point outside the bundle. This matches 'some structure but could be better organized; content that should be separate is inline' rather than 4, since no content is actually split out.

3 / 5

Total

15

/

20

Passed

Description

88%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.

A strong third-person description that concretely states what is removed (code smells plus four named junk-test classes), the safety mechanism (regression tests, proof before cut), and both input scopes, followed by an explicit 'Use when...' clause with natural trigger phrases. The only soft spot is trigger-term breadth, which covers the core phrasings well but misses a few common synonyms.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions: 'Removes AI-generated code smells from branch changes or an explicit file list behind regression tests, including junk tests (prose pins, source greps, copied inventories, mock echoes), each proven by its class's rule before a cut.' It names the two input scopes, four specific junk-test classes, and the proof-before-cut mechanism, matching the comprehensive-coverage anchor. Not below 4: coverage of what gets removed and how safety is enforced is explicit, not just 1-2 generic actions.

5 / 5

Completeness

Both halves are explicit: 'what' is 'Removes AI-generated code smells... including junk tests... each proven by its class's rule before a cut', and 'when' is the 'Use when the user asks to clean up, deslop, remove AI-slop patterns, or prune tests' clause with concrete trigger phrases. This matches the anchor for clearly and explicitly answering both what AND when.

5 / 5

Trigger Term Quality

'Use when the user asks to clean up, deslop, remove AI-slop patterns, or prune tests from recent changes' gives four natural phrases a user would plausibly say, including the distinctive 'deslop'. Not 5: a few natural variants are missing (e.g., 'tidy up the code', 'remove boilerplate', 'cleanup pass'), and no file-extension or synonym-style anchors are present; not 3: coverage goes well beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The niche ('AI slop removal behind regression tests', 'deslop', 'AI-slop patterns', 'prune tests from recent changes') is distinct with dedicated trigger words unlikely to fire for general refactoring or review skills. Not 5: 'clean up... recent changes' has minor overlap risk with generic code-cleanup/lint-fixing skills; not 3: the junk-test taxonomy and deslop triggers carve out a clear specialized slot.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing, 2 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

code-yeongyu/oh-my-openagent

Path

packages/shared-skills/skills/remove-ai-slops/SKILL.md

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.