RRepoGEO

REPOGEO REPORT · LITE

RhysSullivan/executor

Default branch main · commit 382dcd65 · scanned 5/23/2026, 1:12:27 AM

GitHub: 1,814 stars · 113 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 RhysSullivan/executor, 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

2 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • hightopics#1
    Add specific topics to improve AI categorization

    Why:

    CURRENT
    (none)
    COPY-PASTE FIX
    ai-agents, function-calling, tool-management, api-integration, llm-tools, openapi, graphql
  • mediumreadme#2
    Strengthen the problem statement in the README's opening

    Why:

    CURRENT
    The integration layer for AI agents. One catalog for every tool, shared across every agent you use.
    COPY-PASTE FIX
    The integration layer for AI agents. One catalog for every tool, shared across every agent you use. AI agents often struggle with secure, unified access to diverse external tools and APIs. Executor solves this by providing a single, secure catalog for all your functions – OpenAPI, GraphQL, MCP, or custom JavaScript – making them instantly available to any agent.

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 RhysSullivan/executor
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
OpenAI Function Calling
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. OpenAI Function Calling · recommended 2×
  2. langchain-ai/langchain · recommended 1×
  3. run-llama/llama_index · recommended 1×
  4. Google's Gemini Function Calling · recommended 1×
  5. AWS Lambda · recommended 1×
  • CATEGORY QUERY
    How can I give my AI agents access to diverse APIs and custom functions securely?
    you: not recommended
    AI recommended (in order):
    1. LangChain (langchain-ai/langchain)
    2. LlamaIndex (run-llama/llama_index)
    3. OpenAI Function Calling
    4. Google's Gemini Function Calling
    5. AWS Lambda
    6. Google Cloud Functions
    7. Azure Functions
    8. FastAPI (tiangolo/fastapi)
    9. Flask (pallets/flask)
    10. AWS Secrets Manager
    11. Google Secret Manager
    12. HashiCorp Vault (hashicorp/vault)
    13. NGINX (nginx/nginx)
    14. Kong (Kong/kong)
    15. Zapier NLA

    AI recommended 15 alternatives but never named RhysSullivan/executor. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What's the best way to manage a shared catalog of tools for multiple AI agents?
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LlamaIndex
    3. OpenAI Function Calling
    4. Kong
    5. Apigee
    6. FastAPI
    7. Node.js Express
    8. Faiss
    9. Hnswlib
    10. Redis

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

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

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

Subscribe to Pro for deep diagnoses

RhysSullivan/executor — 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