Index of every page on this site: llms.txt
All skills
anthropics avatar

/tech-debt

@b4c9a4e
Run it yourself

Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring priorities, or maintenance backlog.

Use this Skill: https://skilld.dev/gh/anthropics/knowledge-work-plugins/tech-debt

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈61 tokens for metadata: the name and description. ≈296 when used: this file.

Description uses 3.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈246 characters, or 3.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Tech Debt Management

Systematically identify, categorize, and prioritize technical debt.

Categories

Type Examples Risk
Code debt Duplicated logic, poor abstractions, magic numbers Bugs, slow development
Architecture debt Monolith that should be split, wrong data store Scaling limits
Test debt Low coverage, flaky tests, missing integration tests Regressions ship
Dependency debt Outdated libraries, unmaintained dependencies Security vulns
Documentation debt Missing runbooks, outdated READMEs, tribal knowledge Onboarding pain
Infrastructure debt Manual deploys, no monitoring, no IaC Incidents, slow recovery

Prioritization Framework

Score each item on:

  • Impact: How much does it slow the team down? (1-5)
  • Risk: What happens if we don't fix it? (1-5)
  • Effort: How hard is the fix? (1-5, inverted — lower effort = higher priority)

Priority = (Impact + Risk) x (6 - Effort)

Output

Produce a prioritized list with estimated effort, business justification for each item, and a phased remediation plan that can be done alongside feature work.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides an informational framework for identifying and prioritizing technical debt. It contains no executable code, network operations, or external dependencies, posing no security risk.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer9mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at b4c9a4e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 9 months ago

README badge

README badge for anthropics/knowledge-work-plugins/tech-debt

Identifies and scores technical debt across six categories (code, architecture, test, dependency, documentation, infrastructure) using an impact-risk-effort framework, then produces a prioritized remediation roadmap. Helps teams balance feature work with refactoring by quantifying debt and phasing fixes.

Generated from the current SKILL.md.

Does this skill work with specific languages or frameworks?
No. The skill is language and framework agnostic. It provides a general framework for identifying and prioritizing technical debt across any codebase, regardless of tech stack.
What does the prioritization formula actually calculate?
It scores each debt item on impact (1-5), risk (1-5), and effort (1-5), then applies Priority = (Impact + Risk) × (6 - Effort). Higher scores indicate higher priority.
Does this skill generate a remediation plan?
Yes. The skill produces a prioritized list with estimated effort, business justification for each item, and a phased remediation plan designed to run alongside ongoing feature work.
What triggers this skill?
Use it when you ask about tech debt, technical debt audits, refactoring priorities, code health, code quality, or maintenance backlogs.

Generated from the current SKILL.md. These answers refresh after source changes.