CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

unslopify

Audit dead code, stale exports, unused imports, and cleanup candidates. Use when scoped cleanup needs evidence, rollback notes, and repo-native validation.

Quality

83%

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

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.

A lean, well-structured runbook with an exemplary validated workflow (baseline checks, reversible batches, re-validation, stop-on-blocker). The weakest areas are minor redundancy across safety sections and an archive reference tree that nests and duplicates content, which slightly muddies navigation.

Suggestions

Consolidate the overlapping no-evidence-deletion guidance currently spread across Safety, Anti-Patterns, and Gotchas into one section to tighten conciseness.

Define or link the "targeted cleanup lanes" referenced in Workflow step 2 so the cleanup lanes are discoverable without reading the literature bundle.

Flatten references/archive/ to remove the nested references/ subdirectory and its duplicated contract/evals/task-profile files, keeping archived material one level deep.

DimensionReasoningScore

Conciseness

The body is terse and imperative throughout with no explanation of concepts Claude already knows; every section is short. Not 5 because of minor redundancy (the no-evidence-deletion rule repeats across Safety, Anti-Patterns, and Gotchas) and the somewhat padded "Runtime Activation" and "Package Maintenance Gates" meta-sections.

4 / 5

Actionability

Concrete ledger categories, boundary rules, a deliverables spec, and exact gate commands ("<agent-skills-root>/bin/ask skills resolve unslopify --json") give mostly executable guidance. Not 5 because "targeted cleanup lanes" is undefined in the body and the core cleanup steps rely on repo-native commands that are never exemplified; not 3 because the guidance is specific and executable in most sections.

4 / 5

Workflow Clarity

The six-step Workflow has an explicit baseline validation step (step 3), re-validation after each reversible batch (step 5), and a Failure mode section with stop-and-report blockers. This destructive/batch skill includes validation checkpoints and feedback loops, matching the top anchor exactly.

5 / 5

Progressive Disclosure

Body pointers ("references/discovery-interview.md", the two "references/literature/..." lens files) resolve to real files one level deep and are clearly signaled. Not 5 because "references/archive/" contains a nested duplicated "references/" subdirectory (2-level nesting risk), and contract/evals/task-profile are only pointed at by directory rather than by file.

4 / 5

Total

17

/

20

Passed

Description

80%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 description: third-person, concrete, and explicit about both what it does and when to use it. The main gap is that the "Use when" clause describes conditions rather than natural user trigger phrases, which slightly weakens trigger-term quality.

DimensionReasoningScore

Specificity

"Audit dead code, stale exports, unused imports, and cleanup candidates" lists multiple specific concrete actions covering the cleanup domain comprehensively. Not 4 because there is no material gap in the action list.

5 / 5

Completeness

The "what" is concrete and an explicit "Use when..." clause is present, but the "when" is condition-based ("when scoped cleanup needs evidence, rollback notes, and repo-native validation") rather than concrete user trigger phrases. Not 5 because the trigger phrasing could be more explicit; not 3 because trigger guidance is explicit, not merely implied.

4 / 5

Trigger Term Quality

"dead code", "unused imports", "cleanup" are natural phrases users would say, but common synonyms like "code cleanup", "technical debt", or "unused variables/functions" are missing. Not 5 because coverage lacks those variations; clearly above 3 since several natural terms are present.

4 / 5

Distinctiveness Conflict Risk

"Audit dead code, stale exports, unused imports" carves a distinct evidence-first cleanup niche with minimal conflict risk. Not 5 because "cleanup candidates" is broad enough to overlap with general code-review or refactoring skills.

4 / 5

Total

17

/

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

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

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

Warning

Total

14

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/agent-ops/unslopify/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.