RRepoGEO

REPOGEO REPORT · LITE

yliust/Tactile

Default branch main · commit 2581abc0 · scanned 6/14/2026, 9:57:50 AM

GitHub: 621 stars · 13 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 yliust/Tactile, 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
    Update the 'About' description for clarity and keywords

    Why:

    CURRENT
    Tactile: an accessibility-first operating layer for agents.
    COPY-PASTE FIX
    Tactile: an accessibility-first operating layer for AI agents to interact with software UIs using semantic information, not pixels or screenshots.
  • hightopics#2
    Add relevant topics to improve categorization

    Why:

    COPY-PASTE FIX
    ai-agents, accessibility, ui-automation, semantic-ui, agent-framework, assistive-technology
  • mediumreadme#3
    Clarify the project's license in the README

    Why:

    COPY-PASTE FIX
    ## License
This project is licensed under [insert specific license name(s) here, e.g., 'a custom license combining MIT and Apache-2.0 terms']. Please see the [LICENSE](LICENSE) file 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 yliust/Tactile
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
microsoft/playwright
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. microsoft/playwright · recommended 2×
  2. SeleniumHQ/selenium · recommended 2×
  3. Microsoft UI Automation (UIA) · recommended 2×
  4. appium/appium · recommended 2×
  5. Apple Accessibility API (AXAPI) · recommended 1×
  • CATEGORY QUERY
    How can AI agents interact with software UIs using semantic information instead of pixels?
    you: not recommended
    AI recommended (in order):
    1. Playwright (microsoft/playwright)
    2. Selenium (SeleniumHQ/selenium)
    3. Microsoft UI Automation (UIA)
    4. Apple Accessibility API (AXAPI)
    5. Android Accessibility Framework
    6. Appium (appium/appium)
    7. OpenAI's GPT-4V

    AI recommended 7 alternatives but never named yliust/Tactile. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for a tool to improve agent automation by leveraging UI accessibility data.
    you: not recommended
    AI recommended (in order):
    1. Playwright (microsoft/playwright)
    2. Puppeteer (puppeteer/puppeteer)
    3. Appium (appium/appium)
    4. Microsoft UI Automation (UIA)
    5. WinAppDriver (microsoft/WinAppDriver)
    6. Selenium (SeleniumHQ/selenium)
    7. Axe-core (dequelabs/axe-core)
    8. Coded UI Test (CUIT)
    9. TestComplete
    10. Ranorex

    AI recommended 10 alternatives but never named yliust/Tactile. 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 yliust/Tactile?
    pass
    AI named yliust/Tactile explicitly

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

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

Subscribe to Pro for deep diagnoses

yliust/Tactile — 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