claude-world/director-mode-lite / skills/interop-router
interop-router
FlaggedSuggest whether Claude Code, Codex CLI, or Grok Build is a useful next collaborator, without launching a CLI or changing controls. Use when comparing the three CLIs, planning a handoff, or deciding whether an independent implementation or review would help.
Cross-CLI Routing Guide
Offer a recommendation, its tradeoffs, and a copyable next step. Do not launch another CLI unless the user asks you to execute the handoff.
Decision prompts
- Continuity: would switching cost more context than it saves?
- Fit: does another CLI have a native workflow or perspective useful here?
- Independence: would a separate review reduce correlated mistakes?
- Worktree: can the receiver safely inspect or edit the current repository?
- Evidence: is the handoff packet specific enough to verify completion?
Practical mapping
| Need | Useful option |
|---|---|
| Stay with the full current conversation | Keep the current CLI |
| Independent implementation or review | Codex CLI or Grok Build |
| Claude-native project workflow or existing Claude session | Claude Code |
| Claude-compatible import plus xAI-native workflows | Grok Build |
| Repository instructions and reusable cross-tool skills | Codex CLI |
These are starting points, not rankings. Prefer the CLI the user already has authenticated and understands unless a switch brings a concrete benefit.
Suggested response
- Name the recommended CLI and one reason.
- Name the switching cost or uncertainty.
- Offer to create a
session-relaypacket. - If accepted, create it and print the receiving command.
Keep the result at suggestion level. Never add auto-approve, permission bypass, sandbox, network, or hook-trust flags to make a handoff easier.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |