technical-debt-analyzer
Analyzes a codebase to quantify and locate technical debt — where it lives, what it costs, and what order to pay it down in. Use when planning a refactoring sprint, when justifying engineering time to stakeholders, when the user asks where the codebase hurts most, or when onboarding to a legacy system.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill technical-debt-analyzer100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It uses third person voice, provides specific concrete outputs (location, cost, prioritization of technical debt), and includes a comprehensive 'Use when...' clause with four natural trigger scenarios. The description is concise yet complete, making it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'quantify and locate technical debt', 'where it lives', 'what it costs', 'what order to pay it down in'. These are clear, actionable outputs. | 3 / 3 |
Completeness | Clearly answers both what (analyzes codebase to quantify/locate technical debt, costs, prioritization) AND when with explicit 'Use when...' clause covering four distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'technical debt', 'refactoring sprint', 'engineering time', 'stakeholders', 'codebase hurts', 'legacy system', 'onboarding'. Good coverage of varied user scenarios. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on technical debt analysis with distinct triggers like 'refactoring sprint', 'where the codebase hurts', 'legacy system'. Unlikely to conflict with general code analysis or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
Excellent skill content that treats technical debt analysis as a cost optimization problem rather than a code quality checklist. The combination of executable git commands, a concrete worked example with real analysis, and explicit anti-patterns ('Do not rank by complexity alone') makes this immediately actionable. The output format template ensures consistent, stakeholder-ready deliverables.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. The cost equation is essential framing, the signals table is dense reference material, and the worked example teaches by showing rather than explaining. No padding or concepts Claude already knows. | 3 / 3 |
Actionability | Provides executable git commands for every signal, a concrete worked example with real file analysis, specific paydown plans with time estimates, and a copy-paste output format. Claude can immediately apply this. | 3 / 3 |
Workflow Clarity | Clear sequence: gather signals → plot hotspot map → analyze with cost equation → produce prioritized output. The worked example demonstrates the full workflow, and the 'Do not' section provides explicit validation guardrails (coverage first, no rewrites). | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from concept (cost equation) → data gathering (signals table) → visualization (hotspot map) → application (worked example) → constraints (do not) → output format. Appropriate length for a single file with no need for external references. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
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.