RRepoGEO

REPOGEO REPORT · LITE

imhuso/cunzhi

Default branch main · commit f34fbea3 · scanned 5/24/2026, 7:37:13 AM

GitHub: 1,370 stars · 169 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 imhuso/cunzhi, 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
    Clarify the tool's nature in the README's opening paragraph

    Why:

    CURRENT
    还在为 AI 助手总是提前结束对话而抓狂吗？明明还有很多要聊，它却说"还有什么需要帮助的吗？"**寸止** 专治这个毛病！
    COPY-PASTE FIX
    还在为 AI 助手总是提前结束对话而抓狂吗？明明还有很多要聊，它却说"还有什么需要帮助的吗？"**寸止** 是一款命令行工具，专治这个毛病！
  • hightopics#2
    Expand and refine repository topics

    Why:

    CURRENT
    ai, mcp
    COPY-PASTE FIX
    ai, ai-assistant, conversation-management, cli-tool, prompt-engineering, chatbot-utility, developer-tools
  • mediumhomepage#3
    Add a homepage URL to the repository metadata

    Why:

    COPY-PASTE FIX
    https://github.com/imhuso/cunzhi

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 imhuso/cunzhi
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
RasaHQ/rasa
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. RasaHQ/rasa · recommended 2×
  2. microsoft/BotFramework-Composer · recommended 2×
  3. Dialogflow · recommended 1×
  4. Amazon Lex · recommended 1×
  5. OpenAI API · recommended 1×
  • CATEGORY QUERY
    How to stop AI assistants from ending conversations too quickly?
    you: not recommended
    AI recommended (in order):
    1. Dialogflow
    2. Rasa (RasaHQ/rasa)
    3. Microsoft Bot Framework Composer (microsoft/BotFramework-Composer)
    4. Amazon Lex
    5. OpenAI API
    6. NLTK (nltk/nltk)
    7. SpaCy (explosion/spaCy)

    AI recommended 7 alternatives but never named imhuso/cunzhi. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Tools to extend AI chatbot dialogues and manage conversation flow for deeper discussions?
    you: not recommended
    AI recommended (in order):
    1. Rasa Open Source (RasaHQ/rasa)
    2. Google Dialogflow CX
    3. Microsoft Bot Framework Composer (microsoft/BotFramework-Composer)
    4. Cognigy.AI
    5. Voiceflow
    6. OpenAI GPT
    7. LangChain (langchain-ai/langchain)

    AI recommended 7 alternatives but never named imhuso/cunzhi. 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 imhuso/cunzhi?
    pass
    AI named imhuso/cunzhi explicitly

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

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

Subscribe to Pro for deep diagnoses

imhuso/cunzhi — 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