RRepoGEO

REPOGEO REPORT · LITE

ZTE-AICloud/Co-Sight

Default branch master · commit 6e48d7a7 · scanned 6/6/2026, 10:31:58 AM

GitHub: 1,000 stars · 278 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 ZTE-AICloud/Co-Sight, 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
    Add a concise repository description

    Why:

    COPY-PASTE FIX
    An open-source system for generating high-quality, customizable reports using affordable large language models in private environments.
  • highreadme#2
    Reposition README H1 to clearly state core function

    Why:

    CURRENT
    ## 🚀 Still worried about the invitation code? One-click deployment of Co-Sight to quickly build your own Manus-like system!
    COPY-PASTE FIX
    ## 🚀 Co-Sight: One-click deployment for your private AI-powered report generation system
  • mediumtopics#3
    Update repository topics for better categorization

    Why:

    CURRENT
    agent, aicloud, aim, zte
    COPY-PASTE FIX
    ai, llm, report-generation, private-ai, business-intelligence, generative-ai, agent-system

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 ZTE-AICloud/Co-Sight
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Llama 3
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Llama 3 · recommended 2×
  2. Ollama · recommended 2×
  3. LM Studio · recommended 2×
  4. LangChain · recommended 1×
  5. LlamaIndex · recommended 1×
  • CATEGORY QUERY
    Looking for an open-source solution to build a private AI agent system for report generation.
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LlamaIndex
    3. Llama 3
    4. Mistral
    5. Mixtral
    6. Ollama
    7. LM Studio
    8. transformers
    9. Haystack
    10. AutoGPT
    11. BabyAGI
    12. Open-WebUI
    13. Transformers Agents

    AI recommended 13 alternatives but never named ZTE-AICloud/Co-Sight. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    How to generate high-quality business reports using affordable large language models privately?
    you: not recommended
    AI recommended (in order):
    1. Llama 3
    2. Ollama
    3. LM Studio
    4. Mistral 7B
    5. Mixtral 8x7B
    6. Gemma
    7. Google Cloud Vertex AI
    8. Vertex AI Model Garden
    9. Llama 2
    10. Hugging Face Inference Endpoints
    11. Hugging Face Hub
    12. AWS
    13. Azure
    14. Llama.cpp
    15. ChromaDB
    16. Weaviate

    AI recommended 16 alternatives but never named ZTE-AICloud/Co-Sight. 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 ZTE-AICloud/Co-Sight?
    pass
    AI named ZTE-AICloud/Co-Sight explicitly

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

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

Subscribe to Pro for deep diagnoses

ZTE-AICloud/Co-Sight — 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