Using Agent Skills Router — Using 代理 技能s 路由r

Using 代理 技能s 路由r

Use this 技能 as a lightweight dis补丁er. It decides which 技能, 工作流, or 角色 should handle a 请求, then keeps the active path proportional to the task.

Routing 工作流 Re状态 the user goal in one sentence. Classify the 请求: tiny: answer or edit directly; avoid ceremony. implementation: choose the most specific build or domAIn 技能. review: choose a review 技能 or a reviewer persona. ship: choose a lifecycle or release 技能. unclear: gather repo 上下文 first, then decide. Select the smallest useful 技能 设置. Prefer one primary 技能 and at most one support 技能. 状态 the 路由 briefly before executing: Using <技能> because . If no 技能 matches, continue with normal Codex behavior and say no specialized 技能 was needed. 技能 Selection Rules Prefer exact domAIn 技能s over broad lifecycle 技能s. Prefer 仓库-native 工具s, tests, and docs over generic 检查列出s. Use a lifecycle 技能 only when the user wants planning, implementation, verification, review, or shipping as a process. Use a high-risk review 技能 when the task touches security controls, 凭证s, data deletion, public release, money, production 系统s, or broad 权限s. Avoid stacking 技能s that repeat the same gate. One clear review path is better than several shallow ones. 输出 Shape

For a routing-only answer, return:

路由: <技能-or-direct> Reason: Next action:

For execution tasks, keep the routing note short and then proceed. Do not 创建 docs or task files unless the user asks or the chosen 技能 requires durable artifacts.

Anti-Patterns Do not turn small fixes into a full spec-plan-build-review cycle. Do not load long reference files just to decide whether a 技能 应用lies. Do not 角色-play multiple 代理s when the 运行time cannot actually isolate their work. Do not ask the user which 技能 to use when local 上下文 makes the choice clear.