pbuckles22/tech-debt-evaluator
.cursor/skills/tech-debt-evaluator/SKILL.md
Assess and prioritize technical debt (code, architecture, tests, docs, performance). Use when planning refactors, sprint planning, or evaluating codebase health.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add pbuckles22/URLAutoRefresher tech-debt-evaluatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 2:23 AM9.7s1 file scanned
SKILL.md
- name:
- tech-debt-evaluator
- description:
- Assess and prioritize technical debt (code, architecture, tests, docs, performance). Use when planning refactors, sprint planning, or evaluating codebase health.
Tech debt evaluator — Project
Use this skill when evaluating technical debt, planning refactors, or assessing codebase health. Produces a structured, prioritized list.
Role
- Classify debt by category: code (duplication, complexity, coupling), architecture (layering, boundaries), tests (gaps, flakiness), documentation (out-of-date specs), performance (UI thread, blocking work).
- Severity: Low, Medium, High, Critical (e.g. data loss, crash).
- Prioritize: Impact and effort; surface high-impact, lower-effort items first.
- Reference: Use DEV_GUIDE.md, TEST_TDD.md, DESIGN_SYSTEM.md, AGENT_HANDOFF.md as the bar. Debt = deviation or gap vs. those.
When to use
- User asks for a tech-debt pass, health check, or refactor plan.
- Before a large feature or architectural change.
- Sprint or handoff planning.
Output format
For each item: Category | Severity | What (one line + file/area) | Why it matters | Suggested fix | Effort (optional). Optionally group by "Do first" vs "Backlog".
Related Skills
pbuckles22/visual-match
tools
VerifiedTrustedCommunity
Match UI graphics to reference examples (examples/ screenshots and specs). Use when drawing or changing visuals so the result matches the examples without back-and-forth.
SKILL.mdUpdated Apr 16, 2026
pbuckles22/ui-ux
content-media
VerifiedTrustedCommunity
UI/UX review and alignment. Use when writing or reviewing screens, animations, haptics, layout, or design tokens; or when adding/changing UX to match project requirements and accessibility.
SKILL.mdUpdated Apr 16, 2026
pbuckles22/tester
testing
VerifiedTrustedCommunity
Black-box tests, test-first for core logic, and continuous test runs. Use when adding or changing tests or app logic. Run your project’s test command after changes; keep suite green.
SKILL.mdUpdated Apr 16, 2026
pbuckles22/techwriter
development
VerifiedTrustedCommunity
Creates and edits project documentation for both public and internal audiences. Use when writing or updating README.md, AGENT_HANDOFF (or AGENTS.md), CONTRIBUTING, or internal docs (e.g. PM_PLAN, DEV_GUIDE, TEST_TDD, DESIGN_SYSTEM). Covers structure, tone, and what to include for each doc type.
SKILL.mdUpdated Apr 16, 2026