Menu
Show claude-anyteam plugin setup status and the adapter launch command.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use proactively when the user wants help creating, observing, or managing Agent Teams teammates with claude-anyteam CLI backends. Covers the required spawn setup (`team-agent` before `Agent(...)`, otherwise bare codex-/gemini-/kimi- prefixes are refused), post-spawn repair (`team-patch`, `team-roster`), teardown (`team-kill`), observability (`status`, `diagnose`, `visibility-tail`), and the codex-app-server native tool surface (imagegeneration, websearch, imageview, filechange) that lives outside the wrapper-MCP layer. Prefer this skill over ad-hoc Write/Edit/Bash against `~/.claude/teams/` and over reaching for `codex-jr:codex-rescue` when the user wants a real teammate.
Read-only claude-anyteam substrate inspector for leads. Use when the lead invokes /claude-anyteam:diagnose or asks to inspect team roster, manifest cache, visibility_degraded events,
| name | status |
| description | Show claude-anyteam plugin setup status and the adapter launch command. |
| disable-model-invocation | true |
Run a short Bash check against ~/.claude/settings.json to determine whether
env.CLAUDE_CODE_TEAMMATE_COMMAND is present and non-empty.
Then reply with exactly two bullet points:
Setup: say configured or not configuredLaunch: show setsid nohup claude-anyteam --team <team> --name codex-<name> --cwd <workspace> </dev/null >/tmp/claude-anyteam.stdout 2>/tmp/claude-anyteam.stderr & disownKeep the response short and do not add extra commentary.