RRepoGEO

REPOGEO REPORT · LITE

JuliusBrussee/cavemem

Default branch main · commit 1fe41e9c · scanned 6/9/2026, 1:27:04 PM

GitHub: 512 stars · 46 forks

AI VISIBILITY SCORE
27 /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
1 / 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 JuliusBrussee/cavemem, 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
    Clarify core purpose and persistence in README's first paragraph

    Why:

    COPY-PASTE FIX
    cavemem provides **cross-agent persistent memory for coding assistants**, storing observations locally in SQLite. Unlike in-memory-only solutions, `cavemem` ensures your AI assistant's history is saved across sessions, compressed efficiently with the Caveman grammar.
  • hightopics#2
    Add specific topics for AI coding assistants and local persistence

    Why:

    CURRENT
    ai, caveman, claude, claude-code, compress, memory, rag, rag-chatbot
    COPY-PASTE FIX
    ai, coding-assistant, persistent-memory, local-storage, sqlite, conversation-history, llm-memory, agent-memory, claude, claude-code, compress, rag, rag-chatbot
  • mediumabout#3
    Emphasize persistence and local storage in the repository description

    Why:

    CURRENT
    Cross-agent persistent memory for coding assistants. Stored compressed. Retrieved fast. Local by default.
    COPY-PASTE FIX
    Cross-agent **persistent** memory for coding assistants, stored locally in SQLite. Observations are compressed efficiently and retrieved fast, ensuring your AI's history is never lost.

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 JuliusBrussee/cavemem
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
SQLite
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. SQLite · recommended 1×
  2. chroma-core/chroma · recommended 1×
  3. duckdb/duckdb · recommended 1×
  4. JSON/YAML Files · recommended 1×
  5. Pickle · recommended 1×
  • CATEGORY QUERY
    How to give my AI coding assistant persistent memory for past interactions locally?
    you: not recommended
    AI recommended (in order):
    1. SQLite
    2. Chroma (chroma-core/chroma)
    3. DuckDB (duckdb/duckdb)
    4. JSON/YAML Files
    5. Pickle
    6. Faiss (facebookresearch/faiss)

    AI recommended 6 alternatives but never named JuliusBrussee/cavemem. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Tool for efficiently compressing and retrieving AI assistant conversation history across sessions?
    you: not recommended
    AI recommended (in order):
    1. Pinecone
    2. Weaviate
    3. Qdrant
    4. Elasticsearch
    5. Redis
    6. PostgreSQL

    AI recommended 6 alternatives but never named JuliusBrussee/cavemem. 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 JuliusBrussee/cavemem?
    pass
    AI did not name JuliusBrussee/cavemem — 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?

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

Subscribe to Pro for deep diagnoses

JuliusBrussee/cavemem — 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