RRepoGEO

REPOGEO REPORT · LITE

iBlinkQ/llm-wiki-obsidian-blink

Default branch main · commit a9e8399c · scanned 6/25/2026, 2:12:23 AM

GitHub: 509 stars · 90 forks

AI VISIBILITY SCORE
17 /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
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 iBlinkQ/llm-wiki-obsidian-blink, 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
  • hightopics#1
    Add relevant topics to the repository

    Why:

    COPY-PASTE FIX
    llm, obsidian, knowledge-management, personal-wiki, ai-assistant, knowledge-base, andrej-karpathy, llm-wiki-pattern
  • highreadme#2
    Update the README's main heading to emphasize AI-driven automation

    Why:

    CURRENT
    # LLM Wiki - 基于 Obsidian 的知识管理系统
    COPY-PASTE FIX
    # LLM Wiki: AI 驱动的 Obsidian 知识管理系统，自动化维护可复利的个人知识库
  • highlicense#3
    Add a LICENSE file to the repository

    Why:

    COPY-PASTE FIX
    Create a LICENSE file in the repository root 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 iBlinkQ/llm-wiki-obsidian-blink
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Obsidian
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Obsidian · recommended 2×
  2. Mem.ai · recommended 2×
  3. Logseq · recommended 2×
  4. Dataview · recommended 1×
  5. Linter · recommended 1×
  • CATEGORY QUERY
    How can I automate personal knowledge base maintenance using large language models?
    you: not recommended
    AI recommended (in order):
    1. Obsidian
    2. Dataview
    3. Linter
    4. Smart Connections
    5. Text Generator
    6. Mem.ai
    7. Notion AI
    8. Logseq
    9. Logseq AI
    10. SmartBlocks
    11. OpenAI API
    12. Anthropic API
    13. LlamaIndex
    14. LangChain
    15. Readwise Reader
    16. Ghostreader
    17. Capacities.io

    AI recommended 17 alternatives but never named iBlinkQ/llm-wiki-obsidian-blink. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Tools for building an AI-driven personal wiki with structured knowledge and persistent learning?
    you: not recommended
    AI recommended (in order):
    1. Obsidian
    2. Logseq
    3. Notion
    4. TiddlyWiki
    5. Mem.ai
    6. Roam Research

    AI recommended 6 alternatives but never named iBlinkQ/llm-wiki-obsidian-blink. 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 iBlinkQ/llm-wiki-obsidian-blink?
    pass
    AI did not name iBlinkQ/llm-wiki-obsidian-blink — 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 iBlinkQ/llm-wiki-obsidian-blink in production, what risks or prerequisites should they evaluate first?
    pass
    AI named iBlinkQ/llm-wiki-obsidian-blink 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 iBlinkQ/llm-wiki-obsidian-blink solve, and who is the primary audience?
    pass
    AI did not name iBlinkQ/llm-wiki-obsidian-blink — 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 iBlinkQ/llm-wiki-obsidian-blink. 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/iBlinkQ/llm-wiki-obsidian-blink.svg)](https://repogeo.com/en/r/iBlinkQ/llm-wiki-obsidian-blink)
HTML
<a href="https://repogeo.com/en/r/iBlinkQ/llm-wiki-obsidian-blink"><img src="https://repogeo.com/badge/iBlinkQ/llm-wiki-obsidian-blink.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

iBlinkQ/llm-wiki-obsidian-blink — 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