技能本机升级路由

安全 社区

技能解读

当前原文的自动摘译,尚未人工审校。

核心政策

克劳德本地人首先:/init``/review``/security-review升级章鱼:

前往 Claude-Native First 的路线

当满足以下所有条件时,首选 Claude 原生行为: 请求直接映射到初始化、审查或安全审查 用户没有询问多个模型意见 用户没有明确询问 Codex、Gemini 或其他提供商 该任务不需要对抗性辩论、共识评分或外部提供商专业化

升级至八达通

当用户要求或明显受益时升级: 多种模型意见 对抗性审查 提供商之间的辩论 特定于提供商的分析

执行指导

如果 Claude-native 就足够了,不必要时不要将任务包装在 Octopus 中。如果用户明确调用/octo:review或/octo:security,请将其视为升级请求。如果请求不明确,请首先选择 Claude-native,并提及 Octopus 作为升级路径。

建议的用户框架

使用这样的措辞:克劳德本地人优先,章鱼升级。对于普通请求,请使用 Claude-native /review 或 /security-review。当您需要多个模型意见、对抗性审查或更严格的多法学硕士工作流程时,请使用 Octopus。

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
安全
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@nyldn · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
需简单配置
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 命令执行
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) 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, 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.

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。