Individual skill
red-teaming-llms
Red-team LLM systems methodically — scoping, adversarial test design, vulnerability classification, and remediation tracking. Use when you need to find weaknesses before attackers do. Defensive security practice only.
skills/red-teaming-llms/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 54
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- security Derived category
- design Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,043 bytes
Read excerpt
# Red-Teaming LLMs
Red-teaming is structured adversarial testing: deliberately trying to make the system fail —
produce harmful outputs, leak data, bypass controls, get hijacked — so you can fix it before
deployment. It's a security discipline, not mischief: scoped, documented, and aimed at remediation.
## Overview
A red-team engagement: define scope (what system, what threat model, what's off-limits), design
adversarial tests across vulnerability classes, execute methodically while documenting everything,
classify findings by severity, and track remediation to closure. The output isn't a list of
"gotchas" — it's a risk assessment with prioritized fixes and re-test results.
## When to use