RRepoGEO

REPOGEO REPORT · LITE

doccker/cc-use-exp

Default branch main · commit 05c08074 · scanned 6/11/2026, 2:42:27 AM

GitHub: 770 stars · 77 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
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 doccker/cc-use-exp, 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
    Add a clear English tagline to the README and clarify 'doccker' vs 'docker'

    Why:

    CURRENT
    The current README starts with a Chinese H1 and description, leading to AI misinterpretation.
    COPY-PASTE FIX
    Add the following text at the very top of your README, before the existing H1:

"AI Coding Assistant Configuration System: Layered configuration templates for Claude Code, Gemini CLI, Codex, Cursor, and GitHub Copilot. This project is NOT related to Docker."
  • mediumabout#2
    Add a homepage URL to the repository settings

    Why:

    COPY-PASTE FIX
    Set the 'Homepage' field in your repository settings to: `https://github.com/doccker/cc-use-exp`
  • mediumlicense#3
    Clarify the project's license in the README

    Why:

    COPY-PASTE FIX
    Add a new section to your README, for example, after '快速部署' (Quick Deployment):

"## License
This project is licensed under [Specify License Name(s) and terms, e.g., a custom license or a combination of licenses]. Please refer to the [LICENSE file](./LICENSE) for full details."

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 doccker/cc-use-exp
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
devcontainers/spec
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. devcontainers/spec · recommended 1×
  2. NixOS/nix · recommended 1×
  3. conda/conda · recommended 1×
  4. docker/compose · recommended 1×
  5. python-poetry/poetry · recommended 1×
  • CATEGORY QUERY
    Seeking a way to unify setup for various AI programming helpers across different IDEs.
    you: not recommended
    AI recommended (in order):
    1. Dev Containers (devcontainers/spec)
    2. Nix (NixOS/nix)
    3. Conda (conda/conda)
    4. Docker Compose (docker/compose)
    5. Poetry (python-poetry/poetry)
    6. PDM (pdm-project/pdm)
    7. GitHub Codespaces
    8. Gitpod (gitpod-io/gitpod)

    AI recommended 8 alternatives but never named doccker/cc-use-exp. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    How to implement maintainable rules and workflows for AI-powered development tools?
    you: not recommended
    AI recommended (in order):
    1. Temporal (temporalio/temporal)
    2. Apache Airflow (apache/airflow)
    3. Prefect (PrefectHQ/prefect)
    4. Kubeflow Pipelines (kubeflow/pipelines)
    5. AWS Step Functions
    6. Azure Logic Apps
    7. GitHub Actions

    AI recommended 7 alternatives but never named doccker/cc-use-exp. 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 doccker/cc-use-exp?
    pass
    AI named doccker/cc-use-exp explicitly

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

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

Subscribe to Pro for deep diagnoses

doccker/cc-use-exp — 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