code-refactoring-tech-debt

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete executable templates and quantified examples, and it is well-sequenced into clear sections. Its weaknesses are verbosity, a lack of validation checkpoints in the risky refactoring workflow, and a monolithic structure with no progressive disclosure via bundle files.

Suggestions

Add explicit validation checkpoints to the refactoring phases (e.g., 'run the test suite and confirm no regressions before enabling the next feature flag').

Split detailed reference material (metrics dashboard schema, communication/report templates) into files under references/ and link to them from SKILL.md to reduce the body length and improve progressive disclosure.

Trim or consolidate the illustrative ROI/example blocks and remove the restating 'Context' section to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body largely avoids explaining basics Claude already knows, but at ~380 lines it is padded with heavy worked-example dumps (ROI tables, yaml/python templates, trend dicts) and a restating 'Context' section that could be tightened, matching the 'mostly efficient but could be tightened' anchor rather than the lean level 3.	2 / 3
Actionability	It provides concrete, copy-paste-ready material throughout: executable Python (PaymentFacade phases, debt_budget dict, debt_trends), yaml quality-gate configs, quantified ROI calculations, and KPI targets with specific numbers, fully meeting the 'executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The eight numbered sections give a clear sequence (Inventory → Impact → Metrics → Plan → Implementation → Prevention → Communication → Metrics), but the risky refactoring phases (Phase 1/2/3) lack explicit validate-then-proceed checkpoints or feedback loops, which caps workflow clarity at 2 per the rubric's destructive/batch-operations rule.	2 / 3
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent) and the entire skill is a single ~380-line monolithic file with templates and reference-style material inline; it is well-sectioned so not a disorganized wall, but content that could be split out (metrics dashboard, communication templates) is inline, matching the level-2 anchor.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 conveys a clear domain and several concrete actions but is hurt by second-person voice, a missing 'Use when' trigger clause, and truncation mid-word. It is functional but fails to meet the bar for top scores on any dimension.

Suggestions

Rewrite in third person and add an explicit 'Use when...' trigger clause (e.g., 'Use when analyzing technical debt, planning refactoring, or prioritizing code-quality improvements').

Replace the truncated tail ('create acti') with a complete clause such as 'create actionable remediation plans'.

Broaden trigger terms to include natural variations like 'tech debt', 'legacy code', 'refactoring priorities', and 'code cleanup'.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions ('identifying, quantifying, and prioritizing technical debt', 'Analyze the codebase to uncover debt, assess its impact'), which would warrant a 3, but it uses second-person voice ('You are a technical debt expert') and is truncated mid-word ('create acti'), triggering the voice penalty that drops specificity by one.	2 / 3
Completeness	It clearly answers 'what' (identify, quantify, prioritize, analyze, assess impact) but provides no 'Use when...' clause or equivalent trigger guidance, capping completeness at 2 per the rubric guidelines; the truncation further weakens it.	2 / 3
Trigger Term Quality	'technical debt' and 'codebase' are natural terms a user would say, but coverage is thin — it repeats 'technical debt' without common variations like 'tech debt', 'refactoring', 'legacy code', or 'code cleanup', so it only partially matches the level-3 anchor.	2 / 3
Distinctiveness Conflict Risk	The 'technical debt' niche is reasonably specific, but with no explicit triggers and meaningful overlap with broader refactoring, code-review, and code-quality skills, it sits at the 'somewhat specific but could overlap' anchor rather than the clearly distinct level 3.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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
Commit: e63f7dd

Reviewed: about 4 hours ago

Table of Contents

Discovery Implementation Validation

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.