strategic-orchestration
Coordinate agents toward a unified objective; assign roles, sequence work, prevent conflicts, and define success criteria.
What this skill does
# 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.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.