Content
77%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.
The body is a highly actionable, well-sequenced workflow with strong validation checkpoints and feedback loops, anchored in concrete copy-paste commands. Its main weaknesses are repetition across sections that hurts conciseness and dense inlined command detail that belongs in separated reference files.
Suggestions
Consolidate the escalation/质变信号 rules into the single 升级判定 section and reference it from Step 3 and 连续执行模式 instead of restating, to reduce repetition and tighten conciseness.
Extract the dense Step 0 `comet task` / `comet memory` flag catalog into a dedicated reference file (e.g. `references/comet-task.md`) and link to it, improving progressive disclosure and token efficiency.
Provide a local bundle pointer or short fallback for the `comet-classic/reference/*.md` dependencies so the skill remains navigable when comet-classic is not co-located.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and largely avoids explaining concepts Claude already knows, but it restates the same material multiple times — the escalation signals appear in Step 3, the 升级判定 section, and 连续执行模式, and the open→build→根因→verify→archive chain is repeated — so it could be noticeably tightened. It sits above the padded anchor 2 but below the trim anchor 4. | 3 / 5 |
Actionability | Provides copy-paste-ready, concrete commands throughout (e.g. `comet state init <name> hotfix`, `comet guard <change-name> build --apply`, `comet task <project-root> --task ... --json`) plus named artifacts (proposal.md/design.md/tasks.md) covering the common workflow cases. It matches the "fully executable; copy-paste ready" anchor. | 5 / 5 |
Workflow Clarity | A clearly sequenced 6-step process with explicit validation checkpoints (`comet state check`, `comet guard ... --apply`, `comet state next` auto/manual, `verify_result: pass` required before archive), feedback loops (root-cause-elimination returns to Step 2, systematic-debugging on failures), and checklists (退出条件, tasks.md checkboxes). This matches the anchor-5 example with feedback loops and checklists. | 5 / 5 |
Progressive Disclosure | Sections are well-organized and references to `comet-classic/reference/*.md` are clearly signaled and one level deep, but no local bundle exists (references/, scripts/, assets/ absent) and dense inline blocks — notably the Step 0 `comet task` memory/context paragraph and the repeated escalation detail — read as content that should be split into separate files. This fits the "some structure but content that should be separate is inline" anchor better than the well-split anchor 4. | 3 / 5 |
Total | 16 / 20 Passed |