/interop-router
Suggest 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.
$ npx -y skills add claude-world/director-mode-lite --skill interop-router --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/interop-router
Context preview
The summary Claude sees to decide when to auto-load this skill.
Suggest 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.
SKILL.md
interop-router.SKILL.mdname: interop-router
description: Suggest 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.
user-invocable: true
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
1. Name the recommended CLI and one reason. 2. Name the switching cost or uncertainty. 3. Offer to create a `session-relay` packet. 4. 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.
Read more
name: interop-router description: Suggest 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. user-invocable: true
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
1. Name the recommended CLI and one reason. 2. Name the switching cost or uncertainty. 3. Offer to create a `session-relay` packet. 4. 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.
Use Claude Code like a Director, not a Programmer. MIT toolkit with Auto-Loop, guided setup, 27 commands, 14 agents, and 32 skills.
Other skills on director-mode-lite.
- /changelog-observer
Track development session events in a daily markdown changelog, including file changes, test results, and key decisions.
Open skill - /agent-check
Validate custom agent file format and structure. Use after creating or editing an agent, before committing agent changes, or when an agent fails to load.
Open skill - /agent-template
Generate custom agent from template. Use when creating a new subagent from scratch, or scaffolding an agent file with correct frontmatter.
Open skill - /agents
List all available agents (core, expert, self-evolving). Use when the user asks what agents are available or runs /agents.
Open skill - /auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog
Open skill - /changelog
View and manage the runtime changelog for observability
Open skill

