Back to catalog
Static reviewDevelopment

Skill dossier

implementing-anti-phishing-training-program

Source declaration

Guides designing, deploying, and measuring an anti-phishing security awareness program - baseline phishing simulations, interactive training modules, just-in-time learning, and metric tracking - using platforms like KnowBe4, Proofpoint Security Awareness, or Cofense. Use when building or maturing a phishing awareness program, establishing training controls for compliance, or measuring phishing susceptibility and reporting rates over time.

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

Guides designing, deploying, and measuring an anti-phishing security awareness program - baseline phishing simulations, interactive training modules, just-in-time learning, and metric tracking - using platforms like KnowBe4, Proofpoint Security Awareness, or Cofense. Use when building or maturing a phishing awareness program, establishing training controls for compliance, or measuring phishing susceptibility and reporting rates over time.

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.

Guides designing, deploying, and measuring an anti-phishing security awareness program - baseline phishing simulations, interactive training modules, just-in-time learning, and metric tracking - using platforms like KnowBe4, Proofpoint Security Awareness, or Cofense. Use when building or maturing a phishing awareness program, establishing training controls for compliance, or measuring phishing susceptibility and reporting rates over time. 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/implementing-anti-phishing-training-program/SKILL.md:L92]
  • Step 1: Establish Baseline [Source statement; provisional, not tested. Evidence: skills/implementing-anti-phishing-training-program/SKILL.md:L94]
  • Step 2: Design Curriculum [Source statement; provisional, not tested. Evidence: skills/implementing-anti-phishing-training-program/SKILL.md:L99]
  • Step 3: Deploy Training Platform [Source statement; provisional, not tested. Evidence: skills/implementing-anti-phishing-training-program/SKILL.md:L105]
  • Step 4: Run Continuous Simulations [Source statement; provisional, not tested. Evidence: skills/implementing-anti-phishing-training-program/SKILL.md:L111]
  • Step 5: Measure and Optimize [Source statement; provisional, not tested. Evidence: skills/implementing-anti-phishing-training-program/SKILL.md:L116]

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/implementing-anti-phishing-training-program/SKILL.md:L1-L54]

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

File inventory

PathTypeBytes
skills/implementing-anti-phishing-training-program/assets/template.mdReference2.4 KB
skills/implementing-anti-phishing-training-program/LICENSEOther11 KB
skills/implementing-anti-phishing-training-program/references/api-reference.mdReference1.8 KB
skills/implementing-anti-phishing-training-program/references/standards.mdReference2.1 KB
skills/implementing-anti-phishing-training-program/references/workflows.mdReference3.1 KB
skills/implementing-anti-phishing-training-program/scripts/agent.pyScript6.8 KB
skills/implementing-anti-phishing-training-program/scripts/process.pyScript13.9 KB
skills/implementing-anti-phishing-training-program/SKILL.mdInstruction5 KB

SKILL.md frontmatter

