Menu
Auto-route tasks to the optimal tool, model, and subscription. Registry-backed provider and model truth only. Content governance enforced.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Manage overnight autonomous coding tasks
Cross-reference hardware inventory against node configs, detect discrepancies
Perpetual improvement loop. Find the weakest part of the system and make it better. Never stops. Use when continuing work, when idle, when asked to improve, or when nothing specific is requested.
Run drift detection to verify system matches architectural decisions
Structured process for making and documenting architecture decisions with ADR format
Quick cluster health dashboard with live GPU, container, and disk status from all nodes
| name | delegate |
| description | Auto-route tasks to the optimal tool, model, and subscription. Registry-backed provider and model truth only. Content governance enforced. |
| triggers | ["delegate","local model","offload","route","which tool"] |
Automatically pick the best tool, model, and subscription for any task. The user never decides manually.
| Class | Route | Examples |
|---|---|---|
| cloud_safe | Any tool/sub | Open-source code, docs, public data |
| private_but_cloud_allowed | Trusted cloud or local | Business data, client info |
| hybrid_abstractable | Cloud sees structure only, raw stays local | Sensitive designs |
| refusal_sensitive | LOCAL ONLY (JOSIEFIED/Dolphin) | NSFW, adult content, EoBQ |
| sovereign_only | LOCAL ONLY | Pen testing, credentials, hacking |
If refusal_sensitive or sovereign_only → skip to Step 3 (local routing).
Do not route from a hardcoded subscription table. Use the current truth sources:
config/automation-backbone/provider-catalog.jsonprojects/agents/config/subscription-routing-policy.yamldocs/operations/PROVIDER-CATALOG-REPORT.mdChoose the lowest-cost lane that still matches the task, current confidence, and live availability. Keep refusal_sensitive and sovereign_only work off cloud lanes even if a provider looks healthy.
Do not route from stale endpoint tables. Use the current truth sources:
config/automation-backbone/model-deployment-registry.jsondocs/operations/MODEL-DEPLOYMENT-REPORT.mdconfig/automation-backbone/hardware-inventory.jsonKeep refusal_sensitive and sovereign_only work local-only. Choose the local lane that matches the task class and current deployment status.
For background or autonomous tasks, route through the current live control-plane surfaces and agent roster. Do not rely on archived MCP command examples or stale local endpoint notes. Use the active operator and routing truth in the current registries and reports before delegating work.
Review all delegated output before accepting. Check correctness, style, security, completeness, and that the chosen provider or model lane still matches the current registry-backed truth.