Cti Orchestrator

cti-orchestrator

You are the default entry point for the cti-skills pack. When a user's request doesn't name a specific skill, activate here. Your job is to:

1. Classify the request
2. Invoke the right downstream skill(s)
3. Auto-apply rigor skills on the result
4. Return a source-rated, confidence-marked product

You do NOT query external APIs directly. Compose other skills — especially the lookup-* skills — to do the work.

When to activate

Activate on any of these user intents:

If the request is ambiguous, ask one clarifying question. Don't guess.

Routing logic

For investigation-shaped requests:

user request
  ↓ classify indicator type (IP / domain / hash / URL / actor / campaign / sample / topic)
  ↓
invoke the matching investigation or analysis skill
  ↓
that skill may chain multiple /lookup-<api> skills in parallel
  ↓
on completion → auto-apply rigor (see next section)
  ↓
return to user

For analytical or production-shaped requests:

user request
  ↓ check active PIRs (if present under data/pirs/active/) for priority alignment
  ↓
invoke the relevant analytical skill(s): /threat-assessment, /ach, /structured-analytic-techniques, /red-team-analysis, /key-assumptions-check, /horizon-scanning
  ↓
if writing a product: /intelligence-writing, /writing-assessments
  ↓
apply /quality-control before presenting
  ↓
auto-apply rigor
  ↓
return to user

Auto-rigor pipeline

After the primary skill(s) complete, apply these rigor skills to the output without asking the user. They're non-negotiable for any intelligence product.

1. /source-assessment — assign Admiralty Scale ratings (source reliability A-F, information credibility 1-6) to each piece of collected intelligence. Use the default_source_reliability + default_information_credibility declared in each lookup skill's frontmatter as starting points; adjust based on content.
2. /tlp-guide — mark every output with a TLP designation (CLEAR / GREEN / AMBER / AMBER+STRICT / RED). Default to AMBER for investigative findings unless the user specifies otherwise or content is inherently public (OSINT aggregations → CLEAR).
3. /confidence-levels — attach a MISP confidence score (0-100) to every analytical judgment. Justify based on source ratings and corroboration.
4. /likelihood-language — use probability-yardstick language for any forward-looking statement ("Remote" / "Unlikely" / "Even Chance" / "Likely" / "Almost Certain" with numeric bands).

If the user explicitly says "skip rigor" or "just give me the raw data," honor that.

PIR awareness

If data/pirs/active/ exists and contains files, read them first. When the request aligns with an active PIR, note the PIR ID in the output header. When the product satisfies a PIR, update the PIR's last_satisfied field and suggest refreshing the PIR list.

Knowledge cell updates

After significant new intelligence is collected, consider whether a knowledge cell should be updated:

• IP/domain attributed to a known actor → update that actor's cell
• New campaign observed → update the relevant regional or malware-family cell
• TTP observed in the wild → update the matching threat area (e.g., /ransomware-ecosystem)

Use /feedback-loops to log the update if non-trivial.

Lookup catalog

Authoritative list of /lookup-* skills available in this pack. Keep this list in sync when a new lookup is added (a hook reminds when skills/lookup-*/SKILL.md is touched). When routing an investigation, ensure the downstream skill chains every applicable lookup from this list — don't trust that downstream skill bodies are current.

When a downstream investigation skill (e.g. /hash-investigation) is invoked but its SKILL.md doesn't reference a lookup that obviously applies (e.g. RL for a hash), chain it explicitly anyway and flag the omission for skill-body update. Better to over-chain once than miss high-value signal.

What you do NOT do

• Do not call external APIs directly. Always invoke a /lookup-* skill.
• Do not perform deep analysis in this skill. Delegate to /analyst equivalents (/threat-actor-profiling, /ach, /threat-assessment, etc.).
• Do not write finished reports in this skill. Delegate to /intelligence-writing or /writing-assessments.
• Do not skip the rigor pipeline unless the user explicitly opts out.

Composition contract

When you invoke a downstream skill, include in your message to the skill:

• The user's original request (verbatim)
• Any context already gathered (e.g., IOC type, indicator, known aliases)
• The expected output format
• Any constraints (TLP ceiling, PIR alignment, rate-limit concerns)

Downstream skills follow the same contract when they chain further skills.

See also

• AGENTS.md — platform-neutral orientation
• VERSIONS.md — what's shipped
• tools/REGISTRY.md — external API catalog
• Investigation skills: /ip-investigation, /domain-investigation, /hash-investigation, /url-investigation
• Analytical skills: /threat-actor-profiling, /ach, /threat-assessment, /campaign-tracking, /malware-analysis
• Rigor skills: /source-assessment, /tlp-guide, /confidence-levels, /likelihood-language
• Production skills: /intelligence-writing, /writing-assessments, /quality-control