{
  "name": "implementing-anti-phishing-training-program",
  "description": "Guides designing, deploying, and measuring an anti-phishing security awareness program - baseline phishing simulations, interactive training modules, just-in-time learning, and metric tracking - using platforms like KnowBe4, Proofpoint Security Awareness, or Cofense. Use when building or maturing a phishing awareness program, establishing training controls for compliance, or measuring phishing susceptibility and reporting rates over time.",
  "domain": "cybersecurity",
  "subdomain": "phishing-defense",
  "tags": [
    "phishing",
    "email-security",
    "social-engineering",
    "dmarc",
    "awareness",
    "training",
    "security-culture"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.AT-01",
    "DE.CM-09",
    "RS.CO-02",
    "DE.AE-02"
  ],
  "mitre_attack": [
    "T1566",
    "T1598",
    "T1534",
    "T1036"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "reconnaissance",
      "initial-access",
      "stealth"
    ],
    "techniques": [
      {
        "id": "T1660",
        "name": "Phishing",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1598",
        "name": "Phishing for Information",
        "tactic": "reconnaissance",
        "source": "attack"
      },
      {
        "id": "T1672",
        "name": "Email Spoofing",
        "tactic": "stealth",
        "source": "attack"
      },
      {
        "id": "F1032",
        "name": "Impersonate Official",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "F1031",
        "name": "Impersonate Account Holder",
        "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
    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

    Key Concepts

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

  4. 04
    Action

    Baseline Assessment: Initial phishing simulation to measure current susceptibility

    Source-described action candidate under “Training Program Pillars”; not verified execution.

  5. 05
    Action

    Interactive Training: Role-based modules covering phishing identification

    Source-described action candidate under “Training Program Pillars”; not verified execution.

  6. 06
    Action

    Regular Simulations: Monthly/quarterly phishing tests with progressive difficulty

    Source-described action candidate under “Training Program Pillars”; not verified execution.

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

    Just-in-Time Learning: Immediate training after a user fails a simulation

    Source-described action candidate under “Training Program Pillars”; not verified execution.

  2. 08
    Action

    Positive Reinforcement: Recognition for reporting phishing correctly

    Source-described action candidate under “Training Program Pillars”; not verified execution.

  3. 09
    Action

    Metrics & Reporting: Track improvement over time by department and role

    Source-described action candidate under “Training Program Pillars”; not verified execution.

  4. 10
    Action

    Workflow

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

  5. 11
    Action

    Step 1: Establish Baseline

    Source-described action candidate under “Step 1: Establish Baseline”; not verified execution.

  6. 12
    Action

    Run initial phishing simulation across all departments

    Source-described action candidate under “Step 1: Establish Baseline”; not verified execution.

  7. 13
    Output

    Measure click rate, submit rate, and report rate

    Source-described output candidate under “Step 1: Establish Baseline”; not verified execution.

  8. 14
    Action

    Identify high-risk departments and roles

    Source-described action candidate under “Step 1: Establish Baseline”; not verified execution.

  9. 15
    Action

    Step 2: Design Curriculum

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

  10. 16
    Action

    General awareness: Phishing identification basics for all employees

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

  11. 17
    Action

    Role-specific: Finance (BEC/wire fraud), IT (credential phishing), Executives (whaling)

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

  12. 18
    Action

    Progressive difficulty: Beginner, intermediate, advanced modules

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

  13. 19
    Action

    Micro-learning: Short (3-5 minute) frequent sessions vs. annual marathon

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

  14. 20
    Action

    Step 3: Deploy Training Platform

    Source-described action candidate under “Step 3: Deploy Training Platform”; not verified execution.

  15. 21
    Action

    Configure KnowBe4/Proofpoint SAT with organizational groups

    Source-described action candidate under “Step 3: Deploy Training Platform”; not verified execution.

  16. 22
    Action

    Set up automated enrollment workflows

    Source-described action candidate under “Step 3: Deploy Training Platform”; not verified execution.

  17. 23
    Action

    Integrate with LMS for completion tracking

    Source-described action candidate under “Step 3: Deploy Training Platform”; not verified execution.

  18. 24
    Action

    Configure reporting dashboards

    Source-described action candidate under “Step 3: Deploy Training Platform”; not verified execution.

  19. 25
    Action

    Step 4: Run Continuous Simulations

    Source-described action candidate under “Step 4: Run Continuous Simulations”; not verified execution.

  20. 26
    Action

    Monthly simulations with varied scenarios

    Source-described action candidate under “Step 4: Run Continuous Simulations”; not verified execution.

  21. 27
    Action

    Increase difficulty based on organizational performance

    Source-described action candidate under “Step 4: Run Continuous Simulations”; not verified execution.

  22. 28
    Action

    Include diverse attack types: links, attachments, QR codes, BEC

    Source-described action candidate under “Step 4: Run Continuous Simulations”; not verified execution.

  23. 29
    Action

    Step 5: Measure and Optimize

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

  24. 30
    Action

    Use `scripts/process.py` to analyze training completion, simulation results, and program effectiveness over time.

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

  25. 31
    Action

    Tools & Resources

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

  26. 32
    Action

    Validation

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

73 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
Note

File modification is described or implemented

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

Medium

Network access is mentioned

15 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 15 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/implementing-anti-phishing-training-program/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/implementing-anti-phishing-training-program/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/implementing-anti-phishing-training-program
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.