RRepoGEO

REPOGEO REPORT · LITE

rokicool/gsd-opencode

Default branch main · commit ea572af7 · scanned 6/6/2026, 10:02:05 PM

GitHub: 787 stars · 59 forks

AI VISIBILITY SCORE
23 /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
2 / 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 rokicool/gsd-opencode, 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
    Add a prominent status update to the README introduction

    Why:

    CURRENT
    (The current README starts with a general description, with 'Breaking news' further down.)
    COPY-PASTE FIX
    Add the following sentence at the very beginning of the README: "Note: This project is an adapted version of TÂCHES for OpenCode, but as of 2026-05-16, the original get-shit-done is now recommended for use."
  • hightopics#2
    Add relevant topics to improve categorization

    Why:

    CURRENT
    (none)
    COPY-PASTE FIX
    ["meta-prompting", "context-engineering", "spec-driven-development", "ai-code-generation", "claude-code", "llm-tools", "taches", "opencode"]
  • highlicense#3
    Add a LICENSE file to the repository

    Why:

    CURRENT
    (no LICENSE file detected)
    COPY-PASTE FIX
    Create a LICENSE file in the repository root. If this project is based on TÂCHES, consider using the same license or a compatible one, and state it clearly in the README.

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 rokicool/gsd-opencode
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
LangChain
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. LangChain · recommended 2×
  2. LlamaIndex · recommended 2×
  3. Semantic Kernel · recommended 2×
  4. PromptLayer · recommended 1×
  5. Weights & Biases Prompts · recommended 1×
  • CATEGORY QUERY
    What tools help with meta-prompting and spec-driven development for AI code generation?
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LlamaIndex
    3. PromptLayer
    4. Weights & Biases Prompts
    5. Semantic Kernel
    6. Haystack
    7. OpenAI API
    8. Guardrails AI

    AI recommended 8 alternatives but never named rokicool/gsd-opencode. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    How to improve AI assistant code generation quality through better context engineering?
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LlamaIndex
    3. Semantic Kernel
    4. VS Code
    5. Codeium
    6. GitHub Copilot
    7. Cursor
    8. Pinecone
    9. Weaviate
    10. Qdrant
    11. Jinja2
    12. Pydantic
    13. OpenAPI Generator
    14. Swagger Codegen

    AI recommended 14 alternatives but never named rokicool/gsd-opencode. 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 rokicool/gsd-opencode?
    pass
    AI named rokicool/gsd-opencode explicitly

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

  • If a team adopts rokicool/gsd-opencode in production, what risks or prerequisites should they evaluate first?
    pass
    AI named rokicool/gsd-opencode 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 rokicool/gsd-opencode solve, and who is the primary audience?
    pass
    AI did not name rokicool/gsd-opencode — likely talking about a different project

    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 rokicool/gsd-opencode. 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/rokicool/gsd-opencode.svg)](https://repogeo.com/en/r/rokicool/gsd-opencode)
HTML
<a href="https://repogeo.com/en/r/rokicool/gsd-opencode"><img src="https://repogeo.com/badge/rokicool/gsd-opencode.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

rokicool/gsd-opencode — 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