RRepoGEO

REPOGEO REPORT · LITE

mohsen1/yek

Default branch main · commit d49c0ca9 · scanned 5/24/2026, 9:48:03 AM

GitHub: 2,448 stars · 66 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 mohsen1/yek, 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 H1 to specify category

    Why:

    CURRENT
    # `yek`
    COPY-PASTE FIX
    # `yek`: A Rust CLI for LLM-Optimized Codebase Serialization
  • mediumreadme#2
    Add a comparison section to the README

    Why:

    COPY-PASTE FIX
    Add the following section to your README, ideally after the initial description:
    ```markdown
    ## Comparison to other tools
    
    While tools like `cat`, `tree`, `git ls-files`, and `ripgrep` can list or combine files, `yek` is specifically designed for **LLM consumption**. It goes beyond simple concatenation by:
    - **Respecting `.gitignore` and inferring additional ignore patterns** (binary, large files).
    - **Leveraging Git history** to prioritize more important files, ensuring they appear later in the output for better LLM attention.
    - **Automatically streaming content** when piped, and supporting multiple directories and glob patterns.
    - **Providing a structured, delimited output** (`>>>> filename`) optimized for LLM context parsing.
    
    `yek` is not a general-purpose file lister or search tool; it's a specialized serialization utility for preparing codebases for AI models.
    ```
  • lowhomepage#3
    Add a homepage URL to the repository's 'About' section

    Why:

    COPY-PASTE FIX
    https://github.com/mohsen1/yek

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 mohsen1/yek
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
git ls-files
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. git ls-files · recommended 2×
  2. ripgrep · recommended 2×
  3. tree · recommended 1×
  4. cat · recommended 1×
  5. xargs · recommended 1×
  • CATEGORY QUERY
    How to serialize a codebase into a single text file for large language model input?
    you: not recommended
    AI recommended (in order):
    1. tree
    2. cat
    3. git ls-files
    4. xargs
    5. find
    6. codetree
    7. ripgrep

    AI recommended 7 alternatives but never named mohsen1/yek. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Fast Rust utility to combine source code files, respecting gitignore and history, for AI context?
    you: not recommended
    AI recommended (in order):
    1. git-sizer
    2. git2-rs
    3. ripgrep
    4. git ls-files
    5. git-archive
    6. cargo-binstall
    7. crates.io
    8. git-cliff

    AI recommended 8 alternatives but never named mohsen1/yek. 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 mohsen1/yek?
    pass
    AI named mohsen1/yek explicitly

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

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

Subscribe to Pro for deep diagnoses

mohsen1/yek — 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