Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-structured orchestrator overview with concrete routing, explicit gating checkpoints, and helpful worked examples. Its main weaknesses are repeated FLOW_*/COMMON_RULES listings and that the core referenced FLOW_*.md and COMMON_RULES.md files are absent from the bundle, breaking the progressive-disclosure navigation it relies on.
Suggestions
Add the missing ./COMMON_RULES.md and the five ./FLOW_*.md files to the bundle, or remove their references from the body — the routing table, subprocess rules, and resource list all point to files that do not exist.
De-duplicate the FLOW_*.md mapping: it appears in the 流程路由 table, the 子流程调用规则 section, and the 上下文资源 list — keep it in one place and reference it.
Consider noting the additional ./references/ domain files (crm_sales, project_delivery, supply_chain) and bkn_report_template.html in the body, since they exist in the bundle but are not referenced.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Per-section the body is lean (tables, terse MUST/Never rules, no explaining of concepts Claude already knows), but the same FLOW_*.md mappings are listed three times (流程路由 table, 子流程调用规则, 上下文资源) and COMMON_RULES.md is pointed to repeatedly, so it could be tightened. | 2 / 3 |
Actionability | Concrete, specific routing (intent → keyword → target FLOW file), a named progressive protocol ('discover -> preview -> confirm -> execute -> verify -> report'), explicit MUST/Never constraints, a failure-fallback table, and worked 正例/反例 examples give copy-ready guidance; per the rubric, absence of code in this instruction-only orchestrator skill is not penalized. | 3 / 3 |
Workflow Clarity | A clear sequenced protocol with explicit validation/gating checkpoints ('MUST 回显流程路由识别结果并等待用户确认', '任何写操作必须先完成确认步骤') and a feedback loop for error recovery ('工具调用失败：停在当前阶段…Never 自动重试或跳过'), satisfying the explicit-checkpoint anchor including for the destructive delete flow. | 3 / 3 |
Progressive Disclosure | The design is good — a concise overview signaling one-level-deep references to FLOW_*.md and COMMON_RULES.md — but scored against the actual bundle those six core referenced files are missing, so the primary navigation targets are dead links even though ./references/ does contain real files (DOMAIN_ROUTING.md, generic_extraction.md, domain files). | 2 / 3 |
Total | 10 / 12 Passed |