RRepoGEO

REPOGEO REPORT · LITE

elyase/awesome-gpt3

Default branch main · commit 90a82d38 · scanned 8/11/2026, 1:46:39 AM

GitHub: 4,520 stars · 345 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)

3 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
20 /100
Critical
Rule findings
1 pass · 0 warn · 1 fail
Objective metadata checks
AI knows your name
0 / 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 elyase/awesome-gpt3, 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.

CATEGORY VISIBILITY UNAVAILABLE

The category visibility step did not produce results for this scan (the LLM may have been unreachable). Re-run the diagnosis to get the full GEO picture.

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 elyase/awesome-gpt3?
    skipped
    AI did not name elyase/awesome-gpt3 — likely talking about a different project

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

  • If a team adopts elyase/awesome-gpt3 in production, what risks or prerequisites should they evaluate first?
    skipped
    AI did not name elyase/awesome-gpt3 — likely talking about a different project

    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 elyase/awesome-gpt3 solve, and who is the primary audience?
    skipped
    AI did not name elyase/awesome-gpt3 — likely talking about a different project

    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 elyase/awesome-gpt3. 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/elyase/awesome-gpt3.svg)](https://repogeo.com/en/r/elyase/awesome-gpt3)
HTML
<a href="https://repogeo.com/en/r/elyase/awesome-gpt3"><img src="https://repogeo.com/badge/elyase/awesome-gpt3.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

elyase/awesome-gpt3 — 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