Configure Claude Octopus — redirects to /octo:setup interactive wizard
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add nyldn/claude-octopus --skill sys-configure --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Sys Configure?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/nyldn-sys-configure-claude-octopus)More formats (shields.io, HTML) on the badges page.
---
name: sys-configure
description: "Configure Claude Octopus — redirects to /octo:setup interactive wizard"
disable-model-invocation: true
---
> **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`.
# Configuration → Setup Redirect
This skill is an alias for `/octo:setup`. When triggered, invoke the setup command directly.
**Action:** Run `/octo:setup` — the interactive setup wizard handles all configuration:
- Provider installation and auth
- RTK token optimization
- Work mode selection
- First-run onboarding
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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
