Technical debt assessment

Skill ulpi-io/plugin-marketplace/plugins/aj-geddes/skills/technical-debt-assessment

A curated collection of 7,800+ agent skills for Claude Desktop, sourced from skills.sh

Install

npx -y skills add ulpi-io/plugin-marketplace --skill technical-debt-assessment

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Assess, quantify, and prioritize technical debt using code analysis, metrics, and impact analysis. Use when planning refactoring, evaluating codebases, or making architectural decisions.

SKILL.md

2.0 KB, as published. Nobody here has run it

Overview

Systematically identify, measure, and manage technical debt to make informed decisions about code quality investments.

When to Use

Legacy code evaluation
Refactoring prioritization
Sprint planning
Code quality initiatives
Acquisition due diligence
Architectural decisions

Quick Start

Minimal working example:

interface DebtItem {
  id: string;
  title: string;
  description: string;
  category: "code" | "architecture" | "test" | "documentation" | "security";
  severity: "low" | "medium" | "high" | "critical";
  effort: number; // hours
  impact: number; // 1-10 scale
  interest: number; // cost per sprint if not fixed
}

class TechnicalDebtAssessment {
  private items: DebtItem[] = [];

  addDebtItem(item: DebtItem): void {
    this.items.push(item);
  }

  calculatePriority(item: DebtItem): number {
    const severityWeight = {
      low: 1,
      medium: 2,
      high: 3,
      critical: 4,
    };
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

Guide	Contents
Technical Debt Calculator	Technical Debt Calculator
Code Quality Scanner	Code Quality Scanner

Best Practices

✅ DO

Quantify debt impact
Prioritize by ROI
Track debt over time
Include debt in sprints
Document debt decisions
Set quality gates

❌ DON'T

Ignore technical debt
Fix everything at once
Skip impact analysis
Make emotional decisions