Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured instruction skill with a clear sequenced workflow, explicit validation/checklist steps, and exemplary progressive disclosure via real one-level-deep references. The main weakness is conciseness: the writing-philosophy section duplicates guidance already present in the workflow.
Suggestions
Collapse or prune the '写作哲学：像人类专家一样写' section: its two-stage mode, narrative-validation, innovation-persuasion, and annual-plan-progression points already appear in workflow steps 3–5 — keep only what adds new information.
Move the '专家写作的核心特征' bullet list into a reference file (e.g. anti_patterns.md or a new writing_style.md) and link it, leaving the body as a lean overview.
The '一个判断标准' peer-review heuristic is valuable but discursive; consider condensing it to one line or folding it into the DoD checklist reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient domain-specific guidance (no generic concept explanations), but the '写作哲学：像人类专家一样写' section restates the two-stage mode, narrative-driven validation, innovation persuasion, and annual-plan progression already covered in the workflow steps, so it could be tightened. | 2 / 3 |
Actionability | Concrete and specific for an instruction skill: three named output files, an explicit forbidden-edit list, page/word budgets (12–15 pages, 12000–15000 字), framework options, a numbering-purge rule, and copy-paste-ready skeleton/example references. | 3 / 3 |
Workflow Clarity | A clearly numbered 7-step '工作流（按顺序执行）' with an explicit consistency-validation step (6), output purification, a referenced DoD checklist, and feedback prompts (ask when info incomplete; prompt when target files missing). | 3 / 3 |
Progressive Disclosure | Overview body points to 10 well-labeled, one-level-deep reference files (写作小抄 section) plus contextually-linked info_form and dod_checklist; all referenced paths resolve to real files in ./references/, with content appropriately split and easy to navigate. | 3 / 3 |
Total | 11 / 12 Passed |