Back to catalog
Static reviewDevelopment

Skill dossier

executing-phishing-simulation-campaign

Source declaration

Executes authorized phishing simulation campaigns to assess an organization's susceptibility to email-based social engineering attacks. The tester designs realistic phishing scenarios, builds credential harvesting infrastructure, sends targeted phishing emails, and tracks open rates, click-through rates, and credential submission rates to measure human security awareness. Activates for requests involving phishing simulation, social engineering assessment, email security testing, or security awareness measurement.

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

Executes authorized phishing simulation campaigns to assess an organization's susceptibility to email-based social engineering attacks. The tester designs realistic phishing scenarios, builds credential harvesting infrastructure, sends targeted phishing emails, and tracks open rates, click-through rates, and credential submission rates to measure human security awareness. Activates for requests involving phishing simulation, social engineering assessment, email security testing, or security awareness measurement.

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.

Executes authorized phishing simulation campaigns to assess an organization's susceptibility to email-based social engineering attacks. The tester designs realistic phishing scenarios, builds credential harvesting infrastructure, sends targeted phishing emails, and tracks open rates, click-through rates, and credential submission rates to measure human security awareness. Activates for requests involving phishing simulation, social engineering assessment, email security testing, or security awareness measurement. 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-phishing-simulation-campaign/SKILL.md:L88]
  • Step 1: Campaign Planning and Pretext Development [Source statement; provisional, not tested. Evidence: skills/executing-phishing-simulation-campaign/SKILL.md:L90]
  • Step 2: Infrastructure Setup [Source statement; provisional, not tested. Evidence: skills/executing-phishing-simulation-campaign/SKILL.md:L104]
  • Step 3: Campaign Execution [Source statement; provisional, not tested. Evidence: skills/executing-phishing-simulation-campaign/SKILL.md:L119]
  • Step 4: Credential Capture and Access Demonstration [Source statement; provisional, not tested. Evidence: skills/executing-phishing-simulation-campaign/SKILL.md:L130]
  • Step 5: Analysis and Reporting [Source statement; provisional, not tested. Evidence: skills/executing-phishing-simulation-campaign/SKILL.md:L140]

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-phishing-simulation-campaign/SKILL.md:L1-L66]

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
4
Markdown files
2
scripts
1
references
1
Size
32.2 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/executing-phishing-simulation-campaign/LICENSEOther11 KB
skills/executing-phishing-simulation-campaign/references/api-reference.mdReference2 KB
skills/executing-phishing-simulation-campaign/scripts/agent.pyScript6.8 KB
skills/executing-phishing-simulation-campaign/SKILL.mdInstruction12.5 KB

SKILL.md frontmatter

