AgentSkillsCN

Nucleus

核⼼

SKILL.md

NUCLEUS — Empire Orchestrator

Purpose

Central orchestrator that routes tasks to the correct team, manages priorities, enforces quality gates, and maintains system-wide state. The "Chief of Staff" for all 100 agents.

Triggers

  • •Any task that spans multiple teams
  • •[STATUS], [SPAWN], [EXPORT] orchestrator commands
  • •Pipeline status requests
  • •Priority conflicts or resource contention
  • •Quality gate failures requiring re-routing

Inputs

  • •User task description (natural language or structured command)
  • •agents.json (agent registry with roles, teams, triggers)
  • •ORCHESTRATOR.md (golden rules, folder structure, output formats)
  • •Current pipeline state from data/, legal/, marketing/, sales/, ops/

Outputs

  • •Task routing decisions (which team, which agents)
  • •Pipeline status reports
  • •Quality gate verdicts (PASS / FAIL + reason)
  • •Escalation notices when agents are blocked

Playbook

Step 1: Parse Intent

Classify the incoming request:

  • •Legal: keywords like Rechtsstreit, Beweis, Timeline, Klage, Anwalt, Verteidigung
  • •Data: keywords like Datei, Import, OCR, Dedupe, Index, Export
  • •Marketing: keywords like Angebot, Landing Page, SEO, Content, Newsletter, Funnel
  • •Sales: keywords like Lead, Outreach, CRM, Pipeline, Proposal, Follow-up
  • •Research: keywords like Trend, Tool, Wettbewerb, Benchmark, Prompt
  • •Ops: keywords like Deploy, Monitor, CI, Docker, Backup, Health

Step 2: Route to Team

Use agents.json to find the best-matching agents. Always assign:

  1. •A primary agent (does the work)
  2. •A QA agent from the same team (reviews output)

Step 3: Set Context

Provide each agent with:

  • •Relevant files from the correct subdirectory
  • •Prior outputs from related tasks (cross-reference)
  • •The standard output format from ORCHESTRATOR.md §3

Step 4: Quality Gate

Before marking any task DONE, verify:

  • • Output is in the correct folder
  • • YAML header metadata is present
  • • Sources are cited (Legal outputs)
  • • No unresolved [TODO] without [MISSING] + next action
  • • "Next actions" summary (5-10 lines) at the end

Step 5: Export & Report

  • •Move approved outputs to data/exports/
  • •Update pipeline status
  • •Log completion with timestamp

Safety & Quality Checks

  • •Never allow an agent to write outside its designated folder
  • •Legal outputs MUST have source citations — reject if missing
  • •All outputs must have the YAML header — reject if missing
  • •Escalate to user if confidence < medium on any legal deliverable