Security Alert Triage
elastic/agent-skills
Triage Elastic Security alerts — gather context, classify threats, create cases, and acknowledge.
Triage a security alert or case. An agent skill from dandye/ai-runbooks.
Install Triage Alert
$ npx skills add dandye/ai-runbooks --skill triage-alert -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dandye/ai-runbooks triage-alert --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/triage-alert .claude/skills/triage-alert && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "triage-alert" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/triage-alert into .claude/skills/triage-alert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-alert", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dandye/ai-runbooks/tree/main/skills/triage-alertType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dandye/ai-runbooks --skill triage-alert -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dandye/ai-runbooks triage-alert --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/triage-alert .agents/skills/triage-alert && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "triage-alert" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/triage-alert into .agents/skills/triage-alert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-alert", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dandye/ai-runbooks --skill triage-alert -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dandye/ai-runbooks triage-alert --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/triage-alert .cursor/skills/triage-alert && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "triage-alert" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/triage-alert into .cursor/skills/triage-alert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-alert", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dandye/ai-runbooks.git --path skills/triage-alert--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dandye/ai-runbooks --skill triage-alert -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dandye/ai-runbooks triage-alert --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/triage-alert .gemini/skills/triage-alert && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "triage-alert" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/triage-alert into .gemini/skills/triage-alert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-alert", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dandye/ai-runbooks triage-alertInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dandye/ai-runbooks --skill triage-alert -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/triage-alert .github/skills/triage-alert && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "triage-alert" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/triage-alert into .github/skills/triage-alert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-alert", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dandye/ai-runbooks --skill triage-alert -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dandye/ai-runbooks triage-alert --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/triage-alert .opencode/skills/triage-alert && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "triage-alert" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/triage-alert into .opencode/skills/triage-alert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-alert", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
triage-alert- GitHub stars
- 127
- Token cost
- ~1.2k tokens
- SKILL.md length
- 439 words
- Files
- 2
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Triage a security alert or case. An agent skill from dandye/ai-runbooks.
- Works in 6 steps: Gather Initial Context → Find Related Open Cases → Alert-Specific SIEM Search → …
- Given an ALERTID
- SKILL.md covers Inputs, Workflow, Output Requirements and Quick Reference
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Triage Alert is an agent skill from dandye/ai-runbooks. Triage a security alert or case. Use when given an ALERTID or CASEID to assess if it's a real threat. Enriches IOCs, searches SIEM for context, and determines if the alert should be closed (false positive) or escalated for investigation.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).
It sits in Security, covering Security operations. The licence is Apache-2.0.
When your agent uses it
- Given an ALERTID
- CASEID to assess if its a real threat
Example prompts
- “/triage-alert”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 72a6863. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Triage Alert loads about 1.2k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 439 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from dandye/ai-runbooks at commit 72a6863, republished under its Apache-2.0 licence (© dandye). 439 words, ~1,217 tokens.
Download SKILL.mdSave it as
.claude/skills/triage-alert/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- triage-alert
- description
- Triage a security alert or case. Use when given an ALERT_ID or CASE_ID to assess if it's a real threat. Enriches IOCs, searches SIEM for context, and determines if the alert should be closed (false positive) or escalated for investigation.
- type
- Skill
- required_roles.chronicle
- roles/chronicle.viewer
- required_roles.soar
- roles/chronicle.editor
- required_roles.gti
- GTI Standard
- personas
- tier1-analyst, tier2-analyst, tier3-analyst, incident-responder
- generated.by
- human:dandye
- generated.at
- 2026-02-04T06:10:49-05:00
Alert Triage Skill
Perform standardized initial assessment of security alerts to determine if they represent real threats requiring investigation or can be closed as false positives.
Inputs
You need one of these identifiers to begin:
ALERT_ID- The alert identifierCASE_ID- The case identifier
Workflow
Step 1: Gather Initial Context
Retrieve full details about the alert/case:
Use secops-soar tools:
- get_case_full_details(case_id) - Get case metadata and context
- list_alerts_by_case(case_id) - List all alerts in the case
- list_events_by_alert(alert_id) - Get triggering eventsExtract and note:
- Alert type and severity
- Key entities involved (IPs, domains, hashes, users, hostnames)
- Triggering events and timestamps
Note: Duplicate detection should be handled by invoking
/check-duplicatesbefore this skill, or by using the/full-triage-alertworkflow which orchestrates both skills in the correct sequence.
Step 2: Find Related Open Cases
Search for other open cases involving the same entities:
Use secops-soar.list_cases with:
- Search terms = key entities from Step 1
- Status filter = "Opened"Note any related cases for correlation.
Step 3: Alert-Specific SIEM Search
Perform a targeted SIEM search based on the alert type:
Use secops-mcp.search_security_events with relevant queryBy alert type:
- Suspicious Login: Search login events (success/failure) for user/source IP around alert time
- Malware Detection: Search process execution, file mods, network events for the hash/endpoint
- Network Alert: Search network flows, DNS lookups for source/destination IPs/domains
Step 4: Enrich Key Entities
For each key entity (IP, domain, hash, URL), gather threat intelligence:
GTI Enrichment (use gti-mcp tools):
get_ip_address_report(ip)- IP reputation and contextget_domain_report(domain)- Domain reputationget_file_report(hash)- File/hash analysisget_url_report(url)- URL reputation
SIEM Enrichment (use secops-mcp tools):
lookup_entity(entity)- Entity summary from SIEMget_ioc_matches(hours_back)- Check if IOC appears in threat feeds
Step 5: Make Assessment
Based on all gathered evidence, classify the alert:
| Classification | Criteria | Action |
|---|---|---|
| False Positive (FP) | No malicious indicators, known benign activity | Close |
| Benign True Positive (BTP) | Real detection but authorized/expected activity | Close |
| True Positive (TP) | Confirmed malicious indicators or suspicious behavior | Escalate |
| Suspicious | Inconclusive but warrants investigation | Escalate |
Show full SKILL.md (162 more words)Show less
Step 6: Take Action
If FP or BTP:
- Document findings in case comments explaining the rationale
- Close the case/alert:
- Use
secops-soar.siemplify_close_caseorsiemplify_close_alert - Closure reason:
NOT_MALICIOUS - Root cause: Use
get_case_settings_root_causesto get valid options (e.g., "Legit action", "Normal behavior")
- Use
If TP or Suspicious:
- Optionally adjust priority with
secops-soar.change_case_priority - Document initial findings and assessment in case comments
- Escalate to Tier 2 or trigger appropriate investigation runbook:
- Suspicious login →
suspicious_login_triage - Malware →
malware_triage - IOC-focused →
deep_dive_ioc_analysis
- Suspicious login →
Output Requirements
After completing triage, provide:
- Alert Status: Closed (with reason) or Escalated
- Classification: FP, BTP, TP, or Suspicious
- Evidence Summary: Key findings from enrichment and SIEM searches
- Rationale: Why this classification was chosen
- Next Steps: What happens next (closed, assigned to whom, which runbook triggered)
Quick Reference
SOAR Tools:
get_case_full_details,list_alerts_by_case,list_events_by_alertpost_case_comment,change_case_prioritysiemplify_get_similar_cases,siemplify_close_case,siemplify_close_alert
SIEM Tools:
lookup_entity,get_ioc_matches,search_security_events
GTI Tools:
get_file_report,get_domain_report,get_ip_address_report,get_url_report
For detailed workflow diagrams, completion criteria, and evaluation rubric, see reference.md.
© dandye, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/triage-alert of dandye/ai-runbooks.
- SKILL.md
- reference.md
Open the folder on GitHubat commit 72a6863
Compare with similar skills
Triage Alert next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Triage Alert this skilldandye/ai-runbooks | 127 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Security Alert Triageelastic/agent-skills | 592 | 1 repos | ~3.5k | Automated safety check: Notes | Apache-2.0 | |
| Kubernetes Network Security Auditkubeshark/kubeshark | 12k | — | ~7.3k | Automated safety check: Notes | Apache-2.0 | |
| Security Detection Rule Managementelastic/agent-skills | 592 | 1 repos | ~3.9k | Automated safety check: Notes | Apache-2.0 | |
| Chaitin CLIchaitin/chaitin-cli | 115 | — | ~15k | Automated safety check: Notes | GPL-3.0 | |
| GatesNebulock-Inc/agentic-threat-hunting-framework | 388 | — | ~12k | Automated safety check: Pass | MIT |
Similar skills
- Official
Kubernetes Network Security Audit
kubeshark/kubeshark
Hunts for compromised workloads and malicious traffic in a Kubernetes cluster by sweeping network data through Kubeshark MCP, mapped to MITRE ATT&CK.
- Official
Security Detection Rule Management
elastic/agent-skills
Create, tune, and manage Elastic Security detection rules (SIEM and Endpoint).
Chaitin CLI
chaitin/chaitin-cli
A skill your agent uses when running chaitin-cli commands to manage Chaitin security products: SafeLine WAF (site management, IP blocking, ACL, policy rules, attack logs), X-Ray vulnerability…
Gates
Nebulock-Inc/agentic-threat-hunting-framework
GATES method validation for hunt-derived detections. An agent skill from Nebulock-Inc/agentic-threat-hunting-framework.
Elasticsearch Audit
aspectrr/deer
Enable, configure, and query Elasticsearch security audit logs.
More from dandye/ai-runbooks
All 27 skills in this repoClose Case Artifact
dandye/ai-runbooks
Close a case or alert with proper reason and documentation. An agent skill from dandye/ai-runbooks.
Correlate Ioc
dandye/ai-runbooks
Check for existing SIEM alerts and case management entries related to IOCs.
Deep Dive Ioc
dandye/ai-runbooks
Perform exhaustive analysis of a critical IOC. An agent skill from dandye/ai-runbooks.
Enrich Ioc
dandye/ai-runbooks
Enrich an IOC (IP, domain, hash, URL) with threat intelligence.
Find Relevant Case
dandye/ai-runbooks
Search for existing cases related to specific indicators or entities.
Full Alert Triage
dandye/ai-runbooks
Complete Tier 1 triage workflow. An agent skill from dandye/ai-runbooks.
Related
Categories
Questions about Triage Alert
What does Triage Alert do?
Triage a security alert or case. An agent skill from dandye/ai-runbooks. Triage Alert is an agent skill from dandye/ai-runbooks. Triage a security alert or case.
When should I use Triage Alert?
Triage Alert fits situations like: given an ALERTID; CASEID to assess if its a real threat.
How do I install Triage Alert in Claude Code?
Run `npx skills add dandye/ai-runbooks --skill triage-alert -a claude-code`. Or copy the skill folder (skills/triage-alert in dandye/ai-runbooks) into .claude/skills/triage-alert in your project. Claude Code loads it when a task matches its description.
How do I install Triage Alert in Codex?
Run `npx skills add dandye/ai-runbooks --skill triage-alert -a codex`. Or copy the skill folder (skills/triage-alert in dandye/ai-runbooks) into .agents/skills/triage-alert in your project. Codex loads it when a task matches its description.
Can I use Triage Alert in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dandye/ai-runbooks --skill triage-alert -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triage-alert, .gemini/skills/triage-alert, .github/skills/triage-alert and .opencode/skills/triage-alert in your project.
What does Triage Alert need to run?
SKILL.md names no scripts, command-line tools or credentials: Triage Alert is instructions for the agent only.
Does Triage Alert access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Triage Alert safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Triage Alert use?
Triage Alert is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Triage Alert use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Triage Alert?
Skills that share tags, products or a category with Triage Alert: Security Alert Triage (elastic/agent-skills, 592 stars), Kubernetes Network Security Audit (kubeshark/kubeshark, 12k stars), Security Detection Rule Management (elastic/agent-skills, 592 stars) and Chaitin CLI (chaitin/chaitin-cli, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Triage Alert?
dandye (a GitHub user) maintains it in dandye/ai-runbooks, which has 127 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on August 14, 2026.
Source: dandye/ai-runbooks on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.