Back to catalog
Static reviewDevelopment

Skill dossier

building-phishing-reporting-button-workflow

Source declaration

Implement a phishing report button (Microsoft 365 built-in Report button or third-party like KnowBe4/Cofense) in email clients with a SOAR-driven automated triage workflow that classifies reported emails, extracts IOCs, takes remediation actions, and gives feedback to reporters. Use when deploying user-reported phishing intake or automating triage of the resulting reporting mailbox.

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

Implement a phishing report button (Microsoft 365 built-in Report button or third-party like KnowBe4/Cofense) in email clients with a SOAR-driven automated triage workflow that classifies reported emails, extracts IOCs, takes remediation actions, and gives feedback to reporters. Use when deploying user-reported phishing intake or automating triage of the resulting reporting mailbox.

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.

Implement a phishing report button (Microsoft 365 built-in Report button or third-party like KnowBe4/Cofense) in email clients with a SOAR-driven automated triage workflow that classifies reported emails, extracts IOCs, takes remediation actions, and gives feedback to reporters. Use when deploying user-reported phishing intake or automating triage of the resulting reporting mailbox. 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

  • Building Phishing Reporting Button Workflow [Source statement; provisional, not tested. Evidence: skills/building-phishing-reporting-button-workflow/SKILL.md:L57]
  • Workflow [Source statement; provisional, not tested. Evidence: skills/building-phishing-reporting-button-workflow/SKILL.md:L77]
  • Step 1: Deploy Phishing Report Button [Source statement; provisional, not tested. Evidence: skills/building-phishing-reporting-button-workflow/SKILL.md:L79]
  • Step 2: Build Automated Triage Pipeline [Source statement; provisional, not tested. Evidence: skills/building-phishing-reporting-button-workflow/SKILL.md:L86]
  • Step 3: Implement Response Actions [Source statement; provisional, not tested. Evidence: skills/building-phishing-reporting-button-workflow/SKILL.md:L94]
  • Step 4: Create Feedback Loop [Source statement; provisional, not tested. Evidence: skills/building-phishing-reporting-button-workflow/SKILL.md:L101]
  • Step 5: Measure and Optimize [Source statement; provisional, not tested. Evidence: skills/building-phishing-reporting-button-workflow/SKILL.md:L108]

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/building-phishing-reporting-button-workflow/SKILL.md:L1-L56]

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

File inventory

PathTypeBytes
skills/building-phishing-reporting-button-workflow/assets/template.mdReference945 B
skills/building-phishing-reporting-button-workflow/LICENSEOther11 KB
skills/building-phishing-reporting-button-workflow/references/api-reference.mdReference1.8 KB
skills/building-phishing-reporting-button-workflow/references/standards.mdReference1.3 KB
skills/building-phishing-reporting-button-workflow/references/workflows.mdReference1.8 KB
skills/building-phishing-reporting-button-workflow/scripts/agent.pyScript7.1 KB
skills/building-phishing-reporting-button-workflow/scripts/process.pyScript10.5 KB
skills/building-phishing-reporting-button-workflow/SKILL.mdInstruction5.1 KB

SKILL.md frontmatter

