Back to catalog
Static reviewDevelopment

Skill dossier

triaging-security-incident-with-ir-playbook

Source declaration

Classifies and prioritizes security incidents using structured IR playbooks and SIEM/case-management queries (Splunk, TheHive) to determine severity, assign response teams, and initiate the appropriate response procedures. Use when a new SOC alert needs triage, multiple concurrent incidents require prioritization, or automated triage rules need validation or tuning.

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

Classifies and prioritizes security incidents using structured IR playbooks and SIEM/case-management queries (Splunk, TheHive) to determine severity, assign response teams, and initiate the appropriate response procedures. Use when a new SOC alert needs triage, multiple concurrent incidents require prioritization, or automated triage rules need validation or tuning.

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.

Classifies and prioritizes security incidents using structured IR playbooks and SIEM/case-management queries (Splunk, TheHive) to determine severity, assign response teams, and initiate the appropriate response procedures. Use when a new SOC alert needs triage, multiple concurrent incidents require prioritization, or automated triage rules need validation or tuning. 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/triaging-security-incident-with-ir-playbook/SKILL.md:L48]
  • Step 1: Receive and Acknowledge Alert [Source statement; provisional, not tested. Evidence: skills/triaging-security-incident-with-ir-playbook/SKILL.md:L50]
  • Step 2: Enrich Alert Data [Source statement; provisional, not tested. Evidence: skills/triaging-security-incident-with-ir-playbook/SKILL.md:L69]
  • Step 3: Classify Incident Type [Source statement; provisional, not tested. Evidence: skills/triaging-security-incident-with-ir-playbook/SKILL.md:L88]
  • Step 4: Assign Severity Level [Source statement; provisional, not tested. Evidence: skills/triaging-security-incident-with-ir-playbook/SKILL.md:L101]
  • Step 5: Select and Initiate Playbook [Source statement; provisional, not tested. Evidence: skills/triaging-security-incident-with-ir-playbook/SKILL.md:L130]
  • Step 6: Assign Response Team [Source statement; provisional, not tested. Evidence: skills/triaging-security-incident-with-ir-playbook/SKILL.md:L155]
  • Step 7: Document Triage Decision and Hand Off [Source statement; provisional, not tested. Evidence: skills/triaging-security-incident-with-ir-playbook/SKILL.md:L181]

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/triaging-security-incident-with-ir-playbook/SKILL.md:L1-L29]

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

File inventory

PathTypeBytes
skills/triaging-security-incident-with-ir-playbook/assets/template.mdReference2.9 KB
skills/triaging-security-incident-with-ir-playbook/LICENSEOther11 KB
skills/triaging-security-incident-with-ir-playbook/references/api-reference.mdReference1.9 KB
skills/triaging-security-incident-with-ir-playbook/references/standards.mdReference2.3 KB
skills/triaging-security-incident-with-ir-playbook/references/workflows.mdReference4.6 KB
skills/triaging-security-incident-with-ir-playbook/scripts/agent.pyScript8.5 KB
skills/triaging-security-incident-with-ir-playbook/scripts/process.pyScript15.2 KB
skills/triaging-security-incident-with-ir-playbook/SKILL.mdInstruction8.6 KB

SKILL.md frontmatter

{
  "name": "triaging-security-incident-with-ir-playbook",
  "description": "Classifies and prioritizes security incidents using structured IR playbooks and SIEM/case-management queries (Splunk, TheHive) to determine severity, assign response teams, and initiate the appropriate response procedures. Use when a new SOC alert needs triage, multiple concurrent incidents require prioritization, or automated triage rules need validation or tuning.",
  "domain": "cybersecurity",
  "subdomain": "incident-response",
  "tags": [
    "incident-response",
    "triage",
    "playbook",
    "severity-classification",
    "soc"
  ],
  "mitre_attack": [
    "T1486",
    "T1490",
    "T1070",
    "T1078"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "RS.MA-01",
    "RS.MA-02",
    "RS.AN-03",
    "RC.RP-01"
  ]
}

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
    Input

    Step 1: Receive and Acknowledge Alert

    Source-described input candidate under “Step 1: Receive and Acknowledge Alert”; not verified execution.

  4. 04
    Action

    Step 2: Enrich Alert Data

    Source-described action candidate under “Step 2: Enrich Alert Data”; not verified execution.

  5. 05
    Action

    Step 3: Classify Incident Type

    Source-described action candidate under “Step 3: Classify Incident Type”; not verified execution.

  6. 06
    Action

    Step 4: Assign Severity Level

    Source-described action candidate under “Step 4: Assign Severity Level”; not verified execution.

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

    Step 5: Select and Initiate Playbook

    Source-described action candidate under “Step 5: Select and Initiate Playbook”; not verified execution.

  2. 08
    Action

    Step 6: Assign Response Team

    Source-described action candidate under “Step 6: Assign Response Team”; not verified execution.

  3. 09
    Action

    Step 7: Document Triage Decision and Hand Off

    Source-described action candidate under “Step 7: Document Triage Decision and Hand Off”; not verified execution.

  4. 10
    Action

    Key Concepts

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

  5. 11
    Action

    Tools & Systems

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

  6. 12
    Action

    Common Scenarios

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

  7. 13
    Decision

    Brute Force Alert: Multiple failed logins from single IP. Enrich IP reputation, check geo-location, verify if account was compromised, assign P3 if unsuccessful.

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

  8. 14
    Decision

    Malware Detection on Endpoint: AV/EDR quarantined malware. Verify quarantine success, check for lateral movement, assign P2 if persistence detected.

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

  9. 15
    Decision

    Suspicious Outbound Traffic: Large data transfer to unknown external IP. Check if known cloud service, verify data classification, assign P1 if exfiltration confirmed.

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

  10. 16
    Decision

    Phishing Email Reported: User reports suspicious email. Extract IOCs, check if others received it, assign P2 if credentials were entered.

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

  11. 17
    Decision

    Privilege Escalation: User gained admin rights unexpectedly. Verify if authorized change, check for exploitation, assign P1 if unauthorized.

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

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

72 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

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

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

7 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 7 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/triaging-security-incident-with-ir-playbook/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/triaging-security-incident-with-ir-playbook/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/triaging-security-incident-with-ir-playbook
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.