techdebt
Technical debt detection and remediation. Run at session end to find duplicated code, dead imports, security issues, and complexity hotspots. Triggers: 'find tech debt', 'scan for issues', 'check code quality', 'wrap up session', 'ready to commit', 'before merge', 'code review prep'. Always uses parallel subagents for fast analysis.
88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 a strong skill description that excels across all dimensions. It provides specific concrete actions (duplicated code, dead imports, security issues, complexity hotspots), includes an explicit and comprehensive trigger list with natural user language, and clearly defines both what the skill does and when to use it. The description is concise yet complete, using proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'find duplicated code, dead imports, security issues, and complexity hotspots'. These are precise, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Technical debt detection and remediation' with specific capabilities) AND when ('Run at session end', explicit 'Triggers:' clause with multiple scenarios). The explicit trigger guidance is comprehensive. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'find tech debt', 'scan for issues', 'check code quality', 'wrap up session', 'ready to commit', 'before merge', 'code review prep'. These match real user language patterns. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on technical debt and code quality analysis with distinct triggers like 'tech debt', 'complexity hotspots', and session-end workflows. Unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent workflow clarity and progressive disclosure. The main weaknesses are verbosity (explaining concepts like parallel execution benefits that Claude understands) and lack of truly executable code - the skill describes what scanners should do rather than providing working implementations. The detection patterns section would benefit from actual ast-grep patterns rather than descriptions.
Suggestions
Replace the conceptual subagent instructions template with actual working subagent prompts or executable scanner code
Add concrete ast-grep patterns for the duplication and security detection sections (e.g., actual YAML pattern files)
Remove the 'Benefits' bullet list and other explanatory content that describes why parallel execution is good - Claude understands this
Consolidate the troubleshooting and best practices sections into a more concise format or move to a reference file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but overly verbose in places. The architecture diagram, detailed tables, and extensive examples add value, but sections like 'Benefits' with emoji bullets and the lengthy troubleshooting/best practices sections explain concepts Claude already understands. Could be tightened by 30-40%. | 2 / 3 |
Actionability | Provides good conceptual guidance with command examples and report templates, but lacks truly executable code. The subagent instructions are templates rather than working implementations, and the detection patterns describe what to look for without providing actual ast-grep patterns or working scanner code. | 2 / 3 |
Workflow Clarity | Excellent step-by-step workflow with clear sequencing (Steps 1-5), explicit validation in auto-fix mode with safety rules, and clear decision points. The consolidation step includes deduplication and ranking, and the auto-fix section has explicit safety constraints preventing dangerous automatic changes. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from Quick Start to Architecture to detailed Workflow. References external files appropriately (references/patterns.md, references/severity-guide.md) and organizes advanced features separately. Content is appropriately split between overview and detailed sections. | 3 / 3 |
Total | 10 / 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.