RRepoGEO

REPOGEO REPORT · LITE

susiai/susi_device

Default branch master · commit c90979c9 · scanned 6/22/2026, 11:23:01 PM

GitHub: 1,005 stars · 1 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

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 susiai/susi_device, 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

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

OVERALL DIRECTION
  • highabout#1
    Add a concise repository description

    Why:

    COPY-PASTE FIX
    Build an open-source, offline smart speaker with a local LLM, microphone, speaker, and display on a Raspberry Pi using Docker.
  • highlicense#2
    Add a LICENSE file and clarify licensing in README

    Why:

    COPY-PASTE FIX
    Create a `LICENSE` file in the repository root with your chosen open-source license (e.g., Apache-2.0, MIT). Then, add a line to the README, for example: `This project is licensed under the Apache-2.0 License - see the [LICENSE](LICENSE) file for details.`

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 susiai/susi_device
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
mycroftai/mycroft-core
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. mycroftai/mycroft-core · recommended 1×
  2. Picroft · recommended 1×
  3. ggerganov/llama.cpp · recommended 1×
  4. alphacep/vosk-api · recommended 1×
  5. mozilla/DeepSpeech · recommended 1×
  • CATEGORY QUERY
    How can I build an offline voice assistant with a local LLM on a Raspberry Pi?
    you: not recommended
    AI recommended (in order):
    1. Mycroft AI (mycroftai/mycroft-core)
    2. Picroft
    3. llama.cpp (ggerganov/llama.cpp)
    4. Vosk (alphacep/vosk-api)
    5. Mozilla DeepSpeech (mozilla/DeepSpeech)
    6. Piper (rhasspy/piper)
    7. Rhasspy (rhasspy/rhasspy)
    8. Kaldi (kaldi-asr/kaldi)
    9. eSpeak-ng (espeak-ng/espeak-ng)
    10. Home Assistant (home-assistant/core)
    11. Whisper.cpp (ggerganov/whisper.cpp)
    12. Picovoice Porcupine (Picovoice/porcupine)
    13. OpenWakeWord (dscripka/openwakeword)

    AI recommended 13 alternatives but never named susiai/susi_device. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What open-source frameworks exist for creating smart devices with local AI and Docker?
    you: not recommended
    AI recommended (in order):
    1. Home Assistant OS
    2. Home Assistant Supervised
    3. OpenHAB
    4. Node-RED
    5. Eclipse Kura
    6. EdgeX Foundry
    7. MicroK8s
    8. K3s

    AI recommended 8 alternatives but never named susiai/susi_device. 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 susiai/susi_device?
    pass
    AI named susiai/susi_device explicitly

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

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

Subscribe to Pro for deep diagnoses

susiai/susi_device — 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