{
  "name": "executing-phishing-simulation-campaign",
  "description": "Executes authorized phishing simulation campaigns to assess an organization's susceptibility to email-based social engineering attacks. The tester designs realistic phishing scenarios, builds credential harvesting infrastructure, sends targeted phishing emails, and tracks open rates, click-through rates, and credential submission rates to measure human security awareness. Activates for requests involving phishing simulation, social engineering assessment, email security testing, or security awareness measurement.\n",
  "domain": "cybersecurity",
  "subdomain": "penetration-testing",
  "tags": [
    "phishing-simulation",
    "social-engineering",
    "GoPhish",
    "email-security",
    "security-awareness"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "ID.RA-01",
    "ID.RA-06",
    "GV.OV-02",
    "DE.AE-07"
  ],
  "mitre_attack": [
    "T1595",
    "T1190",
    "T1059",
    "T1078",
    "T1003"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "reconnaissance",
      "resource-development",
      "initial-access",
      "positioning"
    ],
    "techniques": [
      {
        "id": "T1598",
        "name": "Phishing for Information",
        "tactic": "reconnaissance",
        "source": "attack"
      },
      {
        "id": "T1660",
        "name": "Phishing",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "F1020.002",
        "name": "Create Fake Materials: Fake Website",
        "tactic": "resource-development",
        "source": "f3"
      },
      {
        "id": "T1583.001",
        "name": "Acquire Infrastructure: Domains",
        "tactic": "resource-development",
        "source": "attack"
      },
      {
        "id": "T1557",
        "name": "Adversary-in-the-Middle",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "F1004",
        "name": "Access with Stolen Session Cookie",
        "tactic": "initial-access",
        "source": "f3"
      }
    ]
  }
}

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
    Decision

    When to Use

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

  2. 02
    Action

    Workflow

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

  3. 03
    Action

    Step 1: Campaign Planning and Pretext Development

    Source-described action candidate under “Step 1: Campaign Planning and Pretext Development”; not verified execution.

  4. 04
    Decision

    Pretext selection: Choose scenarios that mirror real-world attacks:

    Source-described decision candidate under “Step 1: Campaign Planning and Pretext Development”; not verified execution.

  5. 05
    Action

    IT support: Password expiration notice requiring immediate action

    Source-described action candidate under “Step 1: Campaign Planning and Pretext Development”; not verified execution.

  6. 06
    Action

    HR department: Benefits enrollment, policy acknowledgment, W-2/tax document

    Source-described action candidate under “Step 1: Campaign Planning and Pretext Development”; not verified execution.

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

    Executive impersonation: Urgent request from CEO/CFO to review a document

    Source-described action candidate under “Step 1: Campaign Planning and Pretext Development”; not verified execution.

  2. 08
    Action

    Vendor/supplier: Invoice requiring review, delivery notification

    Source-described action candidate under “Step 1: Campaign Planning and Pretext Development”; not verified execution.

  3. 09
    Action

    Cloud services: Microsoft 365 shared document, Google Drive access, Zoom meeting invitation

    Source-described action candidate under “Step 1: Campaign Planning and Pretext Development”; not verified execution.

  4. 10
    Input

    Target segmentation: Divide employees into groups by department, role, or access level. High-value targets (finance, IT admin, executives) may receive more sophisticated pretexts.

    Source-described input candidate under “Step 1: Campaign Planning and Pretext Development”; not verified execution.

  5. 11
    Action

    Timing: Schedule sends during business hours, preferably Tuesday-Thursday when email engagement is highest. Avoid holidays, mass layoff periods, or other sensitive times.

    Source-described action candidate under “Step 1: Campaign Planning and Pretext Development”; not verified execution.

  6. 12
    Output

    Success metrics: Define what constitutes campaign success: email open rate, link click rate, credential submission rate, report rate (employees who report the phish to IT)

    Source-described output candidate under “Step 1: Campaign Planning and Pretext Development”; not verified execution.

  7. 13
    Action

    Step 2: Infrastructure Setup

    Source-described action candidate under “Step 2: Infrastructure Setup”; not verified execution.

  8. 14
    Action

    Domain registration: Register a domain that resembles the target organization's domain (typosquatting, homograph, or brand-adjacent). Examples: `target-corp.com`, `targetcorp-portal.com`, `targetsupport.net`

    Source-described action candidate under “Step 2: Infrastructure Setup”; not verified execution.

  9. 15
    Output

    SSL certificate: Obtain a TLS certificate for the phishing domain (Let's Encrypt) to display the padlock icon

    Source-described output candidate under “Step 2: Infrastructure Setup”; not verified execution.

  10. 16
    Action

    GoPhish configuration:

    Source-described action candidate under “Step 2: Infrastructure Setup”; not verified execution.

  11. 17
    Action

    Set up the GoPhish server on a VPS with the phishing domain

    Source-described action candidate under “Step 2: Infrastructure Setup”; not verified execution.

  12. 18
    Action

    Configure the SMTP sending profile with the phishing domain's mail server

    Source-described action candidate under “Step 2: Infrastructure Setup”; not verified execution.

  13. 19
    Action

    Create the email template with tracking pixel and link to the landing page

    Source-described action candidate under “Step 2: Infrastructure Setup”; not verified execution.

  14. 20
    Action

    Build the credential harvesting landing page that mirrors the target's login portal

    Source-described action candidate under “Step 2: Infrastructure Setup”; not verified execution.

  15. 21
    Input

    Import the target email list and create user groups

    Source-described input candidate under “Step 2: Infrastructure Setup”; not verified execution.

  16. 22
    Action

    Email authentication: Configure SPF, DKIM, and DMARC records for the phishing domain to pass email authentication checks and improve delivery rates

    Source-described action candidate under “Step 2: Infrastructure Setup”; not verified execution.

  17. 23
    Action

    Test delivery: Send test emails to a controlled inbox to verify rendering, link tracking, and landing page functionality

    Source-described action candidate under “Step 2: Infrastructure Setup”; not verified execution.

  18. 24
    Action

    Step 3: Campaign Execution

    Source-described action candidate under “Step 3: Campaign Execution”; not verified execution.

  19. 25
    Action

    Send emails in batches to avoid triggering rate limits or spam filters (e.g., 50 emails per hour)

    Source-described action candidate under “Step 3: Campaign Execution”; not verified execution.

  20. 26
    Action

    Monitor GoPhish dashboard in real-time for delivery failures, bounces, and early interactions

    Source-described action candidate under “Step 3: Campaign Execution”; not verified execution.

  21. 27
    Action

    Track metrics as they come in: emails sent, emails opened (tracking pixel fired), links clicked, credentials submitted

    Source-described action candidate under “Step 3: Campaign Execution”; not verified execution.

  22. 28
    Decision

    If the IT security team or SOC detects the campaign (if this is part of the test), document the detection time and response actions

    Source-described decision candidate under “Step 3: Campaign Execution”; not verified execution.

  23. 29
    Decision

    Maintain an emergency stop procedure: if an employee becomes distressed or the campaign creates unintended consequences, pause immediately

    Source-described decision candidate under “Step 3: Campaign Execution”; not verified execution.

  24. 30
    Action

    Run the campaign for 48-72 hours before closing the landing page, as most interactions occur within the first 24 hours

    Source-described action candidate under “Step 3: Campaign Execution”; not verified execution.

  25. 31
    Action

    Step 4: Credential Capture and Access Demonstration

    Source-described action candidate under “Step 4: Credential Capture and Access Demonstration”; not verified execution.

  26. 32
    Action

    Review all captured credentials in GoPhish. Do not test credentials against real systems unless explicitly authorized.

    Source-described action candidate under “Step 4: Credential Capture and Access Demonstration”; not verified execution.

  27. 33
    Decision

    If authorized for full exploitation: test captured credentials against the organization's actual login portal (VPN, OWA, SSO)

    Source-described decision candidate under “Step 4: Credential Capture and Access Demonstration”; not verified execution.

  28. 34
    Decision

    Document any accounts that were successfully compromised, what data they could access, and whether MFA was present

    Source-described decision candidate under “Step 4: Credential Capture and Access Demonstration”; not verified execution.

  29. 35
    Decision

    If MFA blocks access, document that MFA prevented the compromise and recommend maintaining MFA enforcement

    Source-described decision candidate under “Step 4: Credential Capture and Access Demonstration”; not verified execution.

  30. 36
    Action

    Identify patterns in credential submissions: which departments, roles, or locations are most susceptible

    Source-described action candidate under “Step 4: Credential Capture and Access Demonstration”; not verified execution.

  31. 37
    Action

    Step 5: Analysis and Reporting

    Source-described action candidate under “Step 5: Analysis and Reporting”; not verified execution.

  32. 38
    Output

    Analyze campaign results and produce the assessment report:

    Source-described output candidate under “Step 5: Analysis and Reporting”; not verified execution.

  33. 39
    Action

    Metrics analysis:

    Source-described action candidate under “Step 5: Analysis and Reporting”; not verified execution.

  34. 40
    Action

    Email delivery rate: percentage of emails that reached inboxes

    Source-described action candidate under “Step 5: Analysis and Reporting”; not verified execution.

  35. 41
    Action

    Open rate: percentage of recipients who opened the email

    Source-described action candidate under “Step 5: Analysis and Reporting”; not verified execution.

  36. 42
    Action

    Click rate: percentage who clicked the phishing link

    Source-described action candidate under “Step 5: Analysis and Reporting”; not verified execution.

  37. 43
    Action

    Submission rate: percentage who submitted credentials

    Source-described action candidate under “Step 5: Analysis and Reporting”; not verified execution.

  38. 44
    Output

    Report rate: percentage who reported the email to IT security

    Source-described output candidate under “Step 5: Analysis and Reporting”; not verified execution.

  39. 45
    Action

    Departmental comparison: Compare susceptibility rates across departments to identify groups needing targeted training

    Source-described action candidate under “Step 5: Analysis and Reporting”; not verified execution.

  40. 46
    Decision

    Email security effectiveness: Document whether the phishing emails bypassed the secure email gateway, whether DMARC/SPF prevented delivery, and whether link scanning tools detected the phishing URL

    Source-described decision candidate under “Step 5: Analysis and Reporting”; not verified execution.

  41. 47
    Input

    Recommendations: Provide actionable recommendations including security awareness training topics, technical controls improvements, and policy changes

    Source-described input candidate under “Step 5: Analysis and Reporting”; not verified execution.

  42. 48
    Action

    Key Concepts

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

  43. 49
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  44. 50
    Action

    Common Scenarios

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

  45. 51
    Action

    Develop a Microsoft 365 password expiration pretext: "Your password expires in 24 hours. Click here to update."

    Source-described action candidate under “Scenario: Enterprise Phishing Simulation for Security Awareness Baseline”; not verified execution.

  46. 52
    Action

    Register `m365-targetcorp.com`, set up GoPhish, and build a landing page cloning the Microsoft 365 login portal

    Source-described action candidate under “Scenario: Enterprise Phishing Simulation for Security Awareness Baseline”; not verified execution.

  47. 53
    Input

    Import all 2,000 employee emails and schedule sends in batches of 100 over 20 hours

    Source-described input candidate under “Scenario: Enterprise Phishing Simulation for Security Awareness Baseline”; not verified execution.

  48. 54
    Action

    Campaign results after 72 hours: 1,847 delivered (92.4%), 1,243 opened (67.3%), 487 clicked (26.4%), 312 submitted credentials (16.9%), 23 reported to IT (1.2%)

    Source-described action candidate under “Scenario: Enterprise Phishing Simulation for Security Awareness Baseline”; not verified execution.

  49. 55
    Action

    Analysis reveals Finance (28% submission) and Marketing (24% submission) have the highest susceptibility; IT department has the lowest (4%)

    Source-described action candidate under “Scenario: Enterprise Phishing Simulation for Security Awareness Baseline”; not verified execution.

  50. 56
    Output

    Recommend targeted training for high-susceptibility departments, phishing report button deployment, and quarterly simulation cadence

    Source-described output candidate under “Scenario: Enterprise Phishing Simulation for Security Awareness Baseline”; not verified execution.

  51. 57
    Output

    Output Format

    Source-described output candidate under “Output Format”; 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

26 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

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

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

2 occurrences

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 2 location(s) in the collected text; 2 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-phishing-simulation-campaign/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 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/executing-phishing-simulation-campaign/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-phishing-simulation-campaign
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.