RRepoGEO

REPOGEO REPORT · LITE

principia-ai/WriteHERE

Default branch main · commit 0b78fcb9 · scanned 6/9/2026, 12:52:40 AM

GitHub: 930 stars · 143 forks

AI VISIBILITY SCORE
35 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 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 principia-ai/WriteHERE, 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 sentence to clarify its role as an AI writing system

    Why:

    CURRENT
    WriteHERE is an open-source framework that revolutionizes long-form writing through human-like adaptive planning.
    COPY-PASTE FIX
    WriteHERE is an open-source AI writing project that provides a complete system for generating long-form content, revolutionizing the process through human-like adaptive planning.
  • highlicense#2
    Add a LICENSE file to the repository root

    Why:

    COPY-PASTE FIX
    Create a `LICENSE` file in the repository root containing the text of the MIT License, as suggested by the link in the README.
  • mediumtopics#3
    Refine repository topics for better specificity

    Why:

    CURRENT
    agentic-workflow, ai-agents, ai-writing, creative-writing-ai, deep-research, planning
    COPY-PASTE FIX
    ai-writing, long-form-writing, ai-writing-system, recursive-planning, agentic-ai-writing, deep-research, creative-writing-ai, technical-writing-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 principia-ai/WriteHERE
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
LangChain
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. LangChain · recommended 1×
  2. LlamaIndex · recommended 1×
  3. Haystack · recommended 1×
  4. OpenAI's API · recommended 1×
  5. Hugging Face Transformers · recommended 1×
  • CATEGORY QUERY
    What open-source AI frameworks assist with adaptive planning for complex long-form writing tasks?
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LlamaIndex
    3. Haystack
    4. OpenAI's API
    5. Hugging Face Transformers

    AI recommended 5 alternatives but never named principia-ai/WriteHERE. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    AI agent frameworks for recursive planning and integrating deep research into creative or technical writing?
    you: not recommended
    AI recommended (in order):
    1. LangChain (langchain-ai/langchain)
    2. LlamaIndex (run-llama/llama_index)
    3. AutoGPT (Significant-Gravitas/AutoGPT)
    4. BabyAGI (yoheinakajima/babyagi)
    5. CrewAI (joaomdmoura/crewAI)
    6. Microsoft AutoGen (microsoft/autogen)
    7. Haystack (deepset-ai/haystack)

    AI recommended 7 alternatives but never named principia-ai/WriteHERE. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    warn

    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 principia-ai/WriteHERE?
    pass
    AI named principia-ai/WriteHERE explicitly

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

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

Subscribe to Pro for deep diagnoses

principia-ai/WriteHERE — 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