Skip to content
Development
Skill

/triage-security-incident

Triage a suspected incident across endpoints, identities, applications, cloud resources, networks, or data. Use when an alert, compromise, disruption, unauthorized access, malware, credential concern, or exposure needs scope and ownership.

From plugin
socket
7200 skills5 MCP
Install
$ npx -y skills add gaelic-ghost/socket --skill triage-security-incident --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/triage-security-incident

Context preview

The summary Claude sees to decide when to auto-load this skill.

Triage a suspected incident across endpoints, identities, applications, cloud resources, networks, or data. Use when an alert, compromise, disruption, unauthorized access, malware, credential concern, or exposure needs scope and ownership.

SKILL.md

triage-security-incident.SKILL.md
name: triage-security-incident
description: Triage a suspected incident across endpoints, identities, applications, cloud resources, networks, or data. Use when an alert, compromise, disruption, unauthorized access, malware, credential concern, or exposure needs scope and ownership.

Triage Security Incident

Overview

Establish whether coordinated response is needed, what may be affected, and who owns decisions. Preserve uncertainty and avoid destructive cleanup while urgent harm reduction and evidence collection are balanced.

Read [references/incident-triage-record.md](references/incident-triage-record.md) for the initial record aligned with current NIST incident-response guidance.

Workflow

1. Open the incident record.

  • Record reporter, detection source, time/timezone, symptoms, affected person/system, current status, and incident lead.

2. Validate the signal.

  • Preserve the original alert/report and confirm artifact, account, host, service, or event identity.
  • Separate direct observation, external intelligence, automation labels, and speculation.

3. Estimate scope and urgency.

  • Identify potentially affected assets, identities, data, users, environments, business function, privileges, and time window.
  • Record ongoing execution, access, exfiltration, destruction, fraud, safety, or service impact.

4. Decide immediate harm reduction.

  • Choose reversible isolation, session/token revocation, feature disablement, traffic control, or monitoring only when evidence and authority justify it.
  • State evidence loss and operational impact.

5. Preserve priority evidence.

  • Capture volatile state, logs, artifacts, identity/provider records, application events, network evidence, and timeline sources proportionately.

6. Establish coordination.

  • Name technical, business, legal/privacy, communications, vendor/provider, and affected-user contacts as applicable; keep sensitive details need-to-know.

7. Route the next phase.

  • Use containment for ongoing harm, hunting for scope, specialist analysis for evidence, and recovery only after eradication criteria are defined.

Output

Return incident identity/owner, signal confidence, affected/potential scope, urgency, immediate actions, evidence plan, contacts, open questions, and next phase.

Read more
Ships withsocket

Stuff for Agents on macOS Promo audio: Socket Codex Marketplace Promo

Get the whole plugin

Other skills on socket.