{
  "name": "building-phishing-reporting-button-workflow",
  "description": "Implement a phishing report button (Microsoft 365 built-in Report button or third-party like KnowBe4/Cofense) in email clients with a SOAR-driven automated triage workflow that classifies reported emails, extracts IOCs, takes remediation actions, and gives feedback to reporters. Use when deploying user-reported phishing intake or automating triage of the resulting reporting mailbox.",
  "domain": "cybersecurity",
  "subdomain": "phishing-defense",
  "tags": [
    "phishing-reporting",
    "email-security",
    "incident-response",
    "security-awareness",
    "outlook",
    "microsoft-365",
    "soar"
  ],
  "mitre_attack": [
    "T1566.001",
    "T1566.002",
    "T1598.003",
    "T1204.001",
    "T1534"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "reconnaissance",
      "resource-development",
      "initial-access",
      "stealth"
    ],
    "techniques": [
      {
        "id": "T1598",
        "name": "Phishing for Information",
        "tactic": "reconnaissance",
        "source": "attack"
      },
      {
        "id": "T1660",
        "name": "Phishing",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1672",
        "name": "Email Spoofing",
        "tactic": "stealth",
        "source": "attack"
      },
      {
        "id": "F1020.002",
        "name": "Create Fake Materials: Fake Website",
        "tactic": "resource-development",
        "source": "f3"
      }
    ]
  },
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.AT-01",
    "DE.CM-09",
    "RS.CO-02",
    "DE.AE-02"
  ]
}

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

    Building Phishing Reporting Button Workflow

    Source-described action candidate under “Building Phishing Reporting Button Workflow”; not verified execution.

  2. 02
    Action

    Overview

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

  3. 03
    Decision

    When to Use

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

  4. 04
    Action

    Workflow

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

  5. 05
    Output

    Step 1: Deploy Phishing Report Button

    Source-described output candidate under “Step 1: Deploy Phishing Report Button”; not verified execution.

  6. 06
    Output

    Enable Microsoft built-in Report button via Security & Compliance Center

    Source-described output candidate under “Step 1: Deploy Phishing Report Button”; not verified execution.

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

    Configure user reported settings: route to reporting mailbox and Microsoft

    Source-described action candidate under “Step 1: Deploy Phishing Report Button”; not verified execution.

  2. 08
    Action

    For third-party: deploy KnowBe4 Phish Alert Button or Cofense Reporter

    Source-described action candidate under “Step 1: Deploy Phishing Report Button”; not verified execution.

  3. 09
    Action

    Verify button appears in Outlook desktop, web, and mobile clients

    Source-described action candidate under “Step 1: Deploy Phishing Report Button”; not verified execution.

  4. 10
    Output

    Configure report options: Report Phishing, Report Junk, Report Not Junk

    Source-described output candidate under “Step 1: Deploy Phishing Report Button”; not verified execution.

  5. 11
    Action

    Step 2: Build Automated Triage Pipeline

    Source-described action candidate under “Step 2: Build Automated Triage Pipeline”; not verified execution.

  6. 12
    Action

    Configure reporting mailbox monitored by SOAR platform

    Source-described action candidate under “Step 2: Build Automated Triage Pipeline”; not verified execution.

  7. 13
    Action

    Auto-extract IOCs from reported emails: URLs, attachments, sender info, headers

    Source-described action candidate under “Step 2: Build Automated Triage Pipeline”; not verified execution.

  8. 14
    Action

    Submit URLs to VirusTotal, URLScan.io for reputation check

    Source-described action candidate under “Step 2: Build Automated Triage Pipeline”; not verified execution.

  9. 15
    Action

    Submit attachments to sandbox for dynamic analysis

    Source-described action candidate under “Step 2: Build Automated Triage Pipeline”; not verified execution.

  10. 16
    Action

    Check sender against known threat intelligence feeds

    Source-described action candidate under “Step 2: Build Automated Triage Pipeline”; not verified execution.

  11. 17
    Action

    Auto-classify: confirmed phishing, spam, simulation, legitimate

    Source-described action candidate under “Step 2: Build Automated Triage Pipeline”; not verified execution.

  12. 18
    Action

    Step 3: Implement Response Actions

    Source-described action candidate under “Step 3: Implement Response Actions”; not verified execution.

  13. 19
    Action

    Confirmed phishing: auto-retract from all inboxes, block sender domain

    Source-described action candidate under “Step 3: Implement Response Actions”; not verified execution.

  14. 20
    Action

    Confirmed spam: move to junk for all recipients

    Source-described action candidate under “Step 3: Implement Response Actions”; not verified execution.

  15. 21
    Action

    Simulation email: mark as correctly reported, credit user

    Source-described action candidate under “Step 3: Implement Response Actions”; not verified execution.

  16. 22
    Output

    Legitimate email: return to inbox, notify reporter

    Source-described output candidate under “Step 3: Implement Response Actions”; not verified execution.

  17. 23
    Output

    Generate IOC report for threat intelligence team

    Source-described output candidate under “Step 3: Implement Response Actions”; not verified execution.

  18. 24
    Action

    Step 4: Create Feedback Loop

    Source-described action candidate under “Step 4: Create Feedback Loop”; not verified execution.

  19. 25
    Action

    Send automated thank-you response to reporter within 5 minutes

    Source-described action candidate under “Step 4: Create Feedback Loop”; not verified execution.

  20. 26
    Action

    Include classification result when analysis completes

    Source-described action candidate under “Step 4: Create Feedback Loop”; not verified execution.

  21. 27
    Action

    Track reporter accuracy and engagement metrics

    Source-described action candidate under “Step 4: Create Feedback Loop”; not verified execution.

  22. 28
    Action

    Recognize top reporters in monthly security newsletter

    Source-described action candidate under “Step 4: Create Feedback Loop”; not verified execution.

  23. 29
    Action

    Feed reporting metrics into security awareness training program

    Source-described action candidate under “Step 4: Create Feedback Loop”; not verified execution.

  24. 30
    Action

    Step 5: Measure and Optimize

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

  25. 31
    Action

    Track mean time to triage (target: under 10 minutes automated)

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

  26. 32
    Output

    Monitor report volume trends and false positive rates

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

  27. 33
    Action

    Measure user reporting rate in phishing simulations

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

  28. 34
    Output

    Report on confirmed threats caught by user reports vs. gateway

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

  29. 35
    Action

    Optimize automation rules based on classification accuracy

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

  30. 36
    Action

    Tools & Resources

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

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

Attention recommended

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

Medium

Network access is mentioned

6 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 6 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/building-phishing-reporting-button-workflow/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/building-phishing-reporting-button-workflow/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/building-phishing-reporting-button-workflow
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.