nyldn/claude-octopus

skill-native-escalation-routing

Use when choosing native or multi-LLM handling for init, review, or security requests

First seen May 7, 2026

Installation

$ npx skills add nyldn/claude-octopus --skill skill-native-escalation-routing

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from nyldn/claude-octopus · top by installs.

npx skills add nyldn/claude-octopus

Browse all from nyldn/claude-octopus

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 4.0K
License licenses
Default branch main
Open issues 3
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code codex antigravity

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,571 B
  • docs SUMMARY.md 124 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 20 installs

SKILL.md

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, Antigravity, 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 Antigravity 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.