技能 Native Escala
- 作者仓库星标 3,406
- 作者仓库 claude-octopus
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, seeskills/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: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.
- 流狐分类
- 安全
- 作者声明 Agent
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 作者 / 版本 / 许可
- @nyldn · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 需简单配置
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- Shell 执行
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。 Claude-native first: /init /review
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
Escalate when the user asks for or clearly benefits from: multiple model opinions adversarial review
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…
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.
> **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"
… 作者原文负责流程事实;流狐只索引当前章节、要点、文件与命令。
章节 -> Core Policy → Route to Claude-Native First → Escalate to Octopus → Execution Guidance → Suggested User Framing
要点 -> 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.
文件/命令 -> /octo: · skills/blocks/codex-host-adapter.md · /init · /review · /security-review · /octo:review · /octo:security · /octo:debate
内容 SHA-256 -> eda8cbb45945
原文结构
适用与边界
原文中的明确线索
/octo:、skills/blocks/codex-host-adapter.md、/init、/review、/security-review、/octo:review、/octo:security、/octo:debate