Menu
Control and inspect Chrome via the Chrome DevTools MCP server (navigate, interact, screenshots, console, network, perf).
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
Primary entrypoint for Codex Orchestrator usage: route tasks to the right pipeline, mode, and supporting skills with minimal, auditable steps.
Manage non-trivial tasks via focused collab subagents to save context and improve throughput. Use when work spans multiple files/components, can be split into independent streams, needs separate validation/review, or risks context bloat. Favor direct execution for trivial one-shot tasks.
Ship a signed tag + GitHub Release + npm publish for @kbediako/codex-orchestrator with low-friction, agent-first steps (PR -> watch-merge -> tag -> watch publish -> downstream smoke).
Use when operating the Codex delegation MCP server and tools (delegate.spawn, delegate.question.*, delegate.cancel, github.merge confirmation flow), or when configuring delegation mode/tool_profile with delegation MCP enabled by default.
Use for required periodic cross-check reviews during implementation and before handoff using `codex review`.
Run collab/multi-agent eval scenarios (symbolic RLM, large-context, pause/resume, multi-hour checkpoints) and capture manifest-backed evidence.
| name | chrome-devtools |
| description | Control and inspect Chrome via the Chrome DevTools MCP server (navigate, interact, screenshots, console, network, perf). |
| allowed-tools | mcp__chrome-devtools__* |
Use this skill when you need browser-grounded evidence (UI screenshots, console errors, network failures, perf traces) or when a task requires real page interaction.
codex-orchestrator devtools setup --yes.codex -c 'mcp_servers.chrome-devtools.enabled=true' ...list_console_messageslist_network_requests (and fetch details for failures)standalone-review: route ad-hoc review checks through a manifest-backed review loop when findings need auditability.collab-subagents-first: isolate heavy browser exploration in a dedicated subagent stream to protect parent context.frontend-design-review: optional global skill (not bundled in CO release); use when the task emphasis is structured UI/UX critique with evidence-backed recommendations.long-poll-wait: monitor long-running browser-driven checks or CI replay loops to terminal state.