RRepoGEO

REPOGEO REPORT · LITE

raiyanyahya/recall

Default branch master · commit 0d610133 · scanned 6/27/2026, 10:11:36 PM

GitHub: 583 stars · 31 forks

AI VISIBILITY SCORE
40 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
2 pass · 0 warn · 0 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 raiyanyahya/recall, 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 clear application-level positioning statement to the README intro

    Why:

    COPY-PASTE FIX
    Insert this sentence immediately after the H3 (e.g., '<h3 align="center">Recall — fully-local project memory for Claude Code</h3>'): "This is a specialized plugin designed for developers using Claude Code, not a generic memory database or LLM framework."
  • mediumcomparison#2
    Create a 'Comparison to Alternatives' section in the README

    Why:

    COPY-PASTE FIX
    Add a new section to the README, e.g., '## Recall vs. Generic Memory Solutions', explaining that Recall is an application for Claude Code, not a general-purpose vector database or LLM framework like those often recommended.
  • lowreadme#3
    Enhance repository description with 'AI coding assistant' keyword

    Why:

    CURRENT
    Stop wasting tokens and re-explaining your project every session. Recall gives Claude Code durable memory — entirely offline.
    COPY-PASTE FIX
    Stop wasting tokens and re-explaining your project every session. Recall gives your AI coding assistant (specifically Claude Code) durable memory — entirely offline.

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 raiyanyahya/recall
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Chroma
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Chroma · recommended 2×
  2. SQLite · recommended 2×
  3. LangChain · recommended 1×
  4. Pinecone · recommended 1×
  5. Weaviate · recommended 1×
  • CATEGORY QUERY
    How to give my AI coding assistant persistent memory across sessions?
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. Pinecone
    3. Weaviate
    4. Chroma
    5. Qdrant
    6. LlamaIndex
    7. Redis
    8. PostgreSQL
    9. MongoDB
    10. SQLite

    AI recommended 10 alternatives but never named raiyanyahya/recall. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are options for private, local context management to save LLM tokens?
    you: not recommended
    AI recommended (in order):
    1. Chroma
    2. FAISS
    3. LanceDB
    4. DuckDB
    5. hnswlib
    6. SQLite

    AI recommended 6 alternatives but never named raiyanyahya/recall. This is the gap to close.

    Show full AI answer

Objective checks

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

  • Metadata completeness
    pass

  • 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 raiyanyahya/recall?
    pass
    AI named raiyanyahya/recall explicitly

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

  • If a team adopts raiyanyahya/recall in production, what risks or prerequisites should they evaluate first?
    pass
    AI named raiyanyahya/recall 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 raiyanyahya/recall solve, and who is the primary audience?
    pass
    AI named raiyanyahya/recall 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 raiyanyahya/recall. 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/raiyanyahya/recall.svg)](https://repogeo.com/en/r/raiyanyahya/recall)
HTML
<a href="https://repogeo.com/en/r/raiyanyahya/recall"><img src="https://repogeo.com/badge/raiyanyahya/recall.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

raiyanyahya/recall — 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