Back to catalog
Static reviewDevelopment

Skill dossier

generating-threat-intelligence-reports

Source declaration

Generates structured cyber threat intelligence reports at strategic, operational, and tactical levels tailored to specific audiences including executives, security operations teams, and technical analysts. Use when producing finished intelligence products from raw collection data, creating sector threat briefings, or delivering post-incident intelligence assessments. Activates for requests involving CTI report writing, threat briefings, intelligence products, finished intelligence, or executive security reporting.

The author's original description, preserved in English. It describes intent, not verified performance.

Generates structured cyber threat intelligence reports at strategic, operational, and tactical levels tailored to specific audiences including executives, security operations teams, and technical analysts. Use when producing finished intelligence products from raw collection data, creating sector threat briefings, or delivering post-incident intelligence assessments. Activates for requests involving CTI report writing, threat briefings, intelligence products, finished intelligence, or executive security reporting.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Generates structured cyber threat intelligence reports at strategic, operational, and tactical levels tailored to specific audiences including executives, security operations teams, and technical analysts. Use when producing finished intelligence products from raw collection data, creating sector threat briefings, or delivering post-incident intelligence assessments. Activates for requests involving CTI report writing, threat briefings, intelligence products, finished intelligence, or executive security reporting. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/generating-threat-intelligence-reports/SKILL.md:L54]
  • Step 1: Determine Report Type and Audience [Source statement; provisional, not tested. Evidence: skills/generating-threat-intelligence-reports/SKILL.md:L56]
  • Step 2: Structure Report Using Intelligence Standards [Source statement; provisional, not tested. Evidence: skills/generating-threat-intelligence-reports/SKILL.md:L80]
  • Step 3: Write Report Body [Source statement; provisional, not tested. Evidence: skills/generating-threat-intelligence-reports/SKILL.md:L95]
  • Step 4: Apply TLP and Distribution Controls [Source statement; provisional, not tested. Evidence: skills/generating-threat-intelligence-reports/SKILL.md:L111]
  • Step 5: Review and Quality Control [Source statement; provisional, not tested. Evidence: skills/generating-threat-intelligence-reports/SKILL.md:L122]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/generating-threat-intelligence-reports/SKILL.md:L1-L35]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
30 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/generating-threat-intelligence-reports/LICENSEOther11 KB
skills/generating-threat-intelligence-reports/references/api-reference.mdReference2.8 KB
skills/generating-threat-intelligence-reports/scripts/agent.pyScript8.7 KB
skills/generating-threat-intelligence-reports/SKILL.mdInstruction7.6 KB

SKILL.md frontmatter

{
  "name": "generating-threat-intelligence-reports",
  "description": "Generates structured cyber threat intelligence reports at strategic, operational, and tactical levels tailored to specific audiences including executives, security operations teams, and technical analysts. Use when producing finished intelligence products from raw collection data, creating sector threat briefings, or delivering post-incident intelligence assessments. Activates for requests involving CTI report writing, threat briefings, intelligence products, finished intelligence, or executive security reporting.\n",
  "domain": "cybersecurity",
  "subdomain": "threat-intelligence",
  "tags": [
    "CTI",
    "threat-intelligence",
    "intelligence-products",
    "TLP",
    "PIR",
    "report-writing",
    "NIST-CSF"
  ],
  "version": "1.0.0",
  "author": "team-cybersecurity",
  "license": "Apache-2.0",
  "nist_csf": [
    "ID.RA-01",
    "ID.RA-05",
    "DE.CM-01",
    "DE.AE-02"
  ],
  "mitre_attack": [
    "T1591",
    "T1592",
    "T1593",
    "T1589"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Output

    Step 1: Determine Report Type and Audience

    Source-described output candidate under “Step 1: Determine Report Type and Audience”; not verified execution.

  4. 04
    Action

    Select the appropriate intelligence product type:

    Source-described action candidate under “Step 1: Determine Report Type and Audience”; not verified execution.

  5. 05
    Action

    Content: Threat landscape trends, adversary intent vs. capability, risk to business objectives

    Source-described action candidate under “Step 1: Determine Report Type and Audience”; not verified execution.

  6. 06
    Action

    Format: 1–3 pages, minimal jargon, business impact language, recommended decisions

    Source-described action candidate under “Step 1: Determine Report Type and Audience”; not verified execution.

Inspect all extracted workflow candidates (41 candidate steps)
  1. 07
    Action

    Frequency: Monthly/Quarterly

    Source-described action candidate under “Step 1: Determine Report Type and Audience”; not verified execution.

  2. 08
    Action

    Content: Active campaigns, adversary TTPs, defensive recommendations, sector peer incidents

    Source-described action candidate under “Step 1: Determine Report Type and Audience”; not verified execution.

  3. 09
    Action

    Format: 3–8 pages, moderate technical detail, mitigation priority list

    Source-described action candidate under “Step 1: Determine Report Type and Audience”; not verified execution.

  4. 10
    Action

    Frequency: Weekly

    Source-described action candidate under “Step 1: Determine Report Type and Audience”; not verified execution.

  5. 11
    Action

    Content: Specific IOCs, YARA rules, Sigma detections, CVEs, patching guidance

    Source-described action candidate under “Step 1: Determine Report Type and Audience”; not verified execution.

  6. 12
    Action

    Format: Structured tables, code blocks, 1–2 pages

    Source-described action candidate under “Step 1: Determine Report Type and Audience”; not verified execution.

  7. 13
    Action

    Frequency: Daily or as-needed

    Source-described action candidate under “Step 1: Determine Report Type and Audience”; not verified execution.

  8. 14
    Action

    Content: What is happening, immediate risk, what to do right now

    Source-described action candidate under “Step 1: Determine Report Type and Audience”; not verified execution.

  9. 15
    Action

    Format: 1 page maximum, distributed within 2 hours of threat identification

    Source-described action candidate under “Step 1: Determine Report Type and Audience”; not verified execution.

  10. 16
    Action

    Frequency: As-needed (zero-day, active campaign targeting sector)

    Source-described action candidate under “Step 1: Determine Report Type and Audience”; not verified execution.

  11. 17
    Output

    Step 2: Structure Report Using Intelligence Standards

    Source-described output candidate under “Step 2: Structure Report Using Intelligence Standards”; not verified execution.

  12. 18
    Action

    Apply intelligence writing standards from government and professional practice:

    Source-described action candidate under “Step 2: Structure Report Using Intelligence Standards”; not verified execution.

  13. 19
    Output

    Bad: "This report examines threat actor TTPs associated with Cl0p ransomware"

    Source-described output candidate under “Step 2: Structure Report Using Intelligence Standards”; not verified execution.

  14. 20
    Action

    Good: "Cl0p ransomware group is actively exploiting CVE-2024-20353 in Cisco ASA devices to gain initial access; organizations using unpatched ASA appliances face imminent ransomware risk"

    Source-described action candidate under “Step 2: Structure Report Using Intelligence Standards”; not verified execution.

  15. 21
    Action

    High confidence: "assess with high confidence" — strong evidence, few assumptions

    Source-described action candidate under “Step 2: Structure Report Using Intelligence Standards”; not verified execution.

  16. 22
    Action

    Medium confidence: "assess" — credible sources but analytical assumptions required

    Source-described action candidate under “Step 2: Structure Report Using Intelligence Standards”; not verified execution.

  17. 23
    Action

    Low confidence: "suggests" — limited sources, significant uncertainty

    Source-described action candidate under “Step 2: Structure Report Using Intelligence Standards”; not verified execution.

  18. 24
    Output

    Step 3: Write Report Body

    Source-described output candidate under “Step 3: Write Report Body”; not verified execution.

  19. 25
    Action

    Use structured format:

    Source-described action candidate under “Step 3: Write Report Body”; not verified execution.

  20. 26
    Action

    Step 4: Apply TLP and Distribution Controls

    Source-described action candidate under “Step 4: Apply TLP and Distribution Controls”; not verified execution.

  21. 27
    Input

    Select TLP based on source sensitivity and sharing agreements:

    Source-described input candidate under “Step 4: Apply TLP and Distribution Controls”; not verified execution.

  22. 28
    Action

    TLP:RED: Named recipients only; cannot be shared outside briefing room

    Source-described action candidate under “Step 4: Apply TLP and Distribution Controls”; not verified execution.

  23. 29
    Action

    TLP:AMBER+STRICT: Organization only; no sharing with subsidiaries or partners

    Source-described action candidate under “Step 4: Apply TLP and Distribution Controls”; not verified execution.

  24. 30
    Action

    TLP:AMBER: Organization and trusted partners with need-to-know

    Source-described action candidate under “Step 4: Apply TLP and Distribution Controls”; not verified execution.

  25. 31
    Action

    TLP:GREEN: Community-wide sharing (ISAC members, sector peers)

    Source-described action candidate under “Step 4: Apply TLP and Distribution Controls”; not verified execution.

  26. 32
    Action

    TLP:WHITE/CLEAR: Public distribution; no restrictions

    Source-described action candidate under “Step 4: Apply TLP and Distribution Controls”; not verified execution.

  27. 33
    Action

    Step 5: Review and Quality Control

    Source-described action candidate under “Step 5: Review and Quality Control”; not verified execution.

  28. 34
    Action

    Accuracy: Are all facts sourced and cited? No unsubstantiated claims.

    Source-described action candidate under “Step 5: Review and Quality Control”; not verified execution.

  29. 35
    Action

    Clarity: Can the target audience understand this without additional context?

    Source-described action candidate under “Step 5: Review and Quality Control”; not verified execution.

  30. 36
    Output

    Actionability: Does every report section drive a decision or action?

    Source-described output candidate under “Step 5: Review and Quality Control”; not verified execution.

  31. 37
    Input

    Classification: Is TLP correctly applied? No source identification in AMBER/RED products?

    Source-described input candidate under “Step 5: Review and Quality Control”; not verified execution.

  32. 38
    Action

    Timeliness: Is this intelligence still current? Events older than 48 hours require freshness assessment.

    Source-described action candidate under “Step 5: Review and Quality Control”; not verified execution.

  33. 39
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  34. 40
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  35. 41
    Action

    Common Pitfalls

    Source-described action candidate under “Common Pitfalls”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

18 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

2 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

16 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 16 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/generating-threat-intelligence-reports/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/generating-threat-intelligence-reports/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/generating-threat-intelligence-reports
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.