RRepoGEO

REPOGEO REPORT · LITE

ksimback/tech-debt-skill

Default branch main · commit 5a15c1ca · scanned 6/14/2026, 12:02:49 PM

GitHub: 514 stars · 30 forks

AI VISIBILITY SCORE
30 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 0 warn · 1 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface ksimback/tech-debt-skill, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Reposition the README H1 and opening sentence to clarify 'Claude Code skill'

    Why:

    CURRENT
    # tech-debt-audit
    
    A Claude Code skill that produces a thorough, citable tech debt audit of your entire codebase — not a generic best-practices checklist.
    COPY-PASTE FIX
    # ksimback/tech-debt-skill: A Claude Code Skill for Thorough Tech Debt Audits
    
    This is a Claude Code skill that produces a thorough, file-cited tech debt audit of your entire codebase, designed to go beyond generic best-practices checklists and provide actionable, citable findings.
  • hightopics#2
    Add relevant topics to the repository

    Why:

    COPY-PASTE FIX
    claude-ai, llm, tech-debt, code-audit, ai-code-review, generative-ai, anthropic-claude
  • highlicense#3
    Add a LICENSE file to the repository

    Why:

    COPY-PASTE FIX
    Create a LICENSE file in the repository root, e.g., with the MIT License text.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface ksimback/tech-debt-skill
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
SonarQube
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. SonarQube · recommended 2×
  2. CodeClimate · recommended 2×
  3. DeepSource · recommended 2×
  4. Codiga · recommended 1×
  5. GitHub Copilot · recommended 1×
  • CATEGORY QUERY
    How can I get an AI to thoroughly audit my codebase for technical debt?
    you: not recommended
    AI recommended (in order):
    1. SonarQube
    2. CodeClimate
    3. DeepSource
    4. Codiga
    5. GitHub Copilot
    6. ChatGPT
    7. Pylint
    8. ESLint
    9. Checkstyle
    10. RuboCop
    11. Snyk Code

    AI recommended 11 alternatives but never named ksimback/tech-debt-skill. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for a tool that provides actionable, file-cited tech debt findings, not just generic advice.
    you: not recommended
    AI recommended (in order):
    1. SonarQube
    2. CodeClimate
    3. DeepSource
    4. Codacy
    5. Kiuwan
    6. CAST Highlight
    7. Embold

    AI recommended 7 alternatives but never named ksimback/tech-debt-skill. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    fail

    Suggestion:

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of ksimback/tech-debt-skill?
    pass
    AI named ksimback/tech-debt-skill explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts ksimback/tech-debt-skill in production, what risks or prerequisites should they evaluate first?
    pass
    AI named ksimback/tech-debt-skill explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo ksimback/tech-debt-skill solve, and who is the primary audience?
    pass
    AI named ksimback/tech-debt-skill explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of ksimback/tech-debt-skill. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/ksimback/tech-debt-skill.svg)](https://repogeo.com/en/r/ksimback/tech-debt-skill)
HTML
<a href="https://repogeo.com/en/r/ksimback/tech-debt-skill"><img src="https://repogeo.com/badge/ksimback/tech-debt-skill.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

ksimback/tech-debt-skill — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite