CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

collecting-indicators-of-compromise

Systematically collects, categorizes, and distributes indicators of compromise (IOCs) during and after security incidents to enable detection, blocking, and threat intelligence sharing. Covers network, host, email, and behavioral indicators using STIX/TAXII formats and threat intelligence platforms. Activates for requests involving IOC collection, indicator extraction, threat indicator sharing, compromise indicators, STIX export, or IOC enrichment.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/collecting-indicators-of-compromise/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 a well-organized, example-rich IR workflow with mostly executable guidance, but it is dragged down by a Key Concepts/Tools section teaching things Claude already knows, the absence of any validation checkpoint before batch blocking and external sharing, and total failure to reference the bundle's own api-reference.md and scripts/agent.py.

Suggestions

Add validation checkpoints to the workflow: before Step 5, screen IOCs against internal/CDN/cloud-provider ranges (e.g., a brief allowlist check) and require TLP marking and defanging review before Step 6 sharing — this lifts the batch/destructive cap on workflow_clarity.

Replace the "Key Concepts" and "Tools & Systems" tables with one-line pointers to references/api-reference.md, and add an explicit "Automation" line (e.g., "For automated extraction/enrichment/STIX export, run scripts/agent.py — see references/api-reference.md") so the existing bundle files are discoverable.

Trim the trigger-adjacent over-claim by aligning the description's "behavioral indicators" with the body's caveat, and drop definitions of STIX/TAXII/TLP/defanging that Claude already knows, keeping only the skill-specific confidence-scoring rubric and output format.

DimensionReasoningScore

Conciseness

The workflow steps are dense and example-driven, but the "Key Concepts" table defines IOC, STIX, TAXII, TLP, defanging, and the "Tools & Systems" section describes MISP, VirusTotal, and OpenCTI — concepts and tools Claude already knows. This matches the anchor for mostly efficient content that includes some unnecessary explanation that could be trimmed; it is above level 2 because the padding is confined to two tables rather than pervading the skill.

3 / 5

Actionability

Concrete, executable material abounds: Splunk SPL queries ("index=firewall action=blocked | stats count by dest_ip"), volatility commands ("vol -f memory.raw windows.netscan"), a valid STIX 2.1 JSON object, a confidence-scoring table, and a full output template. It falls short of level 5 because the final distribution/sharing steps ("Submit to MISP, ISAC portals, and TAXII servers per sharing agreements") give no concrete commands, and the sandbox-report block is illustrative output rather than an executable procedure.

4 / 5

Workflow Clarity

The six-step sequence (identify categories → extract → enrich → score → distribute → share) is clearly ordered with a scoring rubric, but it contains no validation checkpoints: pushing batch blocks to firewall/EDR/DNS and sharing externally are batch/destructive-adjacent operations, and no step verifies IOCs against legitimate infrastructure (CDN/cloud allowlists) or internal assets before distribution — the pitfalls list names these risks but the workflow never gates on them. Per the batch-operation cap, workflow clarity cannot exceed 3 without explicit verification steps.

3 / 5

Progressive Disclosure

Section structure and inline content placement are good (roughly level 4), but the bundle contains references/api-reference.md and scripts/agent.py — an automated IOC extraction/enrichment/STIX tool — and the SKILL.md body never mentions either file or directory. The references exist but are completely un-signaled, so the skill's own automation is undiscoverable; this matches the anchor for references present but not clearly signaled rather than the level-4 anchor of minor organization gaps.

3 / 5

Total

13

/

20

Passed

Description

92%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.

Strong description: explicit what-and-when structure, concrete actions, third-person voice, and a dedicated trigger clause with natural analyst phrasing. The only nit is that "Covers... behavioral indicators" slightly overstates scope relative to the body's own caveat against behavioral TTP analysis, and a few natural trigger synonyms are absent.

DimensionReasoningScore

Specificity

"Systematically collects, categorizes, and distributes indicators of compromise (IOCs)" names multiple concrete actions, and "Covers network, host, email, and behavioral indicators using STIX/TAXII formats and threat intelligence platforms" gives comprehensive coverage of scope and formats. This matches the anchor for multiple specific concrete actions; it is not the level-4 anchor because there are no meaningful gaps in action coverage, and it stays in third person throughout.

5 / 5

Completeness

The description explicitly answers "what" ("collects, categorizes, and distributes... to enable detection, blocking, and threat intelligence sharing") and "when" with a dedicated trigger clause ("Activates for requests involving IOC collection, indicator extraction..."). This directly matches the anchor for clearly and explicitly answering both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

"IOC collection, indicator extraction, threat indicator sharing, compromise indicators, STIX export, or IOC enrichment" are natural phrases an analyst would actually say, with good synonym coverage (IOC / indicators / compromise indicators). It falls just short of the level-5 anchor: a few common natural phrasings (e.g., "threat intel", "share IOCs", "C2 indicators") are missing, and there is no analogue to file-extension triggers, so it sits noticeably above the midpoint but not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

IOC collection during incident response is a clear niche with distinct triggers ("STIX export", "IOC enrichment", "compromise indicators") that no adjacent skill (malware analysis, IR playbooks, SIEM engineering) would naturally claim. The trigger terms are specific enough that conflict risk is minimal, matching the level-5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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/collecting-indicators-of-compromise/SKILL.md

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.