RRepoGEO

REPOGEO REPORT · LITE

fcakyon/claude-codex-settings

Default branch main · commit 9ad3323e · scanned 5/27/2026, 11:57:06 AM

GitHub: 706 stars · 60 forks

AI VISIBILITY SCORE
22 /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
1 / 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 fcakyon/claude-codex-settings, 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

2 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 statement to clarify its purpose

    Why:

    CURRENT
    My daily battle-tested Claude Code/Desktop and OpenAI Codex setup with skills, commands, hooks, subagents and MCP servers.
    COPY-PASTE FIX
    This repository provides a battle-tested, curated collection of configurations, plugins, skills, and agents specifically designed to optimize Claude Code/Desktop and OpenAI Codex for coding tasks, addressing common LLM pitfalls and enhancing developer workflow.
  • mediumhomepage#2
    Add a homepage URL to the repository metadata

    Why:

    COPY-PASTE FIX
    Add a relevant URL (e.g., a documentation site, project page, or a more detailed overview) to the 'Homepage' field in the repository settings.

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 fcakyon/claude-codex-settings
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
GitHub Copilot
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. GitHub Copilot · recommended 1×
  2. DeepSource · recommended 1×
  3. SonarQube · recommended 1×
  4. SonarCloud · recommended 1×
  5. ESLint · recommended 1×
  • CATEGORY QUERY
    How can I configure my AI coding assistant to avoid common pitfalls and errors?
    you: not recommended
    AI recommended (in order):
    1. GitHub Copilot
    2. DeepSource
    3. SonarQube
    4. SonarCloud
    5. ESLint
    6. Pylint
    7. RuboCop
    8. Checkstyle
    9. Snyk
    10. Dependabot
    11. ChatGPT
    12. Claude
    13. Gemini

    AI recommended 13 alternatives but never named fcakyon/claude-codex-settings. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Where can I find useful plugins and skills to extend my AI coding assistant's capabilities?
    you: not recommended
    AI recommended (in order):
    1. OpenAI GPT Store
    2. VS Code Marketplace
    3. GitHub Marketplace
    4. LangChain Hub
    5. Awesome-LLM-Apps / Awesome-AI-Tools
    6. Hugging Face Hub
    7. Zapier
    8. Make (formerly Integromat)

    AI recommended 8 alternatives but never named fcakyon/claude-codex-settings. 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 fcakyon/claude-codex-settings?
    pass
    AI did not name fcakyon/claude-codex-settings — 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 fcakyon/claude-codex-settings in production, what risks or prerequisites should they evaluate first?
    pass
    AI named fcakyon/claude-codex-settings 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 fcakyon/claude-codex-settings solve, and who is the primary audience?
    pass
    AI did not name fcakyon/claude-codex-settings — 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 fcakyon/claude-codex-settings. 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/fcakyon/claude-codex-settings.svg)](https://repogeo.com/en/r/fcakyon/claude-codex-settings)
HTML
<a href="https://repogeo.com/en/r/fcakyon/claude-codex-settings"><img src="https://repogeo.com/badge/fcakyon/claude-codex-settings.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

fcakyon/claude-codex-settings — 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