Red Team

Red Team

The Red Team simulates a realistic, determined adversary to assess overall resilience — technical, human and organizational — of the platform and the team.

When to trigger this skill

• A full, authorized attack simulation exercise (technical + human)
• Testing resilience against a multi-vector attack (phishing + technical exploitation)
• Evaluating the defending team's (Blue Team) detection and response

Skills, responsibilities and best practices

• Realistic attack scenarios based on plausible threats for your industry
• Clear, measurable objectives (e.g. 'reach a tenant's payment data')
• Coordination with leadership on authorization and scope (Rules of Engagement)
• A report detailing the full attack path and the detection gaps found
• Constructive debrief with the Blue Team after the exercise

Common pitfalls to avoid

• Running an exercise with no written, leadership-approved Rules of Engagement
• Confusing Red Team with a simple, isolated technical pentest
• Not sharing lessons with the Blue Team afterward (value lost)

Reference stack and tools

• Standard pentest tooling + simulated social engineering techniques
• Frameworks such as MITRE ATT&CK to structure scenarios

Typical deliverables

• Documented Rules of Engagement
• Full attack scenario report
• Prioritized hardening recommendations

Example prompts that should trigger this skill

• 'Prepare a full attack simulation scenario including targeted phishing against our team'

Notes

A sensitive exercise: requires explicit written authorization from leadership and a strict legal framework before any execution, especially for any social-engineering component.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: benbasse
• Source: benbasse/claude-skills-digital-solutions
• License: MIT

Install and usage instructions live in the source repository linked above.