Is technical-debt-management safe to install?

SaferSkills independently audited technical-debt-management (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

src/auto_skill_mcp/skill_data/technical-debt-management/SKILL.md · 1 file

src/auto_skill_mcp/skill_data/technical-debt-management/SKILL.md1.4 KB · Markdown

name: technical-debt-management

description: Track, prioritize, and pay down technical debt systematically without breaking product delivery.

metadata:

category: code-quality

tags: [debt, technical-debt, quality, maintenance]

Technical Debt Management

Debt Types

Reckless vs Prudent: Did you know it was debt? Was it intentional?
Code debt: complexity, duplication, dead code
Design debt: wrong abstractions, over-engineering
Test debt: missing coverage, flaky tests
Documentation debt: missing or outdated docs

Management Process

Inventory — keep a living list of known debt items with context
Quantify impact — how much time does this cost per week? How much risk?
Prioritize — fix debt in code you touch (scout rule: leave it cleaner than you found it)
Budget time — allocate 20% of each sprint to debt reduction
Track progress — measure metrics like test coverage, cyclomatic complexity, build time

When to Fix vs Defer

Fix Now	Defer	Accept
Blocks development	Cosmetic issues	Known, documented risks
Causes production bugs	Out-of-style patterns	One-time migration costs
Creates security risk	Well-understood limitations	Strategic shortcuts
Increases all future changes	Low-impact violations	Deprecated code scheduled for removal

technical-debt-management— agent skill

Is technical-debt-management safe to install?

Technical Debt Management

Debt Types

Management Process

When to Fix vs Defer

Audit the pieces. Scan the whole. Decide.