CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

building-attack-pattern-library-from-cti-reports

Parse cyber threat intelligence reports (Mandiant, CrowdStrike, Talos, Microsoft) with stix2, mitreattack-python, and spaCy to extract adversary behaviors, map them to MITRE ATT&CK technique IDs, and build a searchable STIX 2.1 attack-pattern library with detection templates. Use when cataloging attack patterns from CTI reports for threat-informed detection engineering, or generating Sigma/YARA templates from documented behaviors.

Quality

79%

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-attack-pattern-library-from-cti-reports/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 delivers an executable three-step pipeline with concrete code, but pads it with background explanation and boilerplate 'When to Use' text, omits validation checkpoints in a batch workflow, and fails to link to the provided api-reference.md and agent.py bundle files.

Suggestions

Tighten the Overview and Key Concepts sections — drop explanations of what STIX/ATT&CK are and keep only the extraction-to-library specifics Claude would not already know.

Add an explicit validation/feedback checkpoint in the workflow (e.g., verify mapped technique IDs resolve against the ATT&CK STIX data before building the library) so the batch process can recover from mapping failures.

Link the provided bundle files from the body — reference scripts/agent.py for the full runnable implementation and references/api-reference.md for the technique/IOC regex tables — instead of inlining overlapping code.

DimensionReasoningScore

Conciseness

The Overview restates the description and the Key Concepts sections explain background Claude largely already knows ('STIX defines Attack Pattern as an SDO...'), while the 'When to Use' bullets are generic boilerplate; the code is justified but the prose around it could be trimmed.

3 / 5

Actionability

Three substantial, mostly copy-paste-ready Python classes (CTIReportParser, ATTACKMapper, AttackPatternLibrary) cover the common pipeline end-to-end, with only minor gaps such as the prerequisites listing 'mitreattack-python' while the code imports 'attackcti'.

4 / 5

Workflow Clarity

Steps are clearly sequenced (Parse → Map → Create library) but there are no in-process validation checkpoints or feedback loops for this batch report-processing operation; the Validation Criteria section lists end-state outcomes rather than recoverable checks, capping the score at 3 per the batch-operation guideline.

3 / 5

Progressive Disclosure

Section structure is reasonable and external references are linked, but the bundle files references/api-reference.md and scripts/agent.py are never referenced from the body, and long inline code that overlaps with agent.py arguably belongs in the script — content that should be separate is inlined and internal references are not signaled.

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.

A well-crafted, third-person description that pairs concrete capabilities with an explicit Use-when trigger clause and domain-specific keywords. Its only minor gap is a few additional natural synonyms a user might phrase.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Parse cyber threat intelligence reports', 'extract adversary behaviors', 'map them to MITRE ATT&CK technique IDs', 'build a searchable STIX 2.1 attack-pattern library', 'generate ... Sigma/YARA templates' — with named tools, giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what (parse/extract/map/build/generate) and when via a concrete 'Use when cataloging attack patterns from CTI reports ... or generating Sigma/YARA templates' trigger clause.

5 / 5

Trigger Term Quality

Strong natural keywords a CTI analyst would say — 'CTI reports', 'threat-informed detection engineering', 'Sigma/YARA templates', 'MITRE ATT&CK technique IDs' — but missing a few common variations/synonyms such as 'threat intel', 'IOCs', or file-format triggers.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (CTI attack-pattern extraction → STIX/ATT&CK library → Sigma/YARA templates) with distinct triggers and minimal overlap risk with adjacent skills.

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/building-attack-pattern-library-from-cti-reports/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.