Content
50%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 highly actionable with concrete publish/filter/image commands and a sensible generate-then-publish flow, but it is padded with significant repetition, lacks validation/error-recovery loops for outward-facing publishing, and leaves half its reference bundle unlinked. Tightening duplication and wiring up the orphaned references would substantially improve it.
Suggestions
Remove duplicated blocks — keep 排版规范/颜色规范 in html-layout-guide.md only and reference it once; delete the redundant 默认模式 section and the second 推送后操作 block.
Add an explicit validation/feedback loop for publishing: check the returned draft ID, handle non-success responses, and retry or surface the error before declaring success.
Link the four orphaned reference files (bilibili/wechat/xiaohongshu api-guides, content-template) from the relevant script sections so the full bundle is navigable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Noticeably verbose with repeated sections: 排版规范/颜色规范/局部划线 appears in 阶段一 3.5, again in 注意事项→排版规范, and again in 默认模式; the 默认模式 block rehashes 阶段一; 推送后操作 and the publish commands are duplicated; this is padding rather than concept-explanation, so it lands at 2 rather than 1. | 2 / 5 |
Actionability | Provides mostly executable, copy-paste-ready commands ('python scripts/publish_wechat.py --mode custom_api --title ... --content ... --cover ... --tags ...'), a concrete JSON file format, and specific filter/image-search invocations; held at 4 because some steps are delegated vaguely to '智能体根据...生成' without a script call and error/return-value handling is unspecified. | 4 / 5 |
Workflow Clarity | A clear two-phase sequence exists (生成→预览调整→一键推送) with a human-confirm checkpoint and draft-box safety, but publishing to external platforms is an outward-facing/batch operation and the workflow lacks an explicit validate/recover loop (no 'verify returned draft ID', no error-handling/retry), so per the batch-operation cap it cannot exceed 3. | 3 / 5 |
Progressive Disclosure | Some structure with one-level-deep, well-signaled references (viral-content-templates.md, html-layout-guide.md, sources-config.md each get a '何时读取' note), but 4 of 7 reference files (bilibili-api-guide.md, wechat-api-guide.md, xiaohongshu-api-guide.md, content-template.md) are never linked from the body, and HTML排版规范 is inlined despite a dedicated reference file existing. | 3 / 5 |
Total | 12 / 20 Passed |