deslop
Remove AI-generated code slop from the current branch. Use after writing code to clean up unnecessary comments, defensive checks, and inconsistent style.
Overall
score
75%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description effectively communicates its purpose and includes an explicit 'Use when' clause, making it complete. However, it could benefit from more specific concrete actions and additional natural trigger terms that users might actually say when they need this functionality.
Suggestions
Add more natural trigger terms users might say, such as 'clean up code', 'refactor AI code', 'remove boilerplate', or 'fix generated code'
List more specific concrete actions like 'removes TODO comments, simplifies error handling, standardizes naming conventions' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('AI-generated code slop') and some actions ('clean up unnecessary comments, defensive checks, and inconsistent style'), but doesn't list comprehensive concrete actions like specific refactoring operations or file types handled. | 2 / 3 |
Completeness | Clearly answers both what ('Remove AI-generated code slop... clean up unnecessary comments, defensive checks, and inconsistent style') and when ('Use after writing code') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'code slop', 'unnecessary comments', 'defensive checks', but misses common variations users might say like 'clean up code', 'remove boilerplate', 'fix AI code', 'refactor', or 'code cleanup'. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on AI-generated code cleanup with distinct triggers ('code slop', 'AI-generated'); unlikely to conflict with general code formatting or linting skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a concise, well-scoped skill that clearly defines what constitutes 'AI slop' to remove. However, it would benefit from concrete examples showing before/after code patterns and explicit workflow steps including how to check the diff and validate changes don't break the codebase.
Suggestions
Add 1-2 concrete before/after code examples showing what 'extra comments' or 'abnormal defensive checks' look like versus acceptable code
Include the specific git command to check diff against main (e.g., `git diff main...HEAD`)
Add a validation step: suggest running tests or type-checking after removing code to ensure functionality is preserved
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, listing only what Claude needs to know without explaining basic concepts. Every line serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides clear criteria for what to remove (comments, defensive checks, casts, style inconsistencies) but lacks concrete examples of before/after code or specific commands for checking the diff against main. | 2 / 3 |
Workflow Clarity | The workflow is implicit (check diff → identify slop → remove → report) but not explicitly sequenced. Missing validation steps - no guidance on verifying changes don't break functionality before committing. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is appropriately self-contained with clear organization. No need for external references given the scope. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
62%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 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 10 / 16 Passed | |
- 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.