RRepoGEO

REPOGEO REPORT · LITE

Bolin97/MedArk

Default branch main · commit 9629fd96 · scanned 6/8/2026, 3:02:41 AM

GitHub: 663 stars · 18 forks

AI VISIBILITY SCORE
23 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 0 warn · 1 fail
Objective metadata checks
AI knows your name
2 / 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 Bolin97/MedArk, 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 concise introductory paragraph to the README

    Why:

    CURRENT
    The README immediately follows the H1 with '## Model and Data Access'.
    COPY-PASTE FIX
    Add the following paragraph directly after the H1: "MedArk presents an innovative framework for Large Language Models (LLMs) to proactively ask clarifying questions in medical multi-turn dialogues, especially when dealing with imperfect patient information. This repository provides the code and models for our SIGIR'25 paper, enabling LLMs to decide between 'ask' or 'tell' actions by self-reasoning and knowledge retrieval."
  • hightopics#2
    Add relevant topics to improve discoverability and categorization

    Why:

    CURRENT
    (none)
    COPY-PASTE FIX
    llm, large-language-models, medical-llm, medical-dialogue, question-answering, proactive-ai, nlp, research-paper, sigir25
  • mediumlicense#3
    Add a LICENSE file to the repository

    Why:

    CURRENT
    (no LICENSE file detected — the repo has no recognizable license)
    COPY-PASTE FIX
    Create a LICENSE file (e.g., MIT or Apache-2.0) in the root of the repository to clearly state the terms of use for MedArk.

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 Bolin97/MedArk
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
GPT-4
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. GPT-4 · recommended 1×
  2. Claude 3 Opus · recommended 1×
  3. Llama 3 · recommended 1×
  4. Med-PaLM 2 · recommended 1×
  5. langchain-ai/langchain · recommended 1×
  • CATEGORY QUERY
    How can I build an LLM for medical dialogues that proactively asks clarifying questions?
    you: not recommended
    AI recommended (in order):
    1. GPT-4
    2. Claude 3 Opus
    3. Llama 3
    4. Med-PaLM 2
    5. LangChain (langchain-ai/langchain)
    6. LlamaIndex (run-llama/llama_index)
    7. MIMIC-III/IV
    8. Hugging Face PEFT library (huggingface/peft)
    9. spaCy (explosion/spaCy)
    10. ClinicalBERT/BioBERT
    11. Hugging Face Transformers (huggingface/transformers)
    12. Sentence Transformers (UKPLab/sentence-transformers)
    13. Chroma (chroma-core/chroma)
    14. Pinecone
    15. Weaviate (weaviate/weaviate)
    16. ICD-10/SNOMED CT
    17. UMLS

    AI recommended 17 alternatives but never named Bolin97/MedArk. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What framework helps LLMs decide to ask questions or provide answers in healthcare conversations?
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LlamaIndex
    3. Haystack
    4. Microsoft Guidance
    5. OpenAI Function Calling
    6. Rasa

    AI recommended 6 alternatives but never named Bolin97/MedArk. This is the gap to close.

    Show full AI answer

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

Subscribe to Pro for deep diagnoses

Bolin97/MedArk — 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