Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Alert Triage

ASecurity

Triage a SIEM/EDR alert end-to-end — validate it's real, enrich and scope it, reach a consistent verdict, and decide escalate vs. close with documented rationale. Use when working a SOC alert queue and you need a repeatable, defensible triage.

8 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/19/2026

$npx -y skills add jassics/awesome-claude-security --skill alert-triage --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Alert Triage?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Alert Triage
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jassics-alert-triage/badge)](https://www.skillsdirectory.com/skills/jassics-alert-triage)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: alert-triage
description: >-
  Triage a SIEM/EDR alert end-to-end — validate it's real, enrich and scope it,
  reach a consistent verdict, and decide escalate vs. close with documented rationale.
  Use when working a SOC alert queue and you need a repeatable, defensible triage.
---

# Goal

A consistent, evidence-backed verdict on an alert — true positive / false positive /
benign-true-positive — with the right next action (escalate, close, tune) and a
record that the next analyst can follow.

# Steps

1. **Understand the alert** — what detection fired, the underlying logic, the ATT&CK
   technique, and why it triggered. Read the rule, don't guess.
2. **Validate** — is this real activity or a known false-positive pattern? Confirm
   against the source telemetry, not just the alert summary.
3. **Enrich** — add context: user/asset criticality, the involved IOCs
   (`threat-intelligence:ioc-enrichment`), process lineage, recent related alerts,
   and whether it matches known-good behavior.
4. **Scope** — pivot to see if it's isolated or part of a broader pattern (same host/
   user/campaign, lateral movement). Check for related alerts you should correlate.
5. **Decide & act:**
   - **Escalate** → `dfir:incident-response` for confirmed/likely incidents, with the
     evidence package and scope assembled.
   - **Close** → document why (benign/expected), preserving the rationale.
   - **Tune** → recurring false positive → feed back to
     `detection-engineering:detection-rule-development` (don't just mute).
6. **Record** — verdict, evidence, actions, and timestamps.

# Output

A triage record: alert · ATT&CK technique · verdict · evidence · scope · action
(escalate/close/tune) · rationale. Confirmed incidents → `dfir`; recurring FPs →
`detection-engineering`.

# Notes

Consistency is the goal — the same alert should get the same verdict regardless of
analyst. Always validate against source telemetry before deciding, and feed recurring
false positives back into detection tuning rather than muting them (muting hides the
problem and erodes coverage). Preserve evidence and rationale for every verdict.

Attribution

jassicsjassics
View sourceSee grades on GitHubMore from jassics →
SSkills Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

696561 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes
View all in ai-agents →