CtrlK
BlogDocsLog inGet started
Tessl Logo

automating-ioc-enrichment

Automates the enrichment of raw indicators of compromise with multi-source threat intelligence context using SOAR platforms, Python pipelines, or TIP playbooks to reduce analyst triage time and standardize enrichment outputs. Use when building automated enrichment workflows integrated with SIEM alerts, email submission pipelines, or bulk IOC processing from threat feeds. Activates for requests involving SOAR enrichment, Cortex XSOAR, Splunk SOAR, TheHive, Python enrichment pipelines, or automated IOC processing.

82

Quality

78%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/automating-ioc-enrichment/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

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

This is a strong, well-crafted skill description that clearly defines its niche in automated IOC enrichment using SOAR platforms. It excels across all dimensions with specific actions, comprehensive trigger terms including named tools, explicit 'Use when' and 'Activates for' clauses, and a highly distinctive domain focus. The description is thorough without being unnecessarily verbose.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: enrichment of raw IOCs, multi-source threat intelligence context, SOAR platforms, Python pipelines, TIP playbooks, reducing analyst triage time, and standardizing enrichment outputs. Names specific tools like Cortex XSOAR, Splunk SOAR, TheHive.

3 / 3

Completeness

Clearly answers both 'what' (automates enrichment of raw IOCs with multi-source threat intelligence) and 'when' (explicit 'Use when' clause covering SIEM alerts, email submission pipelines, bulk IOC processing, plus an 'Activates for' clause listing specific tool names and scenarios).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms a security analyst would use: 'SOAR enrichment', 'Cortex XSOAR', 'Splunk SOAR', 'TheHive', 'Python enrichment pipelines', 'automated IOC processing', 'SIEM alerts', 'threat feeds', 'bulk IOC processing'. These are highly specific and natural keywords for this domain.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche focused specifically on automated IOC enrichment workflows with named SOAR platforms. Unlikely to conflict with general security skills, coding skills, or other automation skills due to the very specific domain terminology and tool names.

3 / 3

Total

12

/

12

Passed

Implementation

57%

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

The skill provides highly actionable, executable Python code and concrete SOAR playbook steps, which is its strongest quality. However, it suffers from being a monolithic document that includes unnecessary glossary definitions and tool descriptions that Claude already knows, and it lacks explicit validation checkpoints in the workflow despite dealing with pipeline operations where partial failures can silently degrade output quality.

Suggestions

Remove the 'Key Concepts' glossary table and 'Tools & Systems' section — Claude already knows what SOAR, rate limiting, and these platforms are. This saves ~20 lines of tokens.

Add explicit validation checkpoints: e.g., after Step 2, verify API connectivity with a test IOC; after Step 3, validate playbook output against a known-malicious IOC to confirm scoring logic works correctly.

Split the Python enrichment functions and rate-limiting code into a referenced file (e.g., `ENRICHMENT_FUNCTIONS.md` or `enrichment_pipeline.py`) and keep SKILL.md as a concise overview with navigation links.

Add a caching implementation example since it's called out as a common pitfall but no concrete code or configuration is provided for it.

DimensionReasoningScore

Conciseness

The skill includes a glossary table defining terms like 'SOAR' and 'Rate Limiting' that Claude already knows, and the 'Tools & Systems' section describes well-known platforms unnecessarily. The code examples and workflow steps are reasonably efficient, but the overall content could be tightened by removing explanatory padding.

2 / 3

Actionability

The skill provides fully executable Python code for IP and hash enrichment, a concrete rate-limiting decorator, retry logic, specific API endpoints and headers, and step-by-step SOAR playbook instructions with named commands (e.g., `!vt-file-scan`). The guidance is copy-paste ready and includes specific thresholds and routing logic.

3 / 3

Workflow Clarity

The 5-step workflow is clearly sequenced and includes rate limiting/failure handling in Step 4. However, there are no explicit validation checkpoints — no step verifies that enrichment results are correct or complete before proceeding, no feedback loop for validating the pipeline output, and no verification that API keys are valid or that the pipeline is functioning correctly before processing production alerts.

2 / 3

Progressive Disclosure

The skill is a monolithic wall of content (~150+ lines) with no references to external files. The Python enrichment functions, SOAR playbook details, rate limiting code, metrics guidance, glossary, and tools list are all inline. The code examples and reference tables could be split into separate files with clear navigation links.

1 / 3

Total

8

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
mukul975/Anthropic-Cybersecurity-Skills
Reviewed

Table of Contents

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.