RRepoGEO

REPOGEO REPORT · LITE

jsgrrchg/NeverWrite

Default branch main · commit c63b165f · scanned 6/13/2026, 7:21:43 PM

GitHub: 690 stars · 69 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 jsgrrchg/NeverWrite, 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 README's opening to clearly define NeverWrite's purpose

    Why:

    CURRENT
    Important note about Claude subscription usage in NeverWrite starting June 15, 2026
    COPY-PASTE FIX
    NeverWrite is an AI-powered knowledge workspace designed for interconnected knowledge management and personal knowledge graph building, serving users who seek an intelligent alternative to tools like Obsidian and Logseq. It is currently in active development with a roadmap towards 1.0, focusing on ACP provider compatibility and local LLM support.
  • mediumabout#2
    Update repository description for clarity and accurate categorization

    Why:

    CURRENT
    The bastard son between Cursor and Obsidian
    COPY-PASTE FIX
    An AI-powered knowledge workspace for interconnected knowledge management, blending the best of intelligent assistance with Obsidian-style note-taking.
  • mediumtopics#3
    Correct typo and add more specific topics

    Why:

    CURRENT
    acp, ai, graph, knwoledege, markdown, obsidian-vault
    COPY-PASTE FIX
    ai, knowledge-management, personal-knowledge-graph, markdown, obsidian-vault, llm, agentic-ai

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 jsgrrchg/NeverWrite
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. Notion · recommended 2×
  4. logseq/logseq · recommended 1×
  5. Roam Research · recommended 1×
  • CATEGORY QUERY
    What are the best AI-powered tools for building and managing a personal knowledge graph?
    you: not recommended
    AI recommended (in order):
    1. Obsidian
    2. Logseq (logseq/logseq)
    3. Mem.ai
    4. Roam Research
    5. Notion
    6. TiddlyWiki (TiddlyWiki/TiddlyWiki5)
    7. Athens Research (athensresearch/athens)

    AI recommended 7 alternatives but never named jsgrrchg/NeverWrite. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking an AI-enhanced markdown note-taking application for interconnected knowledge management.
    you: not recommended
    AI recommended (in order):
    1. Mem.ai
    2. Obsidian
    3. Notion
    4. Logseq
    5. Craft

    AI recommended 5 alternatives but never named jsgrrchg/NeverWrite. 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 jsgrrchg/NeverWrite?
    pass
    AI named jsgrrchg/NeverWrite explicitly

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

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

Subscribe to Pro for deep diagnoses

jsgrrchg/NeverWrite — 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