Use when choosing native or multi-LLM handling for init, review, or security requests
58
66%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/skill-native-escalation-routing/SKILL.mdHost: 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, seeskills/blocks/codex-host-adapter.md.
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.
Claude-native first:
/init/review/security-reviewOctopus for escalation:
/octo:review/octo:security/octo:debate/octo:multiPrefer Claude-native behavior when all of the following are true:
Examples:
Escalate when the user asks for or clearly benefits from:
Examples:
/octo:review or /octo:security, treat that as an escalation request.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.
242e51d
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.