ao-spawn-minimax-worker

name	ao-spawn-minimax-worker
description	Spawn an Agent-Orchestrator (AO) worker that uses the minimax CLI with the M3 model (via the minimax Anthropic-compatible API). Use when: the task should be dispatched to a worker that uses minimax M3 specifically, when the user says 'use minimax', 'use the M3 model', 'use the minimax worker', 'ao spawn minimax', or 'minimax CLI for AO'. This skill verifies the env (MINIMAX_MODEL, MINIMAX_API_KEY, ANTHROPIC_BASE_URL) end-to-end, then runs `ao spawn --agent minimax`. Verified 2026-06-13 against session ao-6355 / PR #678.
when_to_use	Use when the user asks to spawn an AO worker on minimax M3, or any time `ao spawn` is needed and the model choice is minimax. Do NOT use for: direct `claude` CLI runs (use shell directly), or for AO workers that should use a different model (use the default `ao spawn` with no `--agent` flag). NOT for fixing 401 errors (use `minimax-401-diagnostic` instead).
allowed-tools	["Bash","Read","Write","Edit"]
context	Verified end-to-end on 2026-06-13 with session ao-6355 and PR https://github.com/jleechanorg/agent-orchestrator-ts/pull/678. The agent-minimax plugin (packages/plugins/agent-minimax/src/index.ts) wraps the `claude` CLI with ANTHROPIC_BASE_URL=https://api.minimax.io/anthropic and propagates MINIMAX_MODEL from the tmux env. modelByCli.minimax.model=MiniMax-M3 in ~/agent-orchestrator.yaml makes this the default. The skill is intentionally a thin pointer — the canonical implementation is the AO plugin source + the user's `~/agent-orchestrator.yaml`.

ao-spawn-minimax-worker

What it does

Spawns an AO worker that uses the minimax CLI (an Anthropic-compatible adapter) with the M3 model. Verifies env, then dispatches.

When NOT to use this skill

• The user wants a direct claude CLI run (use the shell — no AO)
• The user wants a different model (just ao spawn "<task>" with no --agent flag)
• The user is debugging a 401 from the minimax API → use minimax-401-diagnostic instead
• The user wants a non-AO worker (e.g., claude -p, codex, opencode) → use those CLIs directly

Pre-flight checks (do these BEFORE spawning)

# 0. CRITICAL — Check that AO will actually source bashrc.
#    An explicit envSource: [] in agent-orchestrator.yaml overrides the default
#    of ["~/.bashrc"] and silently disables bashrc sourcing, which means
#    MINIMAX_API_KEY never reaches the plugin (bd-g884 regression / 2026-06-13).
#    Refuse to spawn if this is wrong; do not work around it.
#    Regex is indented-anchored (`^\s*envSource:`) so it matches whether the
#    key sits at column 0 or nested under `defaults:` / a project block.
if grep -E '^\s*envSource:\s*\[\s*\]\s*$' ~/agent-orchestrator.yaml >/dev/null 2>&1; then
  echo "BLOCKER: ~/agent-orchestrator.yaml has 'envSource: []' — AO will NOT"
  echo "         source bashrc, so MINIMAX_API_KEY will be missing. Fix the"
  echo "         config first (replace with [\"~/.bashrc\"] or delete the line"
  echo "         to restore the default). Aborting spawn."
  exit 1
fi

# 1. Confirm minimax model is set in bashrc
grep "^export MINIMAX_MODEL" ~/.bashrc

# 2. Confirm API key resolves in the current shell (sanity check only — the

[ -n  ] &&   ||  


curl -s -o /dev/null -w  -m 5 https://api.minimax.io/anthropic





: 
 MINIMAX_ANTHROPIC_BASE_URL
 




curl -s -m 30 -X POST  \
  -H  \
  -H  \
  -H  \
  -d  \
  | python3 -c