mcpField
S
skill-native-escalation-routing

skill-native-escalation-routing

github.com/nyldnAgent workflows4.3k47 installsUpdated today
Repository

About skill-native-escalation-routing

A Codex CLI skill for routing repository initialization, code review, and security review requests. It defaults to Claude-native workflows and identifies cases where Octopus escalation is appropriate, such as multi-model or adversarial analysis.

Key features

  1. 01Claude-native-first routing
  2. 02Octopus escalation criteria
  3. 03Provider-aware request handling
  4. 04Codex host tool guidance

Use cases

  1. 01Choosing a review path for a repository task
  2. 02Escalating for multiple model opinions
  3. 03Routing high-risk security reviews

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nyldn/claude-octopus --skill skill-native-escalation-routing

After installing, type/skill-native-escalation-routingin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

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.

Comments

Markdown supported