skill native escalation routing
- Repo stars 3,406
- Author repo claude-octopus
- Domain
- Security
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @nyldn · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
> **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`.
# Native-First Escalation Routing
Use this skill when the user asks for repository initialization, code review, or security review and it is not yet clear whether Claude-native behavior is sufficient or whether Octopus escalation is warranted.
## Core Policy
Claude-native first:
- `/init`
- `/review`
- `/security-review`
Octopus for escalation:
- `/octo:review`
- `/octo:security`
- `/octo:debate`
- `/octo:multi`
## Route to Claude-Native First
Prefer Claude-native behavior when all of the following are true:
- the request maps directly to init, review, or security review
- the user did not ask for multiple model opinions
- the user did not ask for Codex, Gemini, or another provider explicitly
- the task does not require adversarial debate, consensus scoring, or external-provider specialization
Examples:
- "initialize this repo"
- "review my staged changes"
- "security review this auth module"
## Escalate to Octopus
Escalate when the user asks for or clearly benefits from:
- multiple model opinions
- adversarial review
- debate between providers
- provider-specific analysis
- autonomous codegen verification
- elevated rigor for complex or high-risk work
Examples:
- "get multiple model opinions on this PR"
- "have Codex and Gemini review this architecture"
- "do an adversarial security review"
- "verify this AI-generated implementation before merge"
## Execution Guidance
- If Claude-native is sufficient, do not wrap the task in Octopus unnecessarily.
- If the user explicitly invokes `/octo:review` or `/octo:security`, treat that as an escalation request.
- If the request is ambiguous, prefer Claude-native first and mention Octopus as the escalation path.
## Suggested User Framing
Use wording like:
> Claude-native first, Octopus for escalation. Use Claude-native `/review` or `/security-review` for ordinary requests. Use Octopus when you want multiple model opinions, adversarial review, or stricter multi-LLM workflows.
Sections and files
Listed in source order.
sections -> Core Policy → Route to Claude-Native First → Escalate to Octopus → Execution Guidance → Suggested User Framing
terms -> Host: Codex CLI · > Host: Codex CLI — This skill was designed for Claude Code and adapted for Codex. · - If Claude-native is sufficient, do not wrap the task in Octopus unnecessarily. · > Claude-native first, Octopus for escalation.
files/cmd -> /octo:* · skills/blocks/codex-host-adapter.md · /init · /review · /security-review · /octo:review · /octo:security · /octo:debate
body sha256 -> eda8cbb45945
Core Policy
Claude-native first:
/init/review/security-reviewOctopus for escalation:Route to Claude-Native First
Prefer Claude-native behavior when all of the following are true: the request maps directly to init, review, or security review the user did not ask for multiple model opinions the user did not ask for Codex, Gemini, or another provider explicitly the task does not require adversarial debate, consensus scoring, or external-provider specialization
Escalate to Octopus
Escalate when the user asks for or clearly benefits from: multiple model opinions adversarial review debate between providers provider-specific analysis
Execution Guidance
If Claude-native is sufficient, do not wrap the task in Octopus unnecessarily. If the user explicitly invokes
/octo:reviewor/octo:security, treat that as an escalation request. If the request is ambiguous, prefer Claude-native first and mention Octopus as the escalation path.Suggested User Framing
Use wording like: Claude-native first, Octopus for escalation. Use Claude-native
/reviewor/security-reviewfor ordinary requests. Use Octopus when you want multiple model opinions, adversarial review, or stricter multi-LLM workflows.