CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

collecting-threat-intelligence-with-misp

Deploy MISP, configure threat feeds (MISP community, freetext, TAXII, CSV), and use the PyMISP API to programmatically fetch, add, and search events and IOCs, building automated collection pipelines that aggregate indicators from community and commercial sources. Use when gathering, storing, or correlating IOCs and threat intelligence, or when scripting MISP ingestion via PyMISP.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 — every workflow step has executable code and there is a thorough validation checklist — but it is held back by background padding (Overview, Key Concepts, boilerplate When-to-Use bullets) and by a broken progressive-disclosure design: six bundle files exist yet none are referenced, while API content that duplicates references/api-reference.md is inlined directly.

Suggestions

Replace the inlined PyMISP initialization/search snippets with pointers to the existing bundle files (e.g., "**API reference**: See [references/api-reference.md](references/api-reference.md)", "**Feed workflows**: See [references/workflows.md](references/workflows.md)", "**Report template**: See [assets/template.md](assets/template.md)") so the six bundle files become discoverable and the body stops duplicating them.

Trim the Overview and Key Concepts sections to a few lines each — Claude already knows what MISP, PyMISP, STIX, and TAXII are — and delete the two generic When-to-Use bullets ("improving security program maturity", "establishing standardized procedures") that apply to any security skill.

Embed validation as inline checkpoints after each workflow step (e.g., after Step 1: "verify https://misp.local is reachable and login works"; after Step 2: "confirm feed cache grows and events appear") with a fix-and-retry loop, instead of only listing them in the trailing Validation Criteria section.

DimensionReasoningScore

Conciseness

The workflow steps are dense and code-forward, but there is unnecessary background Claude already knows: the Overview paragraph restates the description nearly verbatim, "PyMISP is the official Python library to access MISP platforms via their REST API" explains a library any model can look up, the Key Concepts section spends ~15 lines on MISP's event/galaxy model, and two "When to Use" bullets ("When improving security program maturity and operational processes", "When establishing standardized procedures for security team workflows") are generic filler. This matches the anchor "mostly efficient but includes some unnecessary explanation or could be tightened" — it is not a 2 because the padding is localized rather than pervasive, and not a 4 because the Overview/Key Concepts/boilerplate bullets clearly could be trimmed.

3 / 5

Actionability

Every step ships copy-paste-ready, executable material: the docker compose deployment commands, the feed listing/enabling/caching calls, a complete feed-registration dict, a parameterized event search with date/type/to_ids filters, and three export variants (STIX 2.1, Suricata, CSV). Placeholders (YOUR_API_KEY, misp.local) are expected configuration points, not pseudocode. This matches the top anchor — fully executable with specific examples covering the common cases.

5 / 5

Workflow Clarity

The five steps form a coherent sequence (deploy → enable feeds → add feeds → search/retrieve → export) and a dedicated Validation Criteria section provides six concrete checks (HTTPS accessibility, 3+ feeds fetching, auth/search works, tagged attributes, valid STIX bundles, scheduled fetches). It does not reach 5 because validation lives in a trailing checklist rather than inline checkpoints, and there are no error-recovery feedback loops (e.g., what to do when a feed fetch or auth check fails), which matters for batch feed operations. It is above 3 because most checkpoints are present and only their placement/feedback loop is missing.

4 / 5

Progressive Disclosure

Scored against the actual bundle structure: the skill ships references/api-reference.md, references/standards.md, references/workflows.md, scripts/agent.py, scripts/process.py, and assets/template.md, yet the body never links to any of them — the References section lists only external URLs. Meanwhile PyMISP client initialization and event-search code is inlined in the body even though references/api-reference.md contains that same material, i.e., "content that clearly belongs in separate files is inlined" plus fully orphaned bundle files with no navigation path. This matches the 2 anchor; it is not a 3 because that anchor requires references to be present (even if unclearly signaled), whereas here the bundle references are entirely absent from the body.

2 / 5

Total

14

/

20

Passed

Description

88%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 description: specific, third-person, with an explicit "Use when..." trigger clause and concrete capability enumeration. Its only weaknesses are a slightly broad trigger clause that could overlap with adjacent CTI skills and a few missing natural synonyms (indicators of compromise, threat intel, STIX).

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Deploy MISP", "configure threat feeds (MISP community, freetext, TAXII, CSV)", "programmatically fetch, add, and search events and IOCs", "building automated collection pipelines" — with comprehensive coverage of the skill's capabilities. This matches the anchor for multiple specific concrete actions; it is not the level below (4) because there are no significant gaps in coverage of the deployment, configuration, and API-automation tasks the body actually performs.

5 / 5

Completeness

It explicitly answers both questions: the "what" (deploy MISP, configure feeds, use PyMISP to fetch/add/search events and IOCs, build pipelines) and the "when" ("Use when gathering, storing, or correlating IOCs and threat intelligence, or when scripting MISP ingestion via PyMISP") with concrete trigger phrases. This is a direct match to the top anchor; the 4 anchor would require the "when" clause to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Strong natural keywords are present: "MISP", "PyMISP", "IOCs", "threat intelligence", "TAXII", "threat feeds", "ingestion", "correlating" — terms a user would naturally say. It falls short of the 5 anchor because a few natural synonyms are missing (e.g., "indicators of compromise" spelled out, "threat intel", "STIX", "indicator sharing"), which the top anchor requires; it is above the 3 anchor because keyword coverage goes well beyond "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (MISP/PyMISP threat-intelligence collection) with distinct triggers like "MISP", "PyMISP", and "TAXII", so it is above the 3 anchor ("could still overlap with similar skills"). It does not reach 5 because the broad when-clause "gathering, storing, or correlating IOCs and threat intelligence" is not MISP-qualified and could fire for general CTI requests served by other skills (e.g., a generic STIX/TAXII or threat-intel-platform skill) — minor overlap risk with closely related skills.

4 / 5

Total

18

/

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-threat-intelligence-with-misp/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.