CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

codebase-refactoring

Three-part workflow to improve overall codebase health with jscpd — find and fix duplicated code, find and remove or refactor dead code, then find and simplify the largest/most complex files. Starts from --dashboard/--health to prioritize and ends by re-measuring the score.

Quality

84%

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

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

The body is highly actionable with executable commands and a clearly sequenced, validated workflow including feedback loops for its destructive dead-code step; it is well-structured with one well-signaled external reference.

DimensionReasoningScore

Conciseness

Largely lean and tool-specific (jscpd flags, health-score semantics, dead-code categories are knowledge Claude does not already have), but the rationale paragraphs for the default ordering and some Tips entries could be trimmed slightly.

4 / 5

Actionability

Fully executable, copy-paste-ready `npx jscpd` commands with specific flags, worked example outputs, a category→fix table, and concrete per-step refactoring strategies covering the common cases.

5 / 5

Workflow Clarity

Clear 0→4 sequence with explicit validation checkpoints (re-run jscpd, run the project's test suite and build after dead-code batches) and feedback loops (dead-code cascade re-runs, revisit a step if a dimension regressed) for destructive/batch operations.

5 / 5

Progressive Disclosure

Well-organized step-by-step sections with one clearly signaled, one-level-deep reference to the sibling dry-refactoring skill; the bulk is appropriately inline but only a single external reference keeps it just short of the clearest split.

4 / 5

Total

18

/

20

Passed

Description

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

The description is specific, concrete, and clearly niche, but it lacks an explicit 'Use when...' trigger clause, capping completeness at 3 despite strong specificity and distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when asked to clean up, refactor, or pay down tech debt in a codebase rather than fix one specific bug.'

Include natural synonyms ('clean up', 'tech debt', 'pay down') in the description, not just the body, to lift trigger_term_quality.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('find and fix duplicated code', 'find and remove or refactor dead code', 'find and simplify the largest/most complex files') plus concrete tool entry points ('--dashboard/--health', 're-measuring the score'), giving comprehensive coverage.

5 / 5

Completeness

A clear and specific 'what' is present, but there is no explicit 'Use when...' trigger clause, so per the judging guideline a missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural-term coverage ('duplicated code', 'dead code', 'complex files', 'refactor', 'codebase health') but misses common synonyms a user might say ('clean up', 'tech debt', 'pay down') that appear only in the body, not the description.

4 / 5

Distinctiveness Conflict Risk

Scoped to a jscpd-based codebase-health workflow across duplication, dead code, and complexity — a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

kucherenko/jscpd

Path

skills/codebase-refactoring/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.