CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

codebase-cleanup-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

72%

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/codebase-cleanup-tech-debt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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-structured, actionable analysis workflow with concrete thresholds, cost models, and templates, but it is significantly overlong: it restates code-quality concepts Claude already knows, includes boilerplate use/do-not-use sections, and embeds dated, fabricated example data. Splitting templates into reference files and cutting the taxonomy restatement would substantially improve token efficiency.

Suggestions

Cut the 'Use this skill when' / 'Do not use this skill when' / 'Context' / 'Requirements' boilerplate sections and compress the Section 1 debt taxonomy to a checklist of thresholds (complexity >10, methods >50 lines, classes >500 lines) since Claude already knows these code-quality concepts.

Move the stakeholder report templates, refactoring guide, and detailed remediation/ROI examples into reference files (e.g., references/report-templates.md, references/remediation-examples.md) and keep SKILL.md as a concise overview with clearly signaled links.

Replace time-sensitive fabricated data (React 16 → 18, 2024_Q1 trend dict, $150/hour rate) with placeholder-driven templates so the examples stay evergreen.

DimensionReasoningScore

Conciseness

Noticeably verbose: boilerplate sections ("The task is unrelated to technical debt analysis and remediation", "Take the requirements, target, and scope from the user's request") add nothing, and the debt taxonomy ("Feature envy", "God classes", "Circular dependencies") largely restates concepts Claude already knows, while fabricated dated examples ("2024_Q1", "React 16 → 18", "$150/hour") pad the doc. It is above anchor 1 because the content is structured as operational checklists and templates rather than tutorial-style explanation.

2 / 5

Actionability

Concrete thresholds ("High cyclomatic complexity (>10)", "God classes (>500 lines, >20 methods)"), worked cost/ROI calculations, and specific YAML quality-gate configs give mostly executable guidance. Not 5 because code examples contain placeholders ("# Clean implementation / pass") and are illustrative rather than copy-paste ready.

4 / 5

Workflow Clarity

Eight clearly numbered phases (Inventory → Impact Assessment → Metrics → Remediation Plan → Implementation → Prevention → Communication → Success Metrics) plus a defined Output Format give a strong sequence, and Section 8's monthly targets and quarterly reviews act as outcome checkpoints. Not 5 because there are no mid-workflow validation checkpoints (e.g., verifying metrics before prioritizing); not 3 because checkpoints are more than implicit.

4 / 5

Progressive Disclosure

The single ~380-line SKILL.md inlines content that clearly belongs in separate reference files (stakeholder report templates, refactoring guides, remediation examples) with no bundle files at all. It is above anchor 2 because sections are well-organized with clear headers, but below 4 because nothing is split out despite the length.

3 / 5

Total

13

/

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.

A strong description that clearly states what the skill does and when to use it, in appropriate third-person imperative voice with concrete quantification language. Minor improvements possible: broaden trigger coverage with synonyms like "tech debt", "refactoring", and "legacy code".

DimensionReasoningScore

Specificity

"Identify and prioritize technical debt by maintenance cost, delivery impact, and risk" plus "planning a measurable remediation roadmap" names several specific actions with quantification dimensions. Not 5 because coverage has gaps (metrics dashboards, prevention strategy, stakeholder communication are unmentioned); not 3 because it goes beyond 1-2 generic actions.

4 / 5

Completeness

Both parts are explicit: what = "Identify and prioritize technical debt by maintenance cost, delivery impact, and risk", when = "Use when assessing code health or planning a measurable remediation roadmap". Not 5 because the when-clause covers only two activity-level triggers and lacks the richer object-level trigger phrases of the anchor-5 example.

4 / 5

Trigger Term Quality

"technical debt", "code health", and "remediation roadmap" are natural phrases users would say when needing this skill. Not 5 because common variants like "tech debt", "refactoring", "legacy code", and "code cleanup" are missing; not 3 because the included keywords are more than 'some relevant' coverage.

4 / 5

Distinctiveness Conflict Risk

Technical debt analysis is a clear niche with domain-specific triggers, so it is mostly distinct from other skills. Not 5 because "assessing code health" is a broadish trigger that could overlap with general code-review or refactoring skills.

4 / 5

Total

16

/

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/codebase-cleanup-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.