RRepoGEO

REPOGEO REPORT · LITE

BehiSecc/VibeSec-Skill

Default branch main · commit 0590993b · scanned 6/3/2026, 7:38:20 AM

GitHub: 912 stars · 81 forks

AI VISIBILITY SCORE
28 /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
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 BehiSecc/VibeSec-Skill, 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
    Reposition the README's opening to clarify 'AI coding skill'

    Why:

    CURRENT
    An AI skill that brings 5+ years of bug bounty hunting experience directly into your AI coding workflow - so LLM models write secure code from the start.
    COPY-PASTE FIX
    An AI skill for Large Language Models (LLMs) that brings 5+ years of bug bounty hunting experience directly into your AI coding workflow - so your LLM models write secure code from the start.
  • hightopics#2
    Add relevant topics for AI security and secure coding

    Why:

    COPY-PASTE FIX
    ai-security, llm-security, secure-coding, bug-bounty, vulnerability-detection, code-security, claude-skill, generative-ai
  • mediumhomepage#3
    Add the official project homepage URL

    Why:

    COPY-PASTE FIX
    https://vibesec.sh

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 BehiSecc/VibeSec-Skill
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 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Snyk Code · recommended 1×
  2. GitHub Copilot · recommended 1×
  3. GitHub Advanced Security · recommended 1×
  4. CodeQL · recommended 1×
  5. OWASP Top 10 · recommended 1×
  • CATEGORY QUERY
    How can I ensure my AI code assistant writes secure code and avoids common vulnerabilities?
    you: not recommended
    AI recommended (in order):
    1. Snyk Code
    2. GitHub Copilot
    3. GitHub Advanced Security
    4. CodeQL
    5. OWASP Top 10
    6. Checkmarx SAST (CxSAST)
    7. Sonatype Nexus Lifecycle

    AI recommended 7 alternatives but never named BehiSecc/VibeSec-Skill. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Tool to integrate bug bounty security best practices into my AI coding workflow?
    you: not recommended
    AI recommended (in order):
    1. Snyk
    2. OWASP Dependency-Check (owasp/dependency-check)
    3. Bandit (PyCQA/bandit)
    4. Semgrep (r2c/semgrep)
    5. GitHub Advanced Security (CodeQL) (github/codeql)
    6. TruffleHog (trufflesecurity/trufflehog)
    7. DeepCode AI

    AI recommended 7 alternatives but never named BehiSecc/VibeSec-Skill. 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 BehiSecc/VibeSec-Skill?
    pass
    AI named BehiSecc/VibeSec-Skill explicitly

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

  • If a team adopts BehiSecc/VibeSec-Skill in production, what risks or prerequisites should they evaluate first?
    pass
    AI named BehiSecc/VibeSec-Skill 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 BehiSecc/VibeSec-Skill solve, and who is the primary audience?
    pass
    AI did not name BehiSecc/VibeSec-Skill — 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?

Embed your GEO score

Drop this badge into the README of BehiSecc/VibeSec-Skill. 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/BehiSecc/VibeSec-Skill.svg)](https://repogeo.com/en/r/BehiSecc/VibeSec-Skill)
HTML
<a href="https://repogeo.com/en/r/BehiSecc/VibeSec-Skill"><img src="https://repogeo.com/badge/BehiSecc/VibeSec-Skill.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

BehiSecc/VibeSec-Skill — 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