Automated summary
This skill produces a structured adversarial analysis of a plan, system, or strategy to surface vulnerabilities, failure modes, and blind spots before a launch.
Strengths
- Highly structured output template covering attack surface, failure modes, adversary scenarios, assumption attacks, and blind spots
- Separates technical and human failure modes and ranks risks by severity
- Includes hardening recommendations with immediate actions and ongoing monitoring
- Pushes beyond criticism by hunting for cascading failures and making the target stronger
Limitations
- Quality depends heavily on the context the user supplies; thin input yields generic analysis
- Pure reasoning skill — it runs no actual tests or scans against the target system
- Severity and likelihood ratings are qualitative and uncalibrated
Use it before a launch, during a security-minded review, or whenever a plan looks too good to be true and needs to be stress-tested.
Avoid relying on it as a substitute for a real security audit, penetration test, or concrete code review.
Security analysis
SafeThe skill is a structured prompt for adversarial analysis and contains no executable commands, tool use, network access, credential handling, or destructive instructions. It poses no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Red team our plan to launch a public API next month: 3 endpoints, OAuth2, rate-limited, deployed on a single region. Find what could go wrong before we ship.Act as a red team and attack our strategy for migrating the user database to a new schema with zero downtime.Red team this authentication design: passwordless email links with 15-minute expiry and session cookies. What failure modes and attack vectors am I missing?name: redteam description: Red team adversarial analysis to find weaknesses, vulnerabilities, and failure modes. Use before launches, for security review, or when a plan feels too perfect. user-invocable: true
Red Team Analysis
Conduct an adversarial analysis to find weaknesses, vulnerabilities, and failure modes in a plan, system, or strategy.
Instructions
Think like an attacker. Your job is to break this, find the gaps, and expose what could go wrong. Be thorough and creative in your attacks.
Output Format
Target: [What we're attacking] Objective: [What would "breaking it" look like?]
Target Understanding
Summary of the Plan/System [Brief description of what we're analyzing]
Key Assumptions
- [Assumption 1]
- [Assumption 2]
Attack Surface Analysis
Entry Points / Vulnerabilities | Vector | Description | Severity | |--------|-------------|----------| | [attack vector] | [how it could be exploited] | Critical/High/Med/Low |
Failure Mode Analysis
Technical/Operational Failures
| Failure Mode | Trigger | Impact | |--------------|---------|--------| | [what could fail] | [what causes it] | [effect] |
Human Failures
| Failure Mode | Trigger | Impact | |--------------|---------|--------| | [human error] | [situation] | [consequence] |
Adversary Scenarios
If I wanted this to fail, I would...
Scenario 1: [Attack Name]
- Attack method: [how they'd do it]
- Likelihood of success: [High/Med/Low]
- Impact if successful: [consequences]
Scenario 2: [Attack Name]
- Attack method: [how]
- Likelihood of success: [High/Med/Low]
- Impact if successful: [consequences]
Assumption Attacks
| Assumption | Attack | What If Wrong? | |------------|--------|----------------| | [assumption] | [challenge to it] | [consequences] |
Blind Spot Analysis
What are we not seeing?
- [Blind spot 1]
- [Blind spot 2]
What are we too optimistic about?
- [Over-optimism 1]
Red Team Findings
Critical Vulnerabilities (Must Address)
| Vulnerability | Risk | Mitigation | |---------------|------|-----------| | [vulnerability] | [risk level] | [how to fix] |
High-Priority Concerns
| Concern | Recommendation | |---------|----------------| | [concern] | [recommendation] |
Hardening Recommendations
Immediate actions:
- [Action 1]
- [Action 2]
Ongoing monitoring:
- [What to watch]
Bottom Line
[Is this plan/system ready? What must change?]
Guidelines
- Be adversarial, not just critical
- Think creatively—real attackers don't follow rules
- Look for cascading failures
- The goal is to make it stronger, not just find flaws
$ARGUMENTS
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/red-team-analysis-ms47vp9x/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/red-team-analysis-ms47vp9x' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/red-team-analysis-ms47vp9x/download' --output '.skill-downloads/red-team-analysis-ms47vp9x/SKILL.md.part' && mv '.skill-downloads/red-team-analysis-ms47vp9x/SKILL.md.part' '.skill-downloads/red-team-analysis-ms47vp9x/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/red-team-analysis-ms47vp9x/SKILL.md' && test -s '.skill-downloads/red-team-analysis-ms47vp9x/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/redteam' && cp -R '.skill-downloads/red-team-analysis-ms47vp9x' '.claude/skills/redteam'Cursor
test -f '.skill-downloads/red-team-analysis-ms47vp9x/SKILL.md' && test -s '.skill-downloads/red-team-analysis-ms47vp9x/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/redteam' && cp -R '.skill-downloads/red-team-analysis-ms47vp9x' '.cursor/skills/redteam'Codex
test -f '.skill-downloads/red-team-analysis-ms47vp9x/SKILL.md' && test -s '.skill-downloads/red-team-analysis-ms47vp9x/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/redteam' && cp -R '.skill-downloads/red-team-analysis-ms47vp9x' '.agents/skills/redteam'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/red-team-analysis-ms47vp9x'openskills read 'red-team-analysis-ms47vp9x'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/red-team-analysis-ms47vp9x/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
DeFi AMM Security
Security
Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, donation attacks, oracle manipulation, slippage, and integer math.
Semgrep Rule Creator
Security
Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Includes test-first methodology, taint mode support, and validation steps. Helps when building targeted static analysis detections.
Dev Toolbar Review Guide
Security
Safety rules for the dev toolbar, PostHog client, and feature flags. Use when reviewing changes to dev-tools and related files, covering environment guards, override cookies, and SSE stream safety.