CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-refactoring-tech-debt

Identify and prioritize technical debt by maintenance cost, delivery impact, and risk. Use when assessing code health or planning a measurable remediation roadmap.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/code-refactoring-tech-debt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-sequenced, methodology-rich skill with concrete thresholds, cost formulas, and output templates that make it genuinely actionable. Its weaknesses are a verbose inline taxonomy of known concepts, time-sensitive sample data, and a monolithic single-file structure with no progressive disclosure despite being well over 300 lines.

Suggestions

Trim or collapse the debt-type taxonomy (Code/Architecture/Testing/Documentation/Infrastructure debt listings) to a compact checklist — Claude already knows these concepts — and keep only the 'Quantify' guidance.

Move the detailed roadmap examples, communication-plan templates, and prevention-gate configs into reference files (e.g., references/roadmap-templates.md, references/communication.md) and link to them from SKILL.md.

Replace time-sensitive sample data ("2024_Q1", "React 16 → 18", "$150/hour") with placeholder-driven, date-agnostic examples so the skill does not age.

DimensionReasoningScore

Conciseness

The eight sections are largely efficient output templates, but the ~70-line debt taxonomy (god classes, feature envy, cyclomatic complexity thresholds) restates concepts Claude already knows, and sample data embeds time-sensitive markers like "2024_Q1" and "React 16 → 18". Mostly efficient, but could be tightened — matching anchor 3 rather than 2 because the example blocks serve as output formats rather than pure padding.

3 / 5

Actionability

Concrete thresholds (complexity >10, methods >50 lines, god classes >500 lines), cost-calculation formulas, YAML metrics/gates templates, and a phased facade-to-migration refactoring pattern give mostly executable guidance. Not a 5 because code snippets are illustrative rather than copy-paste ready (`pass` bodies, undefined `feature_flag()`) and no commands or tools are given for actually scanning a codebase.

4 / 5

Workflow Clarity

A clearly sequenced 8-step process (inventory → impact assessment → metrics dashboard → prioritized roadmap → implementation → prevention → communication → success metrics) with quantification built into each stage. Not a 5 because validation checkpoints are implicit (success KPIs at the end) rather than explicit verify-and-fix loops between stages.

4 / 5

Progressive Disclosure

Section headers provide real navigation across the eight steps, but the skill is ~380 fully-inline lines with zero bundle files or references — roadmap templates, the communication-plan examples, and the prevention gates are content that clearly belongs in separate reference files. Structure exists, but content that should be separate is inline, matching anchor 3 rather than 2 (headers prevent a 'minimal structure' reading) or 4 (nothing is offloaded).

3 / 5

Total

14

/

20

Passed

Description

62%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 solid third-person description with a clear what-and-when structure and a well-defined niche. Its main gaps are limited action variety and missing common trigger synonyms such as refactoring, legacy code, or code quality.

Suggestions

Expand the action list beyond 'identify and prioritize' (e.g., quantify debt cost, generate a metrics dashboard, produce a prioritized remediation roadmap) to broaden capability coverage.

Add natural trigger synonyms users would actually say, such as 'refactoring', 'legacy code', 'code quality', or 'maintainability', to the Use-when clause.

DimensionReasoningScore

Specificity

"Identify and prioritize technical debt" names the domain with exactly two concrete actions, qualified by measurable dimensions ("maintenance cost, delivery impact, and risk"). It matches the anchor for 1-2 concrete actions and falls short of several specific actions.

3 / 5

Completeness

It clearly answers 'what' ("Identify and prioritize technical debt by maintenance cost, delivery impact, and risk") and has an explicit "Use when assessing code health or planning a measurable remediation roadmap" trigger. Not a 5 because the when-clause lacks the multi-synonym concrete trigger phrases of the top anchor.

4 / 5

Trigger Term Quality

"technical debt", "code health", and "remediation roadmap" are relevant natural keywords, but common variations users would say — "refactoring", "legacy code", "code quality", "maintainability" — are absent, matching the 'missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

"Technical debt" is a distinct niche with clear triggers, carrying only minor overlap risk with closely related refactoring or code-review skills. Not a 5 because adjacent code-quality skills could still compete for the same triggers.

4 / 5

Total

14

/

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

rmyndharis/antigravity-skills

Path

skills/code-refactoring-tech-debt/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.