CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conducting-full-scope-red-team-engagement

Plan and execute a comprehensive, MITRE ATT&CK-aligned red team engagement spanning threat modeling, reconnaissance, initial access, and post-exploitation to evaluate an organization's detection, prevention, and response against APT-style behavior. Use when scoping or running a full-scope, objective-based engagement, or purple-teaming against a specific threat actor's TTPs.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/conducting-full-scope-red-team-engagement/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers strong, phase-by-phase executable guidance with concrete tooling for every kill-chain stage, but it is undermined by an orphaned bundle: six provided files are never referenced, meaning the report template, engagement tracker scripts, and ATT&CK standards reference are invisible to a reader. Mid-engagement validation checkpoints are also missing for a workflow whose operations (credential dumping, lateral movement, exfiltration) carry high operational risk.

Suggestions

Add a navigation section (e.g., under References) pointing to the bundle files: "Report template: see assets/template.md", "ATT&CK technique listings: see references/standards.md", "Engagement lifecycle detail: see references/workflows.md", "Engagement tracker: see scripts/process.py", "ATT&CK API usage: see references/api-reference.md and scripts/agent.py" — and move the 13-row ATT&CK tactic table into references/standards.md, which already contains it.

Insert validation checkpoints between phases for the risky operations: e.g., verify C2 callback and opsec hygiene before post-exploitation, run deconfliction checks with the SOC liaison before lateral movement, and re-confirm scope/RoE constraints before each objective, with explicit "if detected, execute emergency stop per RoE" handling.

Trim the overview paragraph (red team vs. pentest distinction is knowledge Claude already has) and rewrite the circular "When to Use" bullets to be concrete; replace the nonexistent proxyshell_exploit.py reference with a real, obtainable command or an explicit note that the operator supplies the exploit.

DimensionReasoningScore

Conciseness

Mostly efficient command blocks, but three areas are padded: the overview paragraph ("Unlike penetration testing, red team operations prioritize stealth, persistence...") explains concepts Claude already knows, the "When to Use" bullet "When conducting security assessments that involve conducting full scope red team engagement" is circular filler, and the 13-row ATT&CK tactic table duplicates both Claude's knowledge and references/standards.md.

3 / 5

Actionability

Concrete, mostly copy-paste-ready commands across all phases (amass, theHarvester, msfvenom, nmap, Rubeus, secretsdump, dnscat2), matching the "mostly executable with minor gaps" anchor: `python3 proxyshell_exploit.py` references a script that does not exist in the bundle, and the GoPhish step is only a comment ("Configure SMTP profile, email template with pretexted lure") with no actual configuration guidance.

4 / 5

Workflow Clarity

The six engagement phases are clearly sequenced with prerequisites acting as an authorization gate, but mid-engagement validation checkpoints (opsec verification, SOC deconfliction, stop conditions) are absent or only implied via a single "emergency stop procedures" mention in Prerequisites; risky operations such as credential dumping and lateral movement lack verification steps, which caps this dimension at 3.

3 / 5

Progressive Disclosure

The body is well-sectioned, but none of the six bundle files (references/api-reference.md, references/standards.md, references/workflows.md, scripts/agent.py, scripts/process.py, assets/template.md) are referenced anywhere in the body — the References section lists only external URLs — so the report template, tracker scripts, and standards listing are undiscoverable, and the inlined ATT&CK table is content that belongs in references/standards.md. Not 3 because references are entirely absent rather than merely unclear; not 1 because the body itself is navigable with clear section headers.

2 / 5

Total

12

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person, concrete, and comprehensive, with an explicit and specific "Use when" clause covering scoping, execution, and purple-teaming triggers. Its only weakness is missing a few natural synonyms such as "adversary emulation" or "APT simulation" that users might say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Plan and execute", "threat modeling, reconnaissance, initial access, and post-exploitation", "evaluate an organization's detection, prevention, and response" — covering the full engagement lifecycle plus the evaluation goal, matching the comprehensive-coverage anchor rather than the minor-gaps level below.

5 / 5

Completeness

Explicitly answers both "what" (plan and execute a MITRE ATT&CK-aligned red team engagement to evaluate detection, prevention, and response) and "when" with a concrete "Use when..." trigger clause, matching the top anchor; the when-clause is explicit and specific, not merely present.

5 / 5

Trigger Term Quality

"Use when scoping or running a full-scope, objective-based engagement, or purple-teaming against a specific threat actor's TTPs" includes natural terms users would say (red team engagement, purple-teaming, TTPs, MITRE ATT&CK), but omits common synonyms like "adversary emulation" or "APT simulation", so it is good-but-not-comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche (full-scope, objective-based red team engagement distinct from penetration testing) with distinct triggers, but "purple-teaming" and threat-actor TTP emulation leave minor overlap risk with a dedicated adversary-emulation or purple-team skill.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

mukul975/Anthropic-Cybersecurity-Skills

Path

skills/conducting-full-scope-red-team-engagement/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.