Content
67%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a disciplined, information-dense router skill: it sequences the five-phase workflow, embeds hard validation gates and error-recovery rules, and delegates details to per-trigger reference files. Its main weaknesses are rule repetition across sections 1-3 that could be consolidated, and inconsistent reference path forms combined with referenced files that are absent from the bundle.
Suggestions
Consolidate the continuation/state-requery rules (currently restated in §1, §2, and §3) into a single rule, leaving each section to reference it — this would cut noticeable token duplication without losing behavior.
Unify reference path forms to one base (e.g., always reference/scripts.md or always comet-classic/reference/scripts.md) so the agent resolves paths unambiguously.
State the mainline happy path up front (resolve workspace → select change → load the phase skill → follow continuation) before the edge-case conditionals, so the primary sequence is legible without parsing dozens of branches.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is extremely dense with no concept padding, but the same rule clusters are restated across sections: continuation/state-requery rules appear in §1 ("选择结果已包含…直接继续；只有缺少信息…才运行 comet state next"), §2 ("同一组任务复用命令结果和已有上下文…才重新查询"), and §3 ("没有可复用的状态信息…才重新查询"), and context-recovery triggers are given at three separate points. This fits 'mostly efficient but could be tightened'; not 2 since nothing is padded or explains concepts Claude already knows. | 3 / 5 |
Actionability | Concrete executable commands appear throughout (comet classic workspace resolve <change-name> --json, comet state select <change-name> --json, comet resume-probe . --stdin --json, comet state restore <change-name> --confirmed) alongside explicit directives ("使用 Skill 工具加载 comet-open 技能。禁止跳过此步骤") and hard stop conditions. Not 5 because a substantial portion of the guidance is conditional routing whose actual procedures live in external reference files rather than here. | 4 / 5 |
Workflow Clarity | A clear numbered sequence (确定目标与工作区 → 载入当前阶段 → 继续完成) with explicit validation ("只有实际运行过测试或构建，才能声称完成相应检查", host-check before approving Open, debug-gate "先调查再修复") and error-recovery loops ("入口错误与恢复" → report the original error and apply recovery rules). It falls short of 5 because several checkpoints — host-check's actual content, 预设范围复核's checks — are signaled by reference rather than specified inline, leaving minor validation gaps. | 4 / 5 |
Progressive Disclosure | The body works as an overview router with well-signaled, one-level-deep references gated by explicit read conditions ("需要状态字段含义时读 comet-classic/reference/comet-yaml-fields.md…其余参考只在上方触发条件满足时读取"). It falls short of 5 because no referenced files exist in this bundle to verify, and path bases are inconsistent (comet-classic/reference/scripts.md vs reference/scripts.md vs ../comet/reference/host-check.md), which makes navigation error-prone. | 4 / 5 |
Total | 15 / 20 Passed |