CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-health

Use when the user asks about code health, code quality, complexity, technical debt, which files are risky or hard to maintain, what to refactor next, untested hotspots, or coverage gaps in a Repowise-indexed codebase (.repowise/ directory exists). Also use to get a before/after health read when planning or finishing a refactor.

Quality

90%

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

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

An exemplary instruction-only skill body: dense with executable tool calls and commands, tight prose, and explicit verification and error-recovery checkpoints. The only soft spot is that its workflow is presented as situation-indexed guidance rather than a single ordered sequence.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it lists markers ("McCabe complexity, deep nesting, brain methods, class cohesion (LCOM4), god classes, clone detection") without explaining them and never teaches background concepts; only trivially trimmable redundancy remains ("Zero LLM calls; pure local analysis" vs "no LLM needed").

5 / 5

Actionability

Fully executable, copy-paste-ready guidance with literal arguments: get_health(targets=["src/x.py", "src/y.py"]), get_health(fix_id=...), repowise coverage add cov.lcov, repowise health --recompute, and /repowise:init, plus exact include-flag values.

5 / 5

Workflow Clarity

Mode selection is clearly disambiguated and the results-usage list includes genuine checkpoints ("Check unresolved before calling a file clean", "Before editing a flagged file → cross-check get_risk") and error-recovery paths (not_indexed → repowise update; no repository → /repowise:init), but the guidance is organized as parallel situational playbooks rather than one strictly sequenced workflow.

4 / 5

Progressive Disclosure

No bundle files exist, and the ~58-line body is appropriately self-contained: it inlines nothing that belongs in a separate file and is organized into clear, navigable sections (modes, include flags, results usage, CLI equivalents, error handling), fitting the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

82%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 with explicit, richly specific trigger guidance and a concrete scope marker. Its main weakness is that the capability side is expressed as a catalogue of user questions rather than a direct statement of what the skill does or returns.

DimensionReasoningScore

Specificity

Enumerates many concrete capability areas — "code health, code quality, complexity, technical debt, which files are risky or hard to maintain, what to refactor next, untested hotspots, or coverage gaps" plus "a before/after health read" — but they are phrased as user questions rather than explicit action verbs, and the actual mechanism (per-file 1–10 scoring) is never stated.

4 / 5

Completeness

The 'when' is explicit and highly specific ("Use when the user asks about...", "Also use to get a before/after health read when planning or finishing a refactor"), but the 'what' is only implied through the topic list rather than stated as actions, leaving it at anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Comprehensive natural phrases users would actually say ("code quality", "technical debt", "hard to maintain", "what to refactor next", "coverage gaps") with synonyms across the domain and a concrete file-system marker (".repowise/ directory exists"), matching the anchor-5 pattern of natural terms plus extension-like markers.

5 / 5

Distinctiveness Conflict Risk

Scoping to "a Repowise-indexed codebase (.repowise/ directory exists)" creates a clear niche, but broadly applicable terms like "code quality" and "what to refactor next" carry minor overlap risk with general code-review/refactoring skills.

4 / 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

repowise-dev/repowise

Path

plugins/claude-code/skills/code-health/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.