Back to catalog
Static reviewDevelopment

Skill dossier

executing-red-team-engagement-planning

Source declaration

Build the foundational red team engagement plan - scope definition, Rules of Engagement (restrictions, communication plan, emergency stop procedures, legal authorization), MITRE ATT&CK-aligned threat profile selection, and operational timelines - producing an engagement brief for stakeholder approval. Use before any offensive testing begins, when scoping a full-scope, assumed-breach, objective-based, or purple-team engagement.

The author's original description, preserved in English. It describes intent, not verified performance.

Build the foundational red team engagement plan - scope definition, Rules of Engagement (restrictions, communication plan, emergency stop procedures, legal authorization), MITRE ATT&CK-aligned threat profile selection, and operational timelines - producing an engagement brief for stakeholder approval. Use before any offensive testing begins, when scoping a full-scope, assumed-breach, objective-based, or purple-team engagement.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Build the foundational red team engagement plan - scope definition, Rules of Engagement (restrictions, communication plan, emergency stop procedures, legal authorization), MITRE ATT&CK-aligned threat profile selection, and operational timelines - producing an engagement brief for stakeholder approval. Use before any offensive testing begins, when scoping a full-scope, assumed-breach, objective-based, or purple-team engagement. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/executing-red-team-engagement-planning/SKILL.md:L94]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/executing-red-team-engagement-planning/SKILL.md:L1-L30]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
74.2 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/executing-red-team-engagement-planning/assets/template.mdReference6.7 KB
skills/executing-red-team-engagement-planning/LICENSEOther11 KB
skills/executing-red-team-engagement-planning/references/api-reference.mdReference2.2 KB
skills/executing-red-team-engagement-planning/references/standards.mdReference2.7 KB
skills/executing-red-team-engagement-planning/references/workflows.mdReference6.1 KB
skills/executing-red-team-engagement-planning/scripts/agent.pyScript5.9 KB
skills/executing-red-team-engagement-planning/scripts/process.pyScript32.7 KB
skills/executing-red-team-engagement-planning/SKILL.mdInstruction6.8 KB

SKILL.md frontmatter

