Strategic Orchestration

Coordinate agents toward a unified objective; assign roles, sequence work, prevent conflicts, and define success criteria.

Security Scan

The skill is an instruction-only orchestration helper whose declared requirements and runtime instructions are consistent with its stated purpose; no disproportionate permissions, installs, or hidden behaviors were found.

Purpose & Capability

Name/description (coordinate agents, assign roles, sequence work) matches the instructions and required inputs (objective, system_state). The skill requests no binaries, credentials, or config paths beyond what is needed for orchestration.

Instruction Scope

SKILL.md stays within orchestration responsibilities: it asks for an objective and system state, maps roles, sequences tasks, detects conflicts, and drafts handoff messages. It does not instruct reading arbitrary files, contacting external endpoints, or accessing hidden credentials.

Install Mechanism

No install spec and no code files — instruction-only — so nothing is downloaded or written to disk. This minimizes installation risk.

Credentials

The skill requests no environment variables, credentials, or config paths. The listed agent roles (Morpheus/RedHat/Trinity/Smith) are internal role mappings and do not require external secrets.

Persistence & Privilege

Defaults are used (not always:true). The skill can be invoked autonomously by agents (platform default) but it does not request elevated or persistent system privileges.

Assessment

This skill appears coherent and low-risk: it only contains orchestration instructions and asks for no credentials or installs. Before installing, verify the agent names and owners used in your environment (the SKILL binds judgment to a 'Morpheus' agent — ensure you trust that agent), confirm the version/owner metadata if provenance matters (files show 'Morpheus' owner while registry metadata lists a different owner id), and test the skill in a sandboxed workflow to ensure its handoff messages and role assignments behave as you expect. Refuse to let the skill authorize irreversible actions without explicit human approval, as its own safety rules suggest.

SKILL: strategic-orchestration

Purpose

Coordinate all agents toward a unified objective with clear roles, sequencing, and success criteria.

When to Use

• A goal requires multiple agents (Morpheus/Trinity/RedHat/Smith)
• Work is stuck due to unclear ownership or sequencing
• Conflicting actions or duplicated efforts appear

Inputs

• objective (required): the desired outcome in one sentence
• system_state (required): current tasks, constraints, risks, and available resources

Steps

1. Define the goal clearly and state non-goals.
2. Define success criteria (what “done” looks like) and the validation path.
3. Map required agents and assign responsibilities:
   • Morpheus → judgment, direction, risk evaluation
   • RedHat → execution, implementation, verification
   • Trinity → routing/coordination/capital engine (when applicable)
   • Smith → adversarial pressure / stress test (bounded)
4. Define sequence:
   • dependencies first
   • execution second
   • validation checkpoints
5. Define agent-to-agent interfaces:
   • what each agent must deliver to the next
   • what inputs are required
6. Detect conflicts:
   • overlapping ownership
   • governance boundary violations
   • unvalidated leaps
7. Output the orchestration plan and the next immediate messages/actions.

Validation

• No conflicting actions across agents.
• Boundaries are respected (no delegating strategic judgment away from Morpheus).
• Each step has an owner and an acceptance criterion.

Output

• execution_plan (ordered steps with owners)
• agent_roles
• dependencies
• handoff_messages (drafts to each agent)
• success_criteria

Safety Rules

• Do not authorize irreversible actions without explicit approval and governance alignment.
• Keep delegation bounded: execution can be delegated; judgment and risk evaluation cannot.

Example

Objective: “Ship a safe MCP + skills update this week.” Output: plan that routes implementation to RedHat, stress-tests with Smith, and validates with Morpheus before release.