Detection Sigma
AgentSecOps/SecOpsAgentKit
Generic detection rule creation and management using Sigma, the universal SIEM rule format.
Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL…
Install Triaging Security Alerts In Splunk
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill triaging-security-alerts-in-splunk -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills triaging-security-alerts-in-splunk --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/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/triaging-security-alerts-in-splunk .claude/skills/triaging-security-alerts-in-splunk && 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 "triaging-security-alerts-in-splunk" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/triaging-security-alerts-in-splunk into .claude/skills/triaging-security-alerts-in-splunk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-security-alerts-in-splunk", 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/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/triaging-security-alerts-in-splunkType 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 mukul975/Anthropic-Cybersecurity-Skills --skill triaging-security-alerts-in-splunk -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills triaging-security-alerts-in-splunk --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/triaging-security-alerts-in-splunk .agents/skills/triaging-security-alerts-in-splunk && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "triaging-security-alerts-in-splunk" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/triaging-security-alerts-in-splunk into .agents/skills/triaging-security-alerts-in-splunk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-security-alerts-in-splunk", 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 mukul975/Anthropic-Cybersecurity-Skills --skill triaging-security-alerts-in-splunk -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills triaging-security-alerts-in-splunk --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/triaging-security-alerts-in-splunk .cursor/skills/triaging-security-alerts-in-splunk && 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 "triaging-security-alerts-in-splunk" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/triaging-security-alerts-in-splunk into .cursor/skills/triaging-security-alerts-in-splunk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-security-alerts-in-splunk", 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/mukul975/Anthropic-Cybersecurity-Skills.git --path skills/triaging-security-alerts-in-splunk--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 mukul975/Anthropic-Cybersecurity-Skills --skill triaging-security-alerts-in-splunk -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills triaging-security-alerts-in-splunk --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/triaging-security-alerts-in-splunk .gemini/skills/triaging-security-alerts-in-splunk && 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 "triaging-security-alerts-in-splunk" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/triaging-security-alerts-in-splunk into .gemini/skills/triaging-security-alerts-in-splunk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-security-alerts-in-splunk", 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 mukul975/Anthropic-Cybersecurity-Skills triaging-security-alerts-in-splunkInstalls 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 mukul975/Anthropic-Cybersecurity-Skills --skill triaging-security-alerts-in-splunk -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/triaging-security-alerts-in-splunk .github/skills/triaging-security-alerts-in-splunk && 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 "triaging-security-alerts-in-splunk" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/triaging-security-alerts-in-splunk into .github/skills/triaging-security-alerts-in-splunk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-security-alerts-in-splunk", 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 mukul975/Anthropic-Cybersecurity-Skills --skill triaging-security-alerts-in-splunk -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills triaging-security-alerts-in-splunk --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/triaging-security-alerts-in-splunk .opencode/skills/triaging-security-alerts-in-splunk && 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 "triaging-security-alerts-in-splunk" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/triaging-security-alerts-in-splunk into .opencode/skills/triaging-security-alerts-in-splunk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-security-alerts-in-splunk", 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
triaging-security-alerts-in-splunk- GitHub stars
- 34k
- Token cost
- ~2.1k tokens
- SKILL.md length
- 622 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 644
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL…
- Works in 7 steps: Access Incident Review and Prioritize… → Investigate the Notable Event Context → Correlate Across Data Sources → …
- SOC analysts face queued alerts from correlation searches
- SKILL.md covers When to Use, Prerequisites, Workflow and Key Concepts, plus 3 more sections
- Runs Python scripts from its folder
What it does
Triaging Security Alerts In Splunk is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when SOC analysts face queued alerts from correlation searches, need to prioritize investigation order, or must document triage decisions for handoff to Tier 2/3 analysts.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/api-reference.md` and `scripts/agent.py`).
It sits in Security. It works with Splunk. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.
When your agent uses it
- SOC analysts face queued alerts from correlation searches
- Need to prioritize investigation order
- Must document triage decisions for handoff to Tier 2/3 analysts
Example prompts
- “Use the triaging-security-alerts-in-splunk skill to triage security alerts in Splunk Enterprise Security by classifying severity, investigating…”
- “/triaging-security-alerts-in-splunk”
Requirements
- Python 3
Workflow steps
7 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 54a7988. 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
Ships 1 file in scripts/ (Python), which the agent can run.
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
Triaging Security Alerts In Splunk loads about 2.1k tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 112 tokens; SKILL.md has 622 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); the scripts in this folder are not scanned.
SKILL.md
The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 622 words, ~2,100 tokens.
Download SKILL.mdSave it as
.claude/skills/triaging-security-alerts-in-splunk/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- triaging-security-alerts-in-splunk
- description
- Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when SOC analysts face queued alerts from correlation searches, need to prioritize investigation order, or must document triage decisions for handoff to Tier 2/3 analysts.
- domain
- cybersecurity
- subdomain
- soc-operations
- tags
- soc, splunk, alert-triage, siem, notable-events, correlation-search, incident-review
- version
- 1.0
- author
- mahipal
- license
- Apache-2.0
- nist_csf
- DE.CM-01, DE.AE-02, RS.MA-01, DE.AE-06
- mitre_attack
- T1078, T1685.002, T1685.005, T1566
Triaging Security Alerts in Splunk
When to Use
Use this skill when:
- SOC Tier 1 analysts need to process the Incident Review queue in Splunk Enterprise Security (ES)
- Notable events require rapid severity classification and initial investigation before escalation
- Alert volume exceeds capacity and analysts need a systematic triage methodology
- Management requests metrics on alert disposition (true positive, false positive, benign)
Do not use for deep forensic investigation — escalate to Tier 2/3 after initial triage confirms malicious activity.
Prerequisites
- Splunk Enterprise Security 7.x+ with Incident Review dashboard configured
- CIM-normalized data sources (Windows Event Logs, firewall, proxy, endpoint)
- Role with
ess_analystcapability for notable event status updates - Familiarity with SPL (Search Processing Language)
Workflow
Step 1: Access Incident Review and Prioritize Queue
Open the Incident Review dashboard in Splunk ES. Sort notable events by urgency (calculated from severity x priority). Apply filters to focus on unassigned events:
| `notable`
| search status="new" OR status="unassigned"
| sort - urgency
| table _time, rule_name, src, dest, user, urgency, status
| head 50Focus on Critical and High urgency events first. Group related alerts by src or dest to identify attack chains rather than treating each alert independently.
Step 2: Investigate the Notable Event Context
For each notable event, pivot to raw events. Example for a brute force alert:
index=wineventlog sourcetype="WinEventLog:Security" EventCode=4625
src_ip="192.168.1.105"
earliest=-1h latest=now
| stats count by src_ip, dest, user, status
| where count > 10
| sort - countCheck if the source IP is internal (lateral movement) or external (perimeter attack). Cross-reference with asset and identity lookups:
| `notable`
| search rule_name="Brute Force Access Behavior Detected"
| lookup asset_lookup_by_cidr ip AS src OUTPUT category, owner, priority
| lookup identity_lookup_expanded identity AS user OUTPUT department, managedBy
| table _time, src, dest, user, category, owner, departmentStep 3: Correlate Across Data Sources
Check if the same source appears in other telemetry:
index=proxy OR index=firewall src="192.168.1.105" earliest=-24h
| stats count by index, sourcetype, action, dest_port
| sort - countLook for corroborating evidence: Did the same IP also trigger DNS anomalies, proxy blocks, or endpoint detection alerts?
index=main sourcetype="cisco:asa" src="192.168.1.105" action=blocked earliest=-24h
| timechart span=1h count by dest_portStep 4: Check Threat Intelligence Enrichment
Query the threat intelligence framework for known IOCs:
| `notable`
| search search_name="Threat - Threat Intelligence Match - Rule"
| lookup threat_intel_by_ip ip AS src OUTPUT threat_collection, threat_description, threat_key
| table _time, src, dest, threat_collection, threat_description, weight
| where weight >= 3For domains, check against threat lists:
| tstats count from datamodel=Web where Web.url="*evil-domain.com*" by Web.src, Web.url, Web.status
| rename Web.* AS *Step 5: Classify and Disposition the Alert
Update the notable event status in Incident Review:
| Disposition | Criteria | Action |
|---|---|---|
| True Positive | Corroborating evidence confirms malicious activity | Escalate to Tier 2, create incident ticket |
| Benign True Positive | Alert fired correctly but activity is authorized (e.g., pen test) | Close with comment, add suppression if recurring |
| False Positive | Alert logic matched benign behavior | Close, tune correlation search, document pattern |
| Undetermined | Insufficient data to classify | Assign to Tier 2 with investigation notes |
Update via Splunk ES UI or REST API:
| sendalert update_notable_event param.status="2" param.urgency="critical"
param.comment="Confirmed brute force from compromised workstation. Escalated to IR-2024-0431."
param.owner="analyst_jdoe"Step 6: Document Triage Findings
Record in the notable event comment field:
- Source/destination involved
- Data sources examined
- Correlation findings (related alerts, TI matches)
- Disposition rationale
- Next steps for escalation
| `notable`
| search rule_name="Brute Force*" status="closed"
| stats count by status_label, disposition
| addtotalShow full SKILL.md (244 more words)Show less
Step 7: Track Triage Metrics
Monitor triage performance over time:
| `notable`
| where status_end > 0
| eval triage_time = status_end - _time
| stats avg(triage_time) AS avg_triage_sec, median(triage_time) AS med_triage_sec,
count by rule_name, status_label
| eval avg_triage_min = round(avg_triage_sec/60, 1)
| sort - count
| table rule_name, status_label, count, avg_triage_minKey Concepts
| Term | Definition |
|---|---|
| Notable Event | Splunk ES alert generated by a correlation search that meets defined risk or threshold criteria |
| Urgency | Calculated field combining event severity with asset/identity priority (Critical/High/Medium/Low/Informational) |
| Correlation Search | Scheduled SPL query that detects threat patterns and generates notable events when conditions match |
| CIM | Common Information Model — Splunk's normalized field naming convention enabling cross-source queries |
| Disposition | Final classification of an alert: true positive, false positive, benign true positive, or undetermined |
| MTTD/MTTR | Mean Time to Detect / Mean Time to Respond — key SOC metrics measuring detection and resolution speed |
Tools & Systems
- Splunk Enterprise Security: SIEM platform providing Incident Review dashboard, correlation searches, and risk-based alerting
- Splunk SOAR (Phantom): Orchestration platform for automating triage playbooks and enrichment actions
- Asset & Identity Framework: Splunk ES lookup tables mapping IPs to asset owners and users to departments for context enrichment
- Threat Intelligence Framework: Splunk ES module ingesting STIX/TAXII feeds and matching IOCs against notable events
Common Scenarios
- Brute Force Alerts: Correlate EventCode 4625 (failed logon) with 4624 (successful logon) from same source to determine if attack succeeded
- Malware Detection: Cross-reference endpoint AV alert with proxy logs for C2 callback confirmation
- Data Exfiltration Alert: Check outbound data volume from DLP and proxy logs against user baseline
- Privilege Escalation: Correlate EventCode 4672 (special privileges assigned) with 4720 (account created) from non-admin users
- Lateral Movement: Map EventCode 4648 (explicit credential logon) across multiple destinations from single source
Output Format
TRIAGE REPORT — Notable Event #NE-2024-08921
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Alert: Brute Force Access Behavior Detected
Time: 2024-03-15 14:23:07 UTC
Source: 192.168.1.105 (WORKSTATION-042, Finance Dept)
Destination: 10.0.5.20 (DC-PRIMARY, Domain Controller)
User: jsmith (Finance Analyst)
Investigation:
- 847 failed logons (4625) in 12 minutes from src
- Successful logon (4624) at 14:35:02 after brute force
- No proxy/DNS anomalies from src in prior 24h
- Source not on threat intel lists
Disposition: TRUE POSITIVE — Compromised credential
Action: Escalated to Tier 2, ticket IR-2024-0431 created
Account jsmith disabled pending password reset© mukul975, 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 3 other files (scripts, references) in skills/triaging-security-alerts-in-splunk of mukul975/Anthropic-Cybersecurity-Skills.
- SKILL.md
- LICENSE
- references/api-reference.md
- scripts/agent.py
Open the folder on GitHubat commit 54a7988
Compare with similar skills
Triaging Security Alerts In Splunk 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 |
|---|---|---|---|---|---|---|
| Triaging Security Alerts In Splunk this skillmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Detection SigmaAgentSecOps/SecOpsAgentKit | 220 | 1 repos | ~4k | Automated safety check: Pass | Custom licence | |
| Siem Detectionbriiirussell/cybersecurity-skills | 413 | — | ~2.6k | Automated safety check: Notes | MIT | |
| Doca ArgusNVIDIA/skills | 3.6k | — | ~4.8k | Automated safety check: Pass | Apache-2.0 | |
| Hunting Threatstrilwu/secskills | 157 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Siem Loggingancoleman/ai-design-components | 525 | — | ~3.4k | Automated safety check: Pass | MIT |
Similar skills
Siem Detection
briiirussell/cybersecurity-skills
Engineer and audit SIEM detection rules — log source coverage, Sigma / KQL / SPL / Elastic query authoring, MITRE ATT&CK mapping, false-positive tuning, and detection-as-code workflows.
- Official
Doca Argus
NVIDIA/skills
A skill your agent uses when the user is deploying or operating the DOCA Argus Service — the packaged BlueField-side runtime-security container that watches the BlueField and attached host for…
Hunting Threats
trilwu/secskills
Run hypothesis-driven threat hunts across endpoint, network, cloud, and identity telemetry using stack counting, outlier analysis, and ATT&CK-based hypotheses, with SIEM query patterns for Splunk…
Siem Logging
ancoleman/ai-design-components
Configure security information and event management (SIEM) systems for threat detection, log aggregation, and compliance.
Breach Forensics
mukul975/Privacy-Data-Protection-Skills
Conducts digital forensics investigations following a personal data breach, covering evidence preservation, chain of custody documentation, log analysis, scope determination, and root cause analysis.
More from mukul975/Anthropic-Cybersecurity-Skills
All 644 skills in this repoCampaign Attribution Evidence Analysis
mukul975/Anthropic-Cybersecurity-Skills
Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.
Go Malware Analysis in Ghidra
mukul975/Anthropic-Cybersecurity-Skills
Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.
LNK and Jump List Forensics
mukul975/Anthropic-Cybersecurity-Skills
Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.
Malware Persistence Analysis with Autoruns
mukul975/Anthropic-Cybersecurity-Skills
Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.
NTFS MFT Deleted File Recovery
mukul975/Anthropic-Cybersecurity-Skills
Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.
Network Covert Channel Analysis
mukul975/Anthropic-Cybersecurity-Skills
Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.
Related
Works with
Categories
Questions about Triaging Security Alerts In Splunk
What does Triaging Security Alerts In Splunk do?
Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL…. Triaging Security Alerts In Splunk is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard.
When should I use Triaging Security Alerts In Splunk?
Triaging Security Alerts In Splunk fits situations like: SOC analysts face queued alerts from correlation searches; need to prioritize investigation order; must document triage decisions for handoff to Tier 2/3 analysts.
How do I install Triaging Security Alerts In Splunk in Claude Code?
Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill triaging-security-alerts-in-splunk -a claude-code`. Or copy the skill folder (skills/triaging-security-alerts-in-splunk in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/triaging-security-alerts-in-splunk in your project. Claude Code loads it when a task matches its description.
How do I install Triaging Security Alerts In Splunk in Codex?
Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill triaging-security-alerts-in-splunk -a codex`. Or copy the skill folder (skills/triaging-security-alerts-in-splunk in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/triaging-security-alerts-in-splunk in your project. Codex loads it when a task matches its description.
Can I use Triaging Security Alerts In Splunk 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 mukul975/Anthropic-Cybersecurity-Skills --skill triaging-security-alerts-in-splunk -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triaging-security-alerts-in-splunk, .gemini/skills/triaging-security-alerts-in-splunk, .github/skills/triaging-security-alerts-in-splunk and .opencode/skills/triaging-security-alerts-in-splunk in your project.
What does Triaging Security Alerts In Splunk need to run?
Going by SKILL.md and its folder, Triaging Security Alerts In Splunk needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Triaging Security Alerts In Splunk 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 Triaging Security Alerts In Splunk 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Triaging Security Alerts In Splunk use?
Triaging Security Alerts In Splunk is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Triaging Security Alerts In Splunk use?
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 535 tokens, read only when the agent opens those files.
What are the alternatives to Triaging Security Alerts In Splunk?
Skills that share tags, products or a category with Triaging Security Alerts In Splunk: Detection Sigma (AgentSecOps/SecOpsAgentKit, 220 stars), Siem Detection (briiirussell/cybersecurity-skills, 413 stars), Doca Argus (NVIDIA/skills, 3.6k stars) and Hunting Threats (trilwu/secskills, 157 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Triaging Security Alerts In Splunk?
mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.
Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.