{
  "name": "executing-red-team-engagement-planning",
  "description": "Build the foundational red team engagement plan - scope definition, Rules of Engagement (restrictions, communication plan, emergency stop procedures, legal authorization), MITRE ATT&CK-aligned threat profile selection, and operational timelines - producing an engagement brief for stakeholder approval. Use before any offensive testing begins, when scoping a full-scope, assumed-breach, objective-based, or purple-team engagement.",
  "domain": "cybersecurity",
  "subdomain": "red-teaming",
  "tags": [
    "red-team",
    "adversary-simulation",
    "mitre-attack",
    "exploitation",
    "post-exploitation",
    "engagement-planning",
    "rules-of-engagement"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "ID.RA-01",
    "GV.OV-02",
    "DE.AE-07"
  ],
  "mitre_attack": [
    "T1595",
    "T1190",
    "T1059",
    "T1078"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Objectives

    Source-described action candidate under “Objectives”; not verified execution.

  4. 04
    Action

    Core Concepts

    Source-described action candidate under “Core Concepts”; not verified execution.

  5. 05
    Action

    Scope Definition: IP ranges, domains, physical locations, personnel

    Source-described action candidate under “Rules of Engagement Components”; not verified execution.

  6. 06
    Action

    Restrictions: Systems/networks that must not be touched (e.g., production databases, medical devices)

    Source-described action candidate under “Rules of Engagement Components”; not verified execution.

Inspect all extracted workflow candidates (41 candidate steps)
  1. 07
    Action

    Communication Plan: Primary and secondary contact channels, escalation procedures

    Source-described action candidate under “Rules of Engagement Components”; not verified execution.

  2. 08
    Action

    Emergency Procedures: Code word for immediate cessation, incident response coordination

    Source-described action candidate under “Rules of Engagement Components”; not verified execution.

  3. 09
    Action

    Legal Authorization: Signed authorization letters, get-out-of-jail letters for physical tests

    Source-described action candidate under “Rules of Engagement Components”; not verified execution.

  4. 10
    Action

    Data Handling: How sensitive data discovered during testing will be handled and destroyed

    Source-described action candidate under “Rules of Engagement Components”; not verified execution.

  5. 11
    Action

    Timeline: Start/end dates, blackout windows, reporting deadlines

    Source-described action candidate under “Rules of Engagement Components”; not verified execution.

  6. 12
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  7. 13
    Action

    Conduct initial scoping meeting with stakeholders

    Source-described action candidate under “Phase 1: Pre-Engagement”; not verified execution.

  8. 14
    Action

    Identify crown jewels and critical business assets

    Source-described action candidate under “Phase 1: Pre-Engagement”; not verified execution.

  9. 15
    Action

    Review previous security assessments and audit findings

    Source-described action candidate under “Phase 1: Pre-Engagement”; not verified execution.

  10. 16
    Action

    Define success criteria and engagement objectives

    Source-described action candidate under “Phase 1: Pre-Engagement”; not verified execution.

  11. 17
    Action

    Draft Rules of Engagement document

    Source-described action candidate under “Phase 1: Pre-Engagement”; not verified execution.

  12. 18
    Action

    Identify relevant threat actors using MITRE ATT&CK

    Source-described action candidate under “Phase 2: Threat Modeling”; not verified execution.

  13. 19
    Action

    Map threat actor TTPs to organizational attack surface

    Source-described action candidate under “Phase 2: Threat Modeling”; not verified execution.

  14. 20
    Action

    Select primary and secondary attack scenarios

    Source-described action candidate under “Phase 2: Threat Modeling”; not verified execution.

  15. 21
    Action

    Define adversary emulation plan with specific technique IDs

    Source-described action candidate under “Phase 2: Threat Modeling”; not verified execution.

  16. 22
    Action

    Establish detection checkpoints for purple team opportunities

    Source-described action candidate under “Phase 2: Threat Modeling”; not verified execution.

  17. 23
    Action

    Set up secure communication channels (encrypted email, Signal, etc.)

    Source-described action candidate under “Phase 3: Operational Planning”; not verified execution.

  18. 24
    Action

    Create operational security (OPSEC) guidelines for the red team

    Source-described action candidate under “Phase 3: Operational Planning”; not verified execution.

  19. 25
    Action

    Establish infrastructure requirements (C2 servers, redirectors, phishing domains)

    Source-described action candidate under “Phase 3: Operational Planning”; not verified execution.

  20. 26
    Action

    Develop phased attack timeline with go/no-go decision points

    Source-described action candidate under “Phase 3: Operational Planning”; not verified execution.

  21. 27
    Action

    Create deconfliction matrix with SOC/IR team

    Source-described action candidate under “Phase 3: Operational Planning”; not verified execution.

  22. 28
    Action

    Compile engagement plan document

    Source-described action candidate under “Phase 4: Documentation and Approval”; not verified execution.

  23. 29
    Action

    Review with legal counsel

    Source-described action candidate under “Phase 4: Documentation and Approval”; not verified execution.

  24. 30
    Action

    Obtain executive sponsor signature

    Source-described action candidate under “Phase 4: Documentation and Approval”; not verified execution.

  25. 31
    Action

    Brief red team operators on ROE and restrictions

    Source-described action candidate under “Phase 4: Documentation and Approval”; not verified execution.

  26. 32
    Action

    Distribute emergency contact cards

    Source-described action candidate under “Phase 4: Documentation and Approval”; not verified execution.

  27. 33
    Action

    Tools and Resources

    Source-described action candidate under “Tools and Resources”; not verified execution.

  28. 34
    Action

    Validation Criteria

    Source-described action candidate under “Validation Criteria”; not verified execution.

  29. 35
    Action

    Common Pitfalls

    Source-described action candidate under “Common Pitfalls”; not verified execution.

  30. 36
    Action

    Scope Creep: Expanding testing beyond approved boundaries during execution

    Source-described action candidate under “Common Pitfalls”; not verified execution.

  31. 37
    Action

    Inadequate Deconfliction: SOC investigating red team activity as real incidents

    Source-described action candidate under “Common Pitfalls”; not verified execution.

  32. 38
    Action

    Missing Legal Authorization: Testing without proper signed authorization

    Source-described action candidate under “Common Pitfalls”; not verified execution.

  33. 39
    Action

    Unrealistic Threat Models: Simulating threats irrelevant to the organization

    Source-described action candidate under “Common Pitfalls”; not verified execution.

  34. 40
    Action

    Poor Communication: Failing to maintain contact with stakeholders during engagement

    Source-described action candidate under “Common Pitfalls”; not verified execution.

  35. 41
    Action

    Related Skills

    Source-described action candidate under “Related Skills”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

16 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

5 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 5 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

11 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 11 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/executing-red-team-engagement-planning/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/executing-red-team-engagement-planning/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/executing-red-team-engagement-planning
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.