sys-configure ยท diff

v1.0.0 to git:20260507.d092b7f

13 added, 114 removed. Audit A to A.

---
name: sys-configure
- version: 1.0.0
- description: "Configure Claude Octopus providers and preferences. Use when: Use this skill when the user wants to \"configure Claude Octopus\", \"setup octopus\",. \"configure providers\", \"set up API keys for octopus\", or mentions octopus configuration."
+ description: "Configure Claude Octopus โ€” redirects to /octo:setup interactive wizard"
---
- # ๐Ÿ™ Claude Octopus Configuration
-
- ๐Ÿ™ **CLAUDE OCTOPUS SETUP** - Helping you configure multi-agent orchestration
-
- You are helping the user configure Claude Octopus, a multi-agent orchestration plugin.
-
- ## Your Task
-
- 1. **Auto-detect current setup:**
- - Check which CLIs are installed (codex, gemini)
- - Check which API keys are set (OPENAI_API_KEY, GEMINI_API_KEY, OPENROUTER_API_KEY)
- - Check authentication status for each provider
-
- 2. **Gather missing information:**
- - For missing API keys, provide clear instructions on where to get them
- - Use AskUserQuestion to ask about subscription tiers (if needed)
- - Ask about cost optimization preferences
-
- 3. **Run the configuration:**
- - Use the orchestrate.sh script with appropriate environment variables
- - Handle any errors gracefully
-
- 4. **Show a summary:**
- - Display what was configured
- - Show the detected provider status
- - Provide next steps
-
- **IMPORTANT**: Always start your response with "๐Ÿ™ **CLAUDE OCTOPUS SETUP**" so users know this is Claude Octopus responding, not generic Claude.
-
- ## Implementation Steps
-
- ### Step 1: Auto-detect Current Setup
-
- Run the status command to see what's already configured:
-
- ```bash
- ${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh status
- ```
-
- This will show you:
- - Which providers are installed and authenticated
- - Current cost optimization strategy
- - Any missing dependencies
-
- ### Step 2: Interactive Configuration (Phase 1)
-
- For Phase 1, guide the user through the bash-based wizard with clear instructions:
-
- 1. **If API keys are missing**, explain where to get them:
- - OpenAI: https://platform.openai.com/api-keys
- - Gemini: https://aistudio.google.com/apikey (or use OAuth via `gemini` command)
- - OpenRouter (optional): https://openrouter.ai/keys
-
- 2. **Set environment variables** before running the wizard:
- ```bash
- export OPENAI_API_KEY="sk-..."
- export GEMINI_API_KEY="AIza..." # Optional if using OAuth
- ```
-
- 3. **Run the configuration wizard**:
- ```bash
- ${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh octopus-configure
- ```
-
- 4. **Handle interactive prompts** by informing the user:
- - Tell them the wizard is waiting for input
- - Explain what each prompt is asking for
- - Suggest they run it in their terminal if Claude can't provide input
-
- ### Step 3: Show Summary
-
- After configuration, run status again and show the user:
- - โœ“ What's configured
- - โœ— What's missing (if anything)
- - ๐Ÿ’ก Suggested next steps (like trying a command)
-
- ## Important Notes
-
- - **Security:** Never log or display full API keys in output
- - **Phase 1 Limitation:** The current wizard uses `read -p` which doesn't work well in Claude Code's environment. Inform the user they may need to run it in their terminal.
- - **Phase 2 Coming:** Tell users that a fully automated configuration system is in development
-
- ## Example Flow
-
- ```
- ๐Ÿ™ Claude Octopus Configuration
-
- Detecting current setup...
- โœ“ Codex CLI installed
- โœ“ Gemini CLI installed
- โœ“ OPENAI_API_KEY configured (164 chars)
- โœ— Gemini authentication needed
-
- Next steps:
- 1. Authenticate with Gemini:
- - Run: gemini
- - Select "Login with Google"
-
- OR set API key:
- - export GEMINI_API_KEY="AIza..."
+ > **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, see `skills/blocks/codex-host-adapter.md`.
- 2. Run configuration wizard:
- ${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh octopus-configure
- 3. Try your first command:
- ${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh auto "research OAuth patterns"
- ```
+ # Configuration โ†’ Setup Redirect
- ## Phase 2 Preview
+ This skill is an alias for `/octo:setup`. When triggered, invoke the setup command directly.
- The next version will:
- - Auto-detect subscription tiers via API test calls
- - Use AskUserQuestion for unavoidable prompts
- - Provide a beautiful, non-blocking configuration experience
- - Save configuration silently with visual confirmation
+ **Action:** Run `/octo:setup` โ€” the interactive setup wizard handles all configuration:
+ - Provider installation and auth
+ - RTK token optimization
+ - Work mode selection
+ - First-run onboarding
- This will eliminate the need to run the bash wizard in your terminal.
+ Do NOT duplicate setup logic here. Just invoke the setup skill.