Content
57%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 delivers unusually concrete output discipline — exact headings, commands, file template, and length budget — supported by well-chosen examples. Its two real defects are the missing 'Workflows/FindStructure.md' file behind the routing table and the absence of an explicit ordered workflow, plus meaningful repetition of the wind-tunnel rules across three sections.
Suggestions
Fix the Workflow Routing table: either ship 'Workflows/FindStructure.md' in the bundle or remove the routing section, since following it currently leads to a missing file.
Add one short numbered sequence (输入 → 找母题 → 结构卡 → 内部风洞 → 结论 → 落盘) early in the body so the pipeline does not have to be reconstructed from the Gotchas and Examples.
De-duplicate the wind-tunnel/conclusion rules: state them once in '风洞如何进入结论' and trim the overlapping Gotchas items (e.g. the repeated '结论不是全文摘要' / '具体试压与抽象规则必须递进' pair).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and rule-per-line with no padding or explanation of known concepts, but the wind-tunnel-to-conclusion rule is stated three times (理解契约 section, Gotchas items on 风洞/结论, and again in 输出要求) and several Gotchas restate 理解契约 points. Fits 'mostly efficient but could be tightened' rather than the noticeably-verbose 2 anchor. | 3 / 5 |
Actionability | Concrete, executable guidance throughout: exact commands ('date +%Y%m%dT%H%M%S', 'date "+%Y-%m-%d %a %H:%M"'), a copy-paste file path template, a full markdown skeleton with required frontmatter, strict heading and ASCII-connector rules, and three worked examples. Not 5 because the core analytical moves (how to actually locate the 母题, how to lay out the relation graph) remain conceptual. | 4 / 5 |
Workflow Clarity | The pipeline (输入 → 母题 → 结构卡 → 内部风洞 → 结论 → 落盘) is never presented as an explicit ordered sequence; it must be synthesized from 理解契约, Gotchas, 输出要求, and the Examples. One validation checkpoint exists ('保存后读回文件并报告路径'), but the sole workflow reference 'Workflows/FindStructure.md' does not exist in the bundle. Non-destructive skill, so the batch cap does not apply; fits 'sequence present but implicit'. | 3 / 5 |
Progressive Disclosure | The body's only external reference — 'Workflows/FindStructure.md' in the Workflow Routing table — is a dangling pointer (no references/, scripts/, assets/, or Workflows/ directory exists in the bundle). Internal sections are well organized, but a broken sole reference is more than the 'minor organization gaps' of the 4 anchor, landing at 'references present but not clearly (or validly) signaled'. | 3 / 5 |
Total | 13 / 20 Passed |