CtrlK
BlogDocsLog inGet started
Tessl Logo

dead-code-cleanup

Use when the user asks about unused code, cleanup, deleting files or exports, refactoring old areas, reducing bundle size, code hygiene, technical debt, or maintenance in a Repowise-indexed repository.

72

Quality

88%

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

The canonical home for this skill is dead-code-cleanup in repowise-dev/repowise

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 tight, highly actionable skill body that gives concrete tool calls, parameters, a safety checklist, and a deletion order without any wasted tokens — exemplary for a tool-integration skill.

DimensionReasoningScore

Conciseness

Lean and efficient — every line is actionable parameter or command guidance with no padding or explanation of concepts Claude already knows; assumes Claude's competence.

5 / 5

Actionability

Fully executable guidance with concrete function names and specific parameters with values (e.g. get_dead_code(safe_only=true, kind="unused_export"), get_risk(targets=[...])) covering the common cases.

5 / 5

Workflow Clarity

Clear sequence with explicit validation checkpoints for the destructive operation — confirm with user, call get_risk to double-check dependents, flag recent-activity false positives, then a defined safe deletion order.

5 / 5

Progressive Disclosure

A single-purpose skill under 50 lines with well-organized section headers and no need for external references, satisfying the simple-skill exception.

5 / 5

Total

20

/

20

Passed

Description

77%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 trigger-rich description that excels at when-to-use guidance and distinctiveness, but it lacks an explicit statement of what the skill does, relying on implied verbs within the trigger list.

Suggestions

Add a leading 'what' clause before 'Use when...', e.g. 'Identifies and removes dead code via Repowise graph analysis.'

State the core capability (dead-code detection/deletion) explicitly so the description answers both what and when.

DimensionReasoningScore

Specificity

Names several concrete actions (cleanup, deleting files or exports, refactoring, reducing bundle size) but presents them as trigger conditions rather than a crisp statement of what the skill does, leaving minor gaps.

4 / 5

Completeness

The 'when' is explicitly and thoroughly answered, but the 'what' (the skill's actual function) is only weakly implied by 'cleanup'/'deleting' rather than stated, which caps completeness.

3 / 5

Trigger Term Quality

Comprehensive natural keywords users would actually say — 'unused code', 'cleanup', 'deleting files', 'refactoring', 'bundle size', 'technical debt', 'maintenance' — with good synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Scoped to a 'Repowise-indexed repository' with distinct triggers, giving it a clear niche and minimal conflict risk with other skills.

5 / 5

Total

17

/

20

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
repowise-dev/repowise
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.