analyzing-security-logs-with-splunk

Leverages Splunk Enterprise Security and SPL (Search Processing Language) to investigate security incidents through log correlation, timeline reconstruction, and anomaly detection. Covers Windows event logs, firewall logs, proxy logs, and authentication data analysis. Activates for requests involving Splunk investigation, SPL queries, SIEM log analysis, security event correlation, or log-based incident investigation.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable Splunk investigation skill with concrete SPL and a clear workflow, weakened mainly by orphaned bundle files and slightly non-paste-ready multi-query code blocks. Conciseness and actionability are solid but not maximal.

Suggestions

Link the bundle files from the body — e.g., add a '## Programmatic access' section pointing to [references/api-reference.md](references/api-reference.md) and document scripts/agent.py's purpose — so progressive disclosure is properly signaled.

Split multi-query ```spl blocks so each search is its own fenced block, and replace '| comment' lines with markdown prose or '#'-style comments Splunk accepts, making the examples copy-paste runnable.

Trim the Key Concepts glossary to the few Splunk-specific terms Claude would not already know (e.g., CIM, Notable Event, Correlation Search) and drop generic entries like SPL/Sourcetype to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Mostly efficient — short framing sentences plus concrete SPL — but the Key Concepts glossary and inline code comments ('\| Detect brute force...') are slightly more than minimal and could be trimmed; not 5 because not every token earns its place.	4 / 5
Actionability	Each individual query is real, executable SPL covering common cases (brute force, pass-the-hash, LSASS, DNS tunneling, exfiltration), but several queries are stacked in a single ```spl block with '\|'-prefixed comment lines that would error if pasted whole, so it is not fully copy-paste ready.	4 / 5
Workflow Clarity	A clearly sequenced six-step workflow (Scope → Auth → Process → Network → Timeline → Detections) where Step 1 scoping acts as an implicit checkpoint; the skill is read-only so the destructive-cap does not apply, but explicit validation/feedback loops are absent, capping it below 5.	4 / 5
Progressive Disclosure	The body has good section headers but never references the available bundle files — references/api-reference.md (splunk SDK + REST endpoints) and scripts/agent.py are orphaned — so references are present as files yet not signaled, and content that could live separately remains inline.	3 / 5
	Total	15 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states capabilities and provides an explicit activation clause with multiple natural trigger terms. It is comprehensive, distinct, and free of vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'log correlation, timeline reconstruction, and anomaly detection' — plus coverage of Windows event logs, firewall logs, proxy logs, and authentication data analysis, giving comprehensive domain coverage.	5 / 5
Completeness	Explicitly answers both 'what' (Leverages Splunk ES and SPL to investigate incidents...) and 'when' ('Activates for requests involving...') with concrete trigger phrases, matching the anchor 5 example structure.	5 / 5
Trigger Term Quality	Rich natural trigger phrases with synonyms — 'Splunk investigation, SPL queries, SIEM log analysis, security event correlation, or log-based incident investigation' — covering the terms a SOC analyst would naturally say.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear Splunk/SIEM incident-investigation niche with distinct, product-specific triggers, making conflict with unrelated skills minimal.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: mukul975/Anthropic-Cybersecurity-Skills
Path: skills/analyzing-security-logs-with-splunk/SKILL.md
Commit: 9429fe9

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.