Start the interactive Claude Octopus setup wizard to install and authenticate providers, configure RTK token optimization, choose a work mode, and complete onboarding. This skill directs configuration requests to the existing setup process.
Configure Claude Octopus — redirects to /octo:setup interactive wizard
Review the instructions the agent will receive before you install.
Host: Codex CLI — This skill was designed for Claude Code and adapted for Codex. Cross-reference commands use installed skill names in Codex rather than
/octo:*slash commands. Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it. For host tool equivalents, seeskills/blocks/codex-host-adapter.md.
This skill is an alias for /octo:setup. When triggered, invoke the setup command directly.
Setup uses a separate, private resume receipt. It rechecks readiness before trusting a recorded stage, leaves interrupted human login incomplete, and marks the receipt complete only after strict configuration persistence and readback. The user runs browser-opening authentication in their own terminal. Remote sessions never open it automatically.
Action: Run /octo:setup — the interactive setup wizard handles all configuration:
Do NOT duplicate setup logic here. Read
${HOME}/.claude-octopus/plugin/commands/setup.md and follow it only because
the user explicitly invoked this configuration skill.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Interpret the saved results of a completed AI council review. Count verdicts, check whether enough participants responded and whether models are independent, surface substantive dissent, and explain what action the outcome supports.
Turn a technical choice into a structured debate between different AI model families. Assign explicit positions, launch the discussion, and summarize agreement, disagreement, and a recommendation supported by the strongest argument that survives the debate.
Clarify a feature’s requirements with multiple AI providers, combining technical constraints with user and business needs. Produce a scoped definition covering priorities, edge cases, exclusions, and a requirements checklist before implementation begins.
Review code or documents with available AI providers before delivery. Combine findings into a scored validation report that checks prior requirements and decisions, separates critical issues from warnings, and recommends next steps.
Develop complex features or business documents by gathering approaches from available AI providers. Combine their perspectives with prior project decisions and quality checks to produce a proposed plan, then proceed with implementation after user confirmation.
Research technical or business questions through multiple available AI providers, each assigned a different perspective. Combine usable results into a report covering findings, disagreements, evidence gaps, priorities, and recommended next steps.