RRepoGEO

REPOGEO REPORT · LITE

berabuddies/Semia

Default branch main · commit 379bc25f · scanned 6/17/2026, 1:21:24 AM

GitHub: 545 stars · 59 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 berabuddies/Semia, 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
    Strengthen the README's opening to explicitly state the project's domain and purpose

    Why:

    CURRENT
    # Semia
    
    > **Security audit for AI agent skills.** Know what a skill *can* do before you trust it.
    COPY-PASTE FIX
    # Semia
    
    > **Semia is a dedicated static analysis tool for AI agent skills, providing a crucial security audit to ensure safety and trustworthiness before deployment.** Know what a skill *can* do before you trust it.
  • highhomepage#2
    Add a homepage URL to the repository metadata

    Why:

    COPY-PASTE FIX
    https://github.com/berabuddies/Semia
  • mediumtopics#3
    Expand repository topics to include relevant AI agent security and static analysis terms

    Why:

    CURRENT
    claude-code, codex, openclaw, security, skill-scanner, static-analysis
    COPY-PASTE FIX
    claude-code, codex, openclaw, security, skill-scanner, static-analysis, ai-agents, agent-security, llm-security, vulnerability-detection, code-security

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 berabuddies/Semia
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Snyk Code
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Snyk Code · recommended 2×
  2. OpenAI Playground · recommended 1×
  3. Azure OpenAI Studio · recommended 1×
  4. LangChain Expression Language (LCEL) · recommended 1×
  5. Semantic Kernel's Planner · recommended 1×
  • CATEGORY QUERY
    How can I ensure AI agent skills are safe before deploying them with my credentials?
    you: not recommended
    AI recommended (in order):
    1. OpenAI Playground
    2. Azure OpenAI Studio
    3. LangChain Expression Language (LCEL)
    4. Semantic Kernel's Planner
    5. Docker
    6. Kubernetes
    7. OWASP ZAP (Zed Attack Proxy)
    8. Burp Suite Community Edition
    9. GitGuardian
    10. Snyk Code
    11. HashiCorp Vault
    12. AWS Secrets Manager
    13. Azure Key Vault
    14. Google Secret Manager
    15. Datadog
    16. Splunk
    17. Elastic Stack

    AI recommended 17 alternatives but never named berabuddies/Semia. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What tools perform static analysis to detect potential vulnerabilities in AI agent skill code?
    you: not recommended
    AI recommended (in order):
    1. Semgrep (returntocorp/semgrep)
    2. Bandit (PyCQA/bandit)
    3. ESLint (eslint/eslint)
    4. SonarQube (SonarSource/sonarqube)
    5. CodeQL (github/codeql)
    6. Snyk Code

    AI recommended 6 alternatives but never named berabuddies/Semia. 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 berabuddies/Semia?
    pass
    AI named berabuddies/Semia explicitly

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

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

Subscribe to Pro for deep diagnoses

berabuddies/Semia — 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