agentleFS
Sign inStart free
claude-worldclaude-world/director-mode-lite/skills/interop-router/SKILL.md

interop-router

Skill80 starsChanged 8 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If accepted, create it and print the receiving command.

    line 38
  2. Distinctive:

    Keep the result at suggestion level.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

NeedUseful option
Stay with the full current conversationKeep the current CLI
Independent implementation or reviewCodex CLI or Grok Build
Claude-native project workflow or existing Claude sessionClaude Code
Claude-compatible import plus xAI-native workflowsGrok Build
Repository instructions and reusable cross-tool skillsCodex 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free