Back to catalog
Static reviewDevelopment

Skill dossier

managing-intelligence-lifecycle

Source declaration

Manages the end-to-end cyber threat intelligence lifecycle from planning and direction through collection, processing, analysis, dissemination, and feedback to ensure intelligence products meet stakeholder requirements and continuously improve. Use when establishing or maturing a CTI program, defining intelligence requirements with business stakeholders, or building feedback loops between intelligence consumers and producers. Activates for requests involving CTI program maturity, intelligence requirements, PIRs, or intelligence lifecycle management.

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

Manages the end-to-end cyber threat intelligence lifecycle from planning and direction through collection, processing, analysis, dissemination, and feedback to ensure intelligence products meet stakeholder requirements and continuously improve. Use when establishing or maturing a CTI program, defining intelligence requirements with business stakeholders, or building feedback loops between intelligence consumers and producers. Activates for requests involving CTI program maturity, intelligence requirements, PIRs, or intelligence lifecycle management.

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.

Manages the end-to-end cyber threat intelligence lifecycle from planning and direction through collection, processing, analysis, dissemination, and feedback to ensure intelligence products meet stakeholder requirements and continuously improve. Use when establishing or maturing a CTI program, defining intelligence requirements with business stakeholders, or building feedback loops between intelligence consumers and producers. Activates for requests involving CTI program maturity, intelligence requirements, PIRs, or intelligence lifecycle management. 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/managing-intelligence-lifecycle/SKILL.md:L53]
  • Step 1: Planning and Direction [Source statement; provisional, not tested. Evidence: skills/managing-intelligence-lifecycle/SKILL.md:L55]
  • Step 2: Collection Planning [Source statement; provisional, not tested. Evidence: skills/managing-intelligence-lifecycle/SKILL.md:L64]
  • Step 3: Processing and Normalization [Source statement; provisional, not tested. Evidence: skills/managing-intelligence-lifecycle/SKILL.md:L73]
  • Step 4: Analysis and Production [Source statement; provisional, not tested. Evidence: skills/managing-intelligence-lifecycle/SKILL.md:L80]
  • Step 5: Dissemination [Source statement; provisional, not tested. Evidence: skills/managing-intelligence-lifecycle/SKILL.md:L89]
  • Step 6: Feedback and Evaluation [Source statement; provisional, not tested. Evidence: skills/managing-intelligence-lifecycle/SKILL.md:L99]

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/managing-intelligence-lifecycle/SKILL.md:L1-L34]

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
26.9 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/managing-intelligence-lifecycle/LICENSEOther11 KB
skills/managing-intelligence-lifecycle/references/api-reference.mdReference2 KB
skills/managing-intelligence-lifecycle/scripts/agent.pyScript7.7 KB
skills/managing-intelligence-lifecycle/SKILL.mdInstruction6.2 KB

SKILL.md frontmatter

