SKILLEMALL.ai
GitHub ↗ RU Sign in

AC tech-debt-tracker

Find, rank and track tech debt in a codebase. Use whenever the user asks what to refactor first, plans a cleanup sprint, modernizes legacy code or wants to know how messy the code is.

alirezarezvani/claude-skills Agent Skills author: alirezarezvani MIT 18 files · 6 scripts body ≈ 1 092 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Find, rank and track tech debt in a codebase.

As a process C 53/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

ProcedureSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
98
Quality 40%
91
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 2

    ✓ No critical or high findings

    Medium and low: 2
    • low Secrets in code secret-password-literal assets/sample_codebase/src/frontend.js:5
      Hard-coded password / key literal (may be an example)
      const API_KEY = "abc1…456"; // FIXME: Should be in environment
    • low Secrets in code secret-password-literal assets/sample_codebase/src/user_service.py:14
      Hard-coded password / key literal (may be an example) (placeholder value)
      API_KEY = "sk-1…def"  # FIXME: This should be in environment variables
      placeholder

    Files scanned: 18. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 53/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 1 mutating operations with no state check
    • 70When it triggers. States when to use, but not when not to
    • 75Steps. 3 steps
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1092 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 183: enough signal without eating the budget
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 3 items
    • +4Has examples (3 code blocks)
    • +4Reference files are cited in the instructions (4 of 4)
    • +3All 3 scripts are documented

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.