Content
71%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 lean, highly actionable dispatch document: exact spec paths, a copy-paste verification command, per-task reading branches, and an explicit re-read feedback loop for missing or truncated sources. Its main weaknesses are the unresolved script references (the bundle contains no scripts/ directory) and slight redundancy in the body-verification rules. Workflow ordering is discernible but requires the reader to interleave task-type and process bullets.
Suggestions
Ship the referenced scripts in the skill bundle (scripts/read-design-system.py, scripts/read-context.py) or rewrite the paths to wherever they actually resolve, so the navigation promises in the body are fulfillable.
Show one full example invocation of scripts/read-design-system.py (with typical arguments) matching the level of detail already given for the read-context.py check command.
Consolidate the body-integrity verification rules stated in both the 检查 bullet and the closing paragraph into a single location.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~20-line body is dense and imperative with no explanation of concepts Claude already knows (uses 'contractData', '受控状态' without elaboration), but the body-integrity verification rule is repeated across the 检查 bullet ('只读审查同样核对必需正文') and the closing paragraph ('核对正文送达…替代当前完整正文'), a minor redundancy that could be trimmed — anchor 4, not the fully lean anchor 5. | 4 / 5 |
Actionability | Gives exact paths ('.trellis/spec/frontend/index.md', 'web/src/index.css', 'web/tailwind.config.ts') and a copy-paste command ('python3 scripts/read-context.py check --source .trellis/spec/frontend/design-system.md'), but 'scripts/read-design-system.py' is named without a full invocation and how to read component contractData is left unspecified — concrete commands with minor gaps, fitting anchor 4. | 4 / 5 |
Workflow Clarity | A sequence is present ('先读…' then per-task reads, then '检查' with engineering checks and browser acceptance) with an explicit validation checkpoint (read-context.py check) and a feedback loop ('来源缺失、截断或变化时先补读'), but task-type bullets (主题/组件/页面) are interleaved with process bullets (读取/检查), so the reader must assemble the global order — anchor 4 rather than 5. | 4 / 5 |
Progressive Disclosure | The body is short and organized with a deliberate on-demand loading design ('按任务选择…逐页补齐'), but the referenced 'scripts/read-design-system.py' and 'scripts/read-context.py' do not exist in the skill bundle (no scripts/ directory present), and the detailed content lives in repo-external '.trellis/' paths rather than bundled references — structure exists but navigation does not fully resolve, fitting anchor 3. | 3 / 5 |
Total | 15 / 20 Passed |