analyzing-dns-logs-for-exfiltration

Analyzes DNS query logs to detect data exfiltration via DNS tunneling, DGA domain communication, and covert C2 channels using entropy analysis, query volume anomalies, and subdomain length detection in SIEM platforms. Use when SOC teams need to identify DNS-based threats that bypass traditional network security controls.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

The body is highly actionable with executable SPL and Python, but it pads concepts Claude already knows and fails to route to its own bundle files, leaving them unreferenced. Tightening the redundant sections and linking the reference/script would lift conciseness and progressive disclosure.

Suggestions

Trim or remove the 'Key Concepts' and 'Tools & Systems' sections — Claude already knows what DNS tunneling, Shannon entropy, DoH, Splunk Stream, and Zeek are; keep only non-obvious thresholds or field offsets.

Add explicit links from the body to the bundle files (e.g., 'Full query library and API keys: see references/api-reference.md; runnable detector: see scripts/agent.py') and move the duplicated Splunk queries out of the body to avoid duplication.

Compress the ASCII 'Output Format' block to a short schema/field list instead of a 30-line mock report to recover token budget.

Dimension	Reasoning	Score
Conciseness	The dense SPL and Python blocks earn their tokens, but the 'Key Concepts' and 'Tools & Systems' sections restate concepts Claude already knows (what DNS tunneling, Shannon entropy, DoH, Splunk Stream, and Zeek are) and the 30-line ASCII 'Output Format' block is illustrative padding.	3 / 5
Actionability	Provides copy-paste-ready Splunk SPL with real index/sourcetype filters, a working Python shannon_entropy function, concrete numeric thresholds, and named tool signatures, fully covering the common detection cases.	5 / 5
Workflow Clarity	Six detection steps are clearly sequenced end-to-end, but validation/verification checkpoints are only implicit (e.g., no 'confirm against baseline before alerting' or false-positive triage step); this is a read-only analysis skill so the destructive-operation cap does not apply.	4 / 5
Progressive Disclosure	Section structure and one-level-deep bundle files (references/api-reference.md, scripts/agent.py) exist, but the body never links to them and inlines substantial content duplicated in api-reference.md, so references are present but not clearly signaled.	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.

The description is specific, trigger-rich, and clearly answers both what the skill does and when to use it, with a well-bounded niche. It is among the strongest reference examples and needs no revision.

Dimension	Reasoning	Score
Specificity	Names three concrete detection targets (DNS tunneling, DGA domain communication, covert C2 channels) and the specific methods used (entropy analysis, query volume anomalies, subdomain length detection) in SIEM platforms, matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly states both the 'what' (analyzes DNS logs to detect exfiltration via tunneling/DGA/C2 using named techniques) and the 'when' ('Use when SOC teams need to identify DNS-based threats that bypass traditional network security controls').	5 / 5
Trigger Term Quality	Includes natural terms a SOC analyst would say — 'DNS query logs', 'data exfiltration', 'DNS tunneling', 'DGA', 'C2 channels', 'SOC teams', 'DNS-based threats' — covering synonyms and the domain vocabulary users actually invoke.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (security-relevant DNS abuse detection) with distinct triggers and an explicit boundary against general DNS troubleshooting, minimizing overlap with adjacent skills.	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-dns-logs-for-exfiltration/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.