cti-orchestrator

Classify CTI requests and route them to downstream skills.

15|5|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Liberty91LTD/cti-skills --skill cti-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cti-orchestrator
Source: https://github.com/Liberty91LTD/cti-skills/tree/main/skills/cti-orchestrator
Command: npx skills add https://github.com/Liberty91LTD/cti-skills --skill cti-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The orchestrator provides a single entry point for CTI requests that do not specify a target skill, classifies the request, delegates to downstream skills, and automatically applies rigor to the results to produce a source-rated, confidence-marked product. It does NOT query external APIs directly and is designed to compose other skills to perform the work.

Core Features & Use Cases

  • Route ambiguous CTI requests to the right investigation or analysis skill (e.g., IOC, actor, campaign, malware, or threat assessment).
  • Auto-apply rigor steps (source assessment, TLP, confidence, and likelihood) across outputs without user prompts.
  • Coordinate multi-skill chains and ensure produced intelligence is prepared for writing or sharing.

Quick Start

Route an unknown CTI request to the orchestrator and observe it handing off to the appropriate downstream skill.

Frequently Asked Questions about cti-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route ambiguous cyber threat intelligence requests to the right analysis skill?

CTI routing solves this by classifying ambiguous cyber threat intelligence requests and automatically delegating them to the correct downstream investigation skill for IOCs, actors, or campaigns.

What is automated rigor in threat intelligence workflows?

Automated rigor in threat intelligence workflows applies source assessment, TLP, confidence, and likelihood markings to outputs automatically, ensuring produced intelligence is prepared for writing or sharing without user prompts.

Can I use the orchestrator to query external threat intelligence APIs directly?

No, the orchestrator does not query external APIs directly. It composes and coordinates other downstream skills to perform the work, acting as a single entry point for CTI requests.

How do I coordinate multi-skill chains for threat investigations?

You coordinate multi-skill chains for threat investigations by routing an unknown CTI request to the orchestrator, which executes internal routing logic and invokes the necessary downstream lookup and production skills automatically.

Do I need to manually specify a target skill for IOC and actor investigations?

No, you do not need to manually specify a target skill. The orchestrator acts as a single entry point for CTI requests that do not specify a target, classifying and delegating the request automatically.