Back to catalog
Static reviewDevelopment

Skill dossier

conducting-full-scope-red-team-engagement

Source declaration

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.

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

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.

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.

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. 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

  • Source-declared purpose: 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. [Evidence: skills/conducting-full-scope-red-team-engagement/SKILL.md:L1-L32]
  • Provisional classification: category and tags are inferred from names, descriptions, and file paths, not verified outcomes. [Evidence: skills/conducting-full-scope-red-team-engagement/SKILL.md:L1-L32]

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/conducting-full-scope-red-team-engagement/SKILL.md:L1-L32]

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
66.8 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/conducting-full-scope-red-team-engagement/assets/template.mdReference6.8 KB
skills/conducting-full-scope-red-team-engagement/LICENSEOther11 KB
skills/conducting-full-scope-red-team-engagement/references/api-reference.mdReference1.8 KB
skills/conducting-full-scope-red-team-engagement/references/standards.mdReference4.3 KB
skills/conducting-full-scope-red-team-engagement/references/workflows.mdReference8.4 KB
skills/conducting-full-scope-red-team-engagement/scripts/agent.pyScript6 KB
skills/conducting-full-scope-red-team-engagement/scripts/process.pyScript20.8 KB
skills/conducting-full-scope-red-team-engagement/SKILL.mdInstruction7.7 KB

SKILL.md frontmatter

{
  "name": "conducting-full-scope-red-team-engagement",
  "description": "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.",
  "domain": "cybersecurity",
  "subdomain": "red-teaming",
  "tags": [
    "red-team",
    "adversary-emulation",
    "mitre-attack",
    "penetration-testing",
    "offensive-security",
    "purple-team",
    "ttp-mapping"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "d3fend_techniques": [
    "File Metadata Consistency Validation",
    "Application Protocol Command Analysis",
    "Identifier Analysis",
    "Content Format Conversion",
    "Message Analysis"
  ],
  "nist_csf": [
    "ID.RA-01",
    "GV.OV-02",
    "DE.AE-07"
  ],
  "mitre_attack": [
    "T1566.001",
    "T1059.001",
    "T1078",
    "T1071.001"
  ]
}

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

    Engagement Phases

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

  4. 04
    Action

    Domain Dominance: Achieve Domain Admin access and DCSync credentials

    Source-described action candidate under “Phase 5: Objective Achievement”; not verified execution.

  5. 05
    Action

    Data Exfiltration: Locate and exfiltrate crown jewel data (e.g., PII, financial records)

    Source-described action candidate under “Phase 5: Objective Achievement”; not verified execution.

  6. 06
    Action

    Business Impact Simulation: Demonstrate ransomware deployment capability (without execution)

    Source-described action candidate under “Phase 5: Objective Achievement”; not verified execution.

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

    Physical Access: Badge cloning, tailgating, server room access

    Source-described action candidate under “Phase 5: Objective Achievement”; not verified execution.

  2. 08
    Action

    Executive Summary: Business impact, risk rating, key findings

    Source-described action candidate under “Phase 6: Reporting and Debrief”; not verified execution.

  3. 09
    Action

    Attack Narrative: Timeline of activities with screenshots and evidence

    Source-described action candidate under “Phase 6: Reporting and Debrief”; not verified execution.

  4. 10
    Action

    MITRE ATT&CK Mapping: Full heat map of techniques used

    Source-described action candidate under “Phase 6: Reporting and Debrief”; not verified execution.

  5. 11
    Action

    Findings: Each finding with CVSS score, evidence, remediation

    Source-described action candidate under “Phase 6: Reporting and Debrief”; not verified execution.

  6. 12
    Action

    Detection Gap Analysis: What the SOC detected vs. what was missed

    Source-described action candidate under “Phase 6: Reporting and Debrief”; not verified execution.

  7. 13
    Action

    Purple Team Recommendations: Specific detection rules for gaps identified

    Source-described action candidate under “Phase 6: Reporting and Debrief”; not verified execution.

  8. 14
    Action

    Metrics and KPIs

    Source-described action candidate under “Metrics and KPIs”; not verified execution.

  9. 15
    Action

    Tools and Frameworks

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

  10. 16
    Action

    References

    Source-described action candidate under “References”; 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.

Attention recommended

44 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 useObserved
Medium

Network access is mentioned

13 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 13 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

30 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 30 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 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/conducting-full-scope-red-team-engagement/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/conducting-full-scope-red-team-engagement/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/conducting-full-scope-red-team-engagement
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.