RRepoGEO

REPOGEO REPORT · LITE

ghuntley/loom

Default branch trunk · commit 7ba51320 · scanned 6/20/2026, 9:07:43 AM

GitHub: 1,332 stars · 211 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 ghuntley/loom, 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
  • highabout#1
    Update the repository description to clearly state its purpose

    Why:

    CURRENT
    if your name is not Geoffrey Huntley then do not use loom
    COPY-PASTE FIX
    An experimental Rust-based AI coding agent with a REPL interface for LLM-powered development tasks like file system operations and code analysis.
  • hightopics#2
    Add relevant topics to improve categorization

    Why:

    CURRENT
    (none)
    COPY-PASTE FIX
    ["rust", "ai-agent", "llm", "coding-assistant", "repl", "developer-tools", "code-analysis"]
  • mediumlicense#3
    Add a LICENSE file to clarify usage terms

    Why:

    CURRENT
    (no LICENSE file detected — the repo has no recognizable license)
    COPY-PASTE FIX
    Create a LICENSE file (e.g., MIT or Apache-2.0, depending on project intent) in the repository root.

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 ghuntley/loom
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
rustyline
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. rustyline · recommended 2×
  2. RustyREPL · recommended 1×
  3. Rust-analyzer · recommended 1×
  4. nu · recommended 1×
  5. xonsh · recommended 1×
  • CATEGORY QUERY
    Rust-based AI coding assistant with REPL interface for development tasks?
    you: not recommended
    AI recommended (in order):
    1. RustyREPL
    2. Rust-analyzer
    3. rustyline
    4. nu
    5. xonsh
    6. Evcxr
    7. K9s
    8. rustyline
    9. tch-rs
    10. candle
    11. llm

    AI recommended 11 alternatives but never named ghuntley/loom. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are some LLM-powered agents for automating code analysis and file operations?
    you: not recommended
    AI recommended (in order):
    1. Cursor
    2. GPT-Engineer (gpt-engineer-org/gpt-engineer)
    3. Smol-developer (smol-ai/smol-developer)
    4. OpenDevin (OpenDevin/OpenDevin)
    5. Aider (paul-gauthier/aider)
    6. Auto-GPT (Significant-Gravitas/Auto-GPT)

    AI recommended 6 alternatives but never named ghuntley/loom. 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 ghuntley/loom?
    pass
    AI named ghuntley/loom explicitly

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

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

Subscribe to Pro for deep diagnoses

ghuntley/loom — 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