CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tech-debt

Scan, prioritize, and report technical debt. Usage: /tech-debt <scan|prioritize|report> [options]

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/tech-debt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean and highly actionable with concrete commands and full script syntax, so an agent knows exactly how to invoke each capability. However, the end-to-end workflow connecting the three commands is implicit rather than explicit, there are no validation checkpoints, and the referenced script paths plus a circular self-reference do not resolve within the provided bundle. Fixing the reference structure and spelling out the scan→prioritize→report pipeline would lift the weaker dimensions.

Suggestions

Add an explicit workflow line such as "1. Run scan to produce inventory.json → 2. Feed inventory.json to prioritize → 3. Run report for the dashboard", so the data flow between subcommands is explicit.

Include a validation checkpoint (e.g., verify inventory.json exists and is well-formed before prioritizing) to satisfy the feedback-loop expectation for batch operations.

Fix the reference structure: point the Scripts section to bundle-relative paths (scripts/debt_scanner.py) and remove or correct the circular "Skill Reference" link to the SKILL.md itself.

DimensionReasoningScore

Conciseness

The ~30-line body contains only usage syntax, copy-paste examples, and a script inventory with no concept explanations or padding; every line is operational, matching the lean anchor.

5 / 5

Actionability

Concrete executable commands with flags ("/tech-debt scan . --format json --output debt-report.json") and exact script invocations with argument lists ("debt_prioritizer.py <inventory.json> [--framework cost_of_delay|wsjf|rice]") make the guidance copy-paste ready and cover the common cases.

5 / 5

Workflow Clarity

The three subcommands are listed with their inputs, but the scan → inventory.json → prioritize → report pipeline is only implicit, and there are no explicit sequence or validation/verification steps; the batch codebase scan also caps workflow clarity at 3 per the rubric guidelines.

3 / 5

Progressive Disclosure

Sections are clearly labeled, but the bundle contains no scripts/references/assets directories while the Scripts section points to external "engineering/skills/tech-debt-tracker/scripts/..." paths outside the bundle, and "Skill Reference" is a circular link to the SKILL.md itself; references are present but not resolvable against the actual bundle structure.

3 / 5

Total

16

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states what the skill does and is concise, but it omits any when-to-use trigger guidance and lacks common synonym terms users would naturally say. It is distinguishable from other skills but sits just below the strongest examples. Adding an explicit "Use when..." clause with natural trigger phrases would raise completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user mentions technical debt, tech debt, code debt, code smells, or asks for a debt backlog or remediation plan."

Include common user phrasings and synonyms ("tech debt", "code debt", "refactoring backlog", "remediation plan") alongside the existing keywords.

Briefly state what each action produces (e.g., "scan codebases for debt indicators, score severity, and generate prioritized remediation plans") to make the capabilities more concrete.

DimensionReasoningScore

Specificity

"Scan, prioritize, and report technical debt" names the domain and three concrete actions, but the description never states what each action entails or produces (e.g., severity scoring, remediation plans, output formats), leaving coverage thin rather than comprehensive.

3 / 5

Completeness

The "what" is clear (scan, prioritize, and report technical debt), but there is no "Use when..." clause or equivalent trigger guidance; the "Usage: /tech-debt <scan|prioritize|report> [options]" portion is invocation syntax, not when-to-use guidance, so completeness is capped at 3.

3 / 5

Trigger Term Quality

It includes relevant keywords ("technical debt", "scan", "prioritize", "report") but misses natural variations users commonly say such as "tech debt", "code debt", "code smells", or "refactoring backlog".

3 / 5

Distinctiveness Conflict Risk

"Technical debt" is a distinct niche with triggers unlikely to fire for unrelated skills, with only minor overlap risk against closely related code-quality or refactoring skills; it lacks the distinguishing trigger phrases needed for a 5.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/tech-debt/SKILL.md

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.