swap-control-center

Swap Control Center

Use this skill as the dynamic-provider preset for agent-control-center. Keep one orchestration engine and exactly one active controller.

Procedure

1. Read Agent Control Center and its four references. If the core skill is incomplete, stop and report the missing resource.
2. Freeze the objective, host, topology, scope, authorization, budget, and acceptance contract before route selection.
3. Build the live route inventory first. Classify every application, CLI, SDK, API, MCP bridge, and manual route independently. Never infer a ready route from a provider name or an application login.
4. Follow provider-selection.md. In the active parent conversation, use the host's exposed structured question tool, including AskUserQuestion or request_user_input when that exact tool is available. Otherwise ask one concise plain-text question at a time. Resolve controller and worker routes independently from current verified capabilities. Derive manual-handoff from a manual controller transport; otherwise select a compatible automatic or sequential relay mode. Never infer worker assignments from the selected controller.
5. If the chosen route needs setup, present the exact official source, version, install or configuration action, authentication step, expected billing or data boundary, rollback, and bounded smoke test. Obtain explicit user approval before each state-changing action or paid request. Rebuild the inventory after setup.
6. Bind the selected controller provider to controller=<provider-id>, bind the separately selected worker defaults or per-role routes, and run the Agent Control Center host-mediated loop. The host parent remains the user-facing relay and dispatch authority. The selected controller owns decomposition, work-order decisions, receipt review, and final acceptance. Topology skills execute controller-issued orders and do not create a second plan or controller. For provider=codex and transport=codex-cli, use the bundled stateful bridge in ../agent-control-center/references/codex-cli-bridge.md. Do not improvise a one-shot command. Other external providers require an equivalent verified preflight, start, reply, cancel, and close adapter before automatic use.
7. If the user requests a later role swap, use the one-transfer contract in controller-modes.md. Pause dispatch, settle outstanding work, obtain any required approval, invalidate unused old orders, and resume with one new controller. Never run co-controllers or recursive controller delegation.
8. Report the active host, controller provider, transport, requested and attested model settings, setup or smoke-test evidence, worker routes, transfer history, validation, fallback, and residual risk.