CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

building-threat-intelligence-platform

Design and deploy a Threat Intelligence Platform (TIP) by integrating open-source CTI tools (MISP, OpenCTI, TheHive, Cortex) into a unified system with feed ingestion pipelines, enrichment workflows, STIX/TAXII interoperability, and analyst dashboards. Use when architecting or standing up a centralized CTI platform to collect, analyze, and disseminate threat intelligence across a security team.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/building-threat-intelligence-platform/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 delivers a clearly sequenced, code-first workflow with a validation checklist, but it is not reliably copy-paste executable (host port conflicts in the compose file, questionable pymisp method names), and it ignores its own bundle — neither the reference files, scripts, nor template are ever linked, while equivalent code is inlined instead. Conciseness is decent but hampered by an Overview that duplicates the description and pinned versions that will age.

Suggestions

Fix the Docker Compose host port collisions (minio and thehive both publish 9000; the minio console and cortex both publish 9001) so Step 1 deploys as written, and verify the PyMISP calls (enable_feed, fetch_feed, get_server_statistics) against the current PyMISP API, replacing them with documented methods.

Link the bundle from the body: add pointers to references/api-reference.md (STIX/TAXII details), references/standards.md, references/workflows.md, and assets/template.md, and replace the inline Steps 2-4 Python — which duplicates scripts/process.py — with brief usage notes pointing at that script.

Trim the Overview (it restates the frontmatter description) and the generic 'When to Use' bullets, and collect the pinned image versions into a labeled version-compatibility note so the time-sensitive pins don't age the rest of the content.

DimensionReasoningScore

Conciseness

The body is mostly efficient code with little concept-explanation padding, but it can be tightened: the Overview paragraph restates the frontmatter description, the 'When to Use' bullets are generic boilerplate ('When establishing security controls aligned to compliance requirements'), and multiple pinned version numbers ('elasticsearch:8.12.0', 'opencti/platform:6.4.4', 'strangebee/thehive:5.3', 'thehiveproject/cortex:3.1.8') are time-sensitive and not placed in a versions/deprecation section, which the guidelines say should penalize conciseness. This lands on anchor 3 ('mostly efficient but... could be tightened') rather than anchor 4.

3 / 5

Actionability

The guidance is concrete and complete in form (full Docker Compose file, runnable-looking Python classes, real Cortex REST paths like '/api/analyzer/{id}/run'), but key details are wrong or unverified: the compose file binds host port 9000 to both minio and thehive, and 9001 to both the minio console and cortex, so 'docker compose up' fails as written; and pymisp calls like 'self.misp.enable_feed(...)', 'self.misp.fetch_feed(...)', and 'self.misp.get_server_statistics()' do not match documented PyMISP methods. Not being copy-paste executable puts this at anchor 3 ('missing key details') rather than anchor 4 ('minor gaps').

3 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced (deploy → feeds → enrichment → dashboards), there is a final 'Validation Criteria' checklist ('All platform components... deployed and accessible', 'MISP-OpenCTI bidirectional sync operational', 'At least 3 OSINT feeds ingesting'), and Step 2 includes an inline connector-status check with per-feed error handling. It falls short of anchor 5 because there are no explicit post-step verification checkpoints or error-recovery feedback loops (e.g., what to do when a validation criterion fails), matching anchor 4 ('clear sequence with most checkpoints present; minor validation gaps').

4 / 5

Progressive Disclosure

The body is well-sectioned but scored against the actual bundle: the 'References' section lists only external URLs and never mentions the bundled references/api-reference.md, references/standards.md, references/workflows.md, scripts/agent.py, scripts/process.py, or assets/template.md, so those files are undiscoverable. Additionally, Steps 2-4 inline ~150 lines of Python that overlap in function with the bundled scripts/process.py — content that arguably belongs in the separate files. This matches anchor 3 ('references present but not clearly signaled; content that should be separate is inline'); it is above anchor 2 because the section structure itself is good and nothing is deeply nested.

3 / 5

Total

13

/

20

Passed

Description

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

An exemplary description: it states concrete capabilities with named tools, includes full synonym coverage of natural trigger terms, and explicitly answers both what the skill does and when to use it. The only minor weakness is slight breadth in the closing 'collect, analyze, and disseminate' phrasing that could overlap with adjacent CTI skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Design and deploy', 'integrating open-source CTI tools (MISP, OpenCTI, TheHive, Cortex)', 'feed ingestion pipelines, enrichment workflows, STIX/TAXII interoperability, and analyst dashboards' — giving comprehensive coverage of the skill's capabilities. It fits anchor 5 ('multiple specific concrete actions; comprehensive coverage') better than anchor 4, since no meaningful capability area of TIP building is omitted.

5 / 5

Completeness

It explicitly answers both questions: the 'what' ('Design and deploy a Threat Intelligence Platform... with feed ingestion pipelines, enrichment workflows, STIX/TAXII interoperability, and analyst dashboards') and the 'when' ('Use when architecting or standing up a centralized CTI platform to collect, analyze, and disseminate threat intelligence across a security team'). An explicit 'Use when...' clause with concrete trigger phrases is exactly anchor 5.

5 / 5

Trigger Term Quality

Natural trigger terms are comprehensively covered with synonyms: 'Threat Intelligence Platform (TIP)', 'CTI', 'threat intelligence', plus the specific tool names users would actually say ('MISP', 'OpenCTI', 'TheHive', 'Cortex', 'STIX/TAXII') and natural trigger verbs ('architecting or standing up a centralized CTI platform'). This matches anchor 5's comprehensive synonym coverage; secondary terms like 'IOC' or 'OSINT' being absent is not enough to drop to anchor 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

The named-tool integration and platform-building framing creates a clear niche with distinct triggers, but the closing phrase 'collect, analyze, and disseminate threat intelligence' leaves minor overlap risk with closely related skills (e.g., a MISP-administration or general TI-analysis skill). Anchor 4 ('mostly distinct; minor overlap risk with closely related skills') is the best fit; anchor 5 would require tighter scoping that rules out those neighbors.

4 / 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/building-threat-intelligence-platform/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.