deslop
Remove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, and strips defensive code. Use when cleaning up code, simplifying, removing boilerplate, or before committing.
99
100%
Does it follow best practices?
Impact
98%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 is a strong skill description that clearly communicates its purpose, lists specific concrete actions, includes natural trigger terms, and has an explicit 'Use when' clause. It occupies a distinct niche around cleaning up AI-generated code artifacts that differentiates it well from general code quality or formatting skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: remove AI-generated code slop, remove unnecessary comments, remove over-engineering, clean up boilerplate, simplify abstractions, strip defensive code. These are all concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Remove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, and strips defensive code') and when ('Use when cleaning up code, simplifying, removing boilerplate, or before committing') with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'code slop', 'unnecessary comments', 'over-engineering', 'boilerplate', 'simplify', 'cleaning up code', 'before committing'. These cover a good range of how users would naturally describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on removing AI-generated slop and over-engineering from branch diffs. The combination of 'AI-generated code slop', 'branch diff', and 'defensive code' creates a distinct identity unlikely to conflict with general code formatting or linting skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, lean skill that provides concrete commands, a clear workflow with validation checkpoints, and specific patterns to look for. The guardrails section appropriately constrains behavior for a potentially destructive operation. The focus areas list is particularly strong—each bullet is specific and actionable without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. No unnecessary explanations of what slop is or why it's bad—jumps straight to commands, workflow, and focus areas. Bullet points are tight and specific. | 3 / 3 |
Actionability | Provides exact bash commands to run, a concrete list of slop patterns to look for, specific guardrails for safe editing, and a clear output format. The test verification command is copy-paste ready. | 3 / 3 |
Workflow Clarity | Six clearly sequenced steps with an explicit verification step (re-run diff to confirm only slop removed) and a test/type-check validation step. The feedback loop of identify → edit → verify → test is well-defined for this potentially destructive operation. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (Commands, Workflow, Focus Areas, Guardrails, Output) that are easy to scan and navigate. | 3 / 3 |
Total | 12 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- rohitg00/pro-workflow
- Commit
9df6af8
- 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.