RRepoGEO

REPOGEO REPORT · LITE

iwe-org/iwe

Default branch master · commit 39f0ed98 · scanned 6/29/2026, 9:27:20 AM

GitHub: 1,214 stars · 56 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
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 iwe-org/iwe, 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
    Reposition the README's opening paragraph to explicitly define the project category

    Why:

    CURRENT
    IWE turns a directory of markdown files into a knowledge graph — a connected structure you browse from your editor and your AI queries from the command line. Same files, same links, two interfaces. No cloud, no database, no lock-in. Version everything with git.
    COPY-PASTE FIX
    IWE is a local-first, plain Markdown knowledge graph and Zettelkasten system for personal knowledge management and AI agent integration. It transforms your directory of markdown files into queryable context, browsable from your editor and accessible via CLI. Unlike web platforms or development environments, IWE offers a powerful memory system with no cloud, no database, and no lock-in, versioned with git.
  • mediumreadme#2
    Add a dedicated 'Comparison' section to the README

    Why:

    COPY-PASTE FIX
    ## IWE vs. X, Y, Z

IWE differentiates itself from tools like Obsidian, Logseq, and Zettlr by focusing on a local-first, plain Markdown knowledge graph that is equally accessible to human editors (via LSP integration) and AI agents (via CLI and MCP server). Unlike general-purpose graph databases such as Neo4j or Memgraph, IWE operates directly on your file system, ensuring no lock-in and full Git version control. It provides structured access for AI without requiring proprietary formats or cloud services, making it a unique blend of Zettelkasten principles with modern AI tooling.
  • lowreadme#3
    Enhance the 'What You Get' section with more explicit keywords

    Why:

    CURRENT
    Plain markdown, full ownership.** Your notes are `.md` files in a local directory. Read them, edit them, `git push` them. Nothing proprietary.
    COPY-PASTE FIX
    Plain markdown, full ownership, local-first.** Your notes are `.md` files in a local directory, forming a true Zettelkasten system. Read them, edit them, `git push` them. Nothing proprietary.

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 iwe-org/iwe
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. Dataview · recommended 1×
  3. Neo4j · recommended 1×
  4. Memgraph · recommended 1×
  5. Logseq · recommended 1×
  • CATEGORY QUERY
    How can I organize markdown notes into a queryable knowledge graph for AI agents?
    you: not recommended
    AI recommended (in order):
    1. Obsidian
    2. Dataview
    3. Neo4j
    4. Memgraph
    5. Logseq
    6. Airtable
    7. ArangoDB
    8. Dendron
    9. markdown-it-py
    10. mistune
    11. spaCy
    12. NetworkX
    13. Dgraph
    14. Roam Research

    AI recommended 14 alternatives but never named iwe-org/iwe. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are good CLI tools for managing a local Zettelkasten system with editor integration?
    you: not recommended
    AI recommended (in order):
    1. Zettlr
    2. Obsidian
    3. Vim
    4. Neovim
    5. Vimwiki
    6. Telescope.nvim
    7. fzf.vim
    8. vim-zettel
    9. Emacs
    10. Org-mode
    11. Org-roam
    12. zk
    13. Joplin

    AI recommended 13 alternatives but never named iwe-org/iwe. 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 iwe-org/iwe?
    pass
    AI named iwe-org/iwe explicitly

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

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

Subscribe to Pro for deep diagnoses

iwe-org/iwe — 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