{
  "name": "managing-intelligence-lifecycle",
  "description": "Manages the end-to-end cyber threat intelligence lifecycle from planning and direction through collection, processing, analysis, dissemination, and feedback to ensure intelligence products meet stakeholder requirements and continuously improve. Use when establishing or maturing a CTI program, defining intelligence requirements with business stakeholders, or building feedback loops between intelligence consumers and producers. Activates for requests involving CTI program maturity, intelligence requirements, PIRs, or intelligence lifecycle management.\n",
  "domain": "cybersecurity",
  "subdomain": "threat-intelligence",
  "tags": [
    "CTI",
    "intelligence-lifecycle",
    "PIR",
    "NIST-SP-800-150",
    "threat-intelligence-program",
    "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
    Action

    Step 1: Planning and Direction

    Source-described action candidate under “Step 1: Planning and Direction”; not verified execution.

  4. 04
    Action

    Interview SOC leads, IR team, CISO, risk management, and product security

    Source-described action candidate under “Step 1: Planning and Direction”; not verified execution.

  5. 05
    Action

    Document PIRs in structured format: "What is the current capability and intent of [threat actor] to attack [critical asset] using [technique]?"

    Source-described action candidate under “Step 1: Planning and Direction”; not verified execution.

  6. 06
    Action

    Prioritize 5–10 PIRs for the quarter, reviewed monthly

    Source-described action candidate under “Step 1: Planning and Direction”; not verified execution.

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

    Step 2: Collection Planning

    Source-described action candidate under “Step 2: Collection Planning”; not verified execution.

  2. 08
    Action

    Technical sources: commercial feeds, TAXII, ISAC data, honeypot telemetry, darkweb monitoring

    Source-described action candidate under “Step 2: Collection Planning”; not verified execution.

  3. 09
    Action

    Human sources: vendor threat briefings, industry working groups, law enforcement partnerships

    Source-described action candidate under “Step 2: Collection Planning”; not verified execution.

  4. 10
    Action

    Internal sources: SIEM logs, EDR telemetry, phishing submission mailbox

    Source-described action candidate under “Step 2: Collection Planning”; not verified execution.

  5. 11
    Action

    Step 3: Processing and Normalization

    Source-described action candidate under “Step 3: Processing and Normalization”; not verified execution.

  6. 12
    Action

    Ingest → normalize to STIX 2.1 → deduplicate → enrich → score confidence

    Source-described action candidate under “Step 3: Processing and Normalization”; not verified execution.

  7. 13
    Action

    Reject unverifiable or duplicate indicators before analysis

    Source-described action candidate under “Step 3: Processing and Normalization”; not verified execution.

  8. 14
    Input

    Tag all processed data with source, collection date, and expiration

    Source-described input candidate under “Step 3: Processing and Normalization”; not verified execution.

  9. 15
    Action

    Step 4: Analysis and Production

    Source-described action candidate under “Step 4: Analysis and Production”; not verified execution.

  10. 16
    Output

    Strategic: Quarterly threat landscape report for executives; sector trends, geopolitical context

    Source-described output candidate under “Step 4: Analysis and Production”; not verified execution.

  11. 17
    Action

    Operational: Weekly campaign reports for security leadership; active campaigns, adversary activity

    Source-described action candidate under “Step 4: Analysis and Production”; not verified execution.

  12. 18
    Action

    Tactical: Daily IOC bulletins for SOC; actionable indicators with block/monitor recommendations

    Source-described action candidate under “Step 4: Analysis and Production”; not verified execution.

  13. 19
    Action

    Apply structured analytic techniques: Analysis of Competing Hypotheses (ACH), Key Assumptions Check, Devil's Advocacy.

    Source-described action candidate under “Step 4: Analysis and Production”; not verified execution.

  14. 20
    Action

    Step 5: Dissemination

    Source-described action candidate under “Step 5: Dissemination”; not verified execution.

  15. 21
    Action

    Executives: 1-page PDF with risk ratings, business impact, recommended decisions

    Source-described action candidate under “Step 5: Dissemination”; not verified execution.

  16. 22
    Action

    SOC analysts: SIEM-ready IOC list, Sigma rules, MISP events

    Source-described action candidate under “Step 5: Dissemination”; not verified execution.

  17. 23
    Action

    Vulnerability management: CVE lists with EPSS scores and exploitation likelihood

    Source-described action candidate under “Step 5: Dissemination”; not verified execution.

  18. 24
    Output

    IT/Security leadership: Full intelligence report with technical appendix

    Source-described output candidate under “Step 5: Dissemination”; not verified execution.

  19. 25
    Action

    Apply TLP classifications and distribution lists per product type.

    Source-described action candidate under “Step 5: Dissemination”; not verified execution.

  20. 26
    Action

    Step 6: Feedback and Evaluation

    Source-described action candidate under “Step 6: Feedback and Evaluation”; not verified execution.

  21. 27
    Action

    Did the product address the PIR?

    Source-described action candidate under “Step 6: Feedback and Evaluation”; not verified execution.

  22. 28
    Action

    Was actionability sufficient?

    Source-described action candidate under “Step 6: Feedback and Evaluation”; not verified execution.

  23. 29
    Action

    What data was missing?

    Source-described action candidate under “Step 6: Feedback and Evaluation”; not verified execution.

  24. 30
    Action

    Key Concepts

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

  25. 31
    Action

    Tools & Systems

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

  26. 32
    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

22 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

6 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 6 location(s) in the collected text; 3 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/managing-intelligence-lifecycle/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/managing-intelligence-lifecycle/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/managing-intelligence-lifecycle
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.