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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.7 KB |
| scripts/check_cli_available.shexecutable | script | 1.3 KB |
| scripts/score_decision.pyexecutable | script | 4.2 KB |
| scripts/wrap_context.pyexecutable | script | 6.4 KB |
scripts/check_cli_available.sh
View on GitHub#!/usr/bin/env bash
# Report available first-class CLIs. This script never launches or configures one.
set -euo pipefail
JSON_OUTPUT=false
[[ "${1:-}" == "--json" ]] && JSON_OUTPUT=true
probe() {
local name="$1"
if command -v "$name" >/dev/null 2>&1; then
local version
version="$("$name" --version 2>&1 | head -1 || true)"
printf 'true|%s\n' "$version"
else
printf 'false|\n'
fi
}
claude_result="$(probe claude)"
codex_result="$(probe codex)"
grok_result="$(probe grok)"
if $JSON_OUTPUT; then
CLAUDE_RESULT="$claude_result" CODEX_RESULT="$codex_result" GROK_RESULT="$grok_result" python3 - <<'PY'
import json
import os
def value(name):
available, version = os.environ[name].split("|", 1)
return {"available": available == "true", "version": version}
print(json.dumps({
"claude": value("CLAUDE_RESULT"),
"codex": value("CODEX_RESULT"),
"grok": value("GROK_RESULT"),
"behavior": "report-only",
}, indent=2))
PY
else
echo "=== AI CLI availability (report only) ==="
printf 'Claude Code: %s\n' "${claude_result#*|}"
printf 'Codex CLI: %s\n' "${codex_result#*|}"
printf 'Grok Build: %s\n' "${grok_result#*|}"
echo "No CLI was launched and no permission or routing setting was changed."
fi
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: 471k | 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 |