RRepoGEO

REPOGEO REPORT · LITE

Goochbeater/Spiritual-Spell-Red-Teaming

Default branch main · commit d2188432 · scanned 5/25/2026, 3:32:55 PM

GitHub: 1,465 stars · 274 forks

AI VISIBILITY SCORE
17 /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
1 / 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 Goochbeater/Spiritual-Spell-Red-Teaming, 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
    Replace garbled README content with clear, descriptive text

    Why:

    COPY-PASTE FIX
    This repository provides methods and resources for red-teaming Large Language Models (LLMs), with a primary focus on jailbreaking and identifying safety vulnerabilities in models like Claude. It aims to explore prompt injection techniques and bypass content restrictions to improve LLM security.
  • hightopics#2
    Add relevant topics for LLM red-teaming and security

    Why:

    CURRENT
    (none)
    COPY-PASTE FIX
    llm-red-teaming, prompt-injection, llm-security, jailbreaking, claude, ai-safety, adversarial-ai, content-moderation-bypass
  • mediumlicense#3
    Add a LICENSE file to clarify usage terms

    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, and add its content. For example, for MIT: 'MIT License\n\nCopyright (c) [YEAR] [COPYRIGHT HOLDER]\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the "Software"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.')

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 Goochbeater/Spiritual-Spell-Red-Teaming
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Garak
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Garak · recommended 1×
  2. LLM Guard · recommended 1×
  3. Prompt Security Toolkit (PST) · recommended 1×
  4. OWASP Top 10 for LLM Applications (OWASP LLM Top 10) · recommended 1×
  5. Red Teaming with Human Experts · recommended 1×
  • CATEGORY QUERY
    How can I test large language models for prompt injection and safety vulnerabilities?
    you: not recommended
    AI recommended (in order):
    1. Garak
    2. LLM Guard
    3. Prompt Security Toolkit (PST)
    4. OWASP Top 10 for LLM Applications (OWASP LLM Top 10)
    5. Red Teaming with Human Experts
    6. Adversarial GLUE (AdvGLUE)
    7. OpenAI API
    8. Hugging Face Transformers

    AI recommended 8 alternatives but never named Goochbeater/Spiritual-Spell-Red-Teaming. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What tools help with red teaming AI models to bypass content restrictions?
    you: not recommended
    AI recommended (in order):
    1. Adversarial Robustness Toolbox (ART) (IBM/adversarial-robustness-toolbox)
    2. TextAttack (TextAttack/TextAttack)
    3. CleverHans (tensorflow/cleverhans)
    4. OpenAI Evals (openai/evals)
    5. Hugging Face Transformers (huggingface/transformers)
    6. Guidance (microsoft/guidance)
    7. Atheris (google/atheris)
    8. American Fuzzy Lop - AFL (google/AFL)

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

Subscribe to Pro for deep diagnoses

Goochbeater/Spiritual-Spell-Red-Teaming — 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