Content
72%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 an exemplary token-efficient router: no padding, real one-level-deep references, and strong conditional-loading discipline. Its weaknesses are compressed, sometimes grammatically broken instruction bullets that hurt actionability, and the absence of an explicit workflow sequence with validation checkpoints for edit and delivery operations.
Suggestions
Repair and clarify the compressed bullets — e.g. rewrite "Initial/full authoring plans needs before layout" and the asset-work bullet so each is an unambiguous instruction a reader can execute without interpretation.
Add a short ordered workflow (read source/tokens → plan → edit → validate/preview → deliver) with explicit checkpoints, since edits and whole-deck batch previews are destructive/batch operations that currently lack a validation loop.
In the asset-work bullet, link the specific shared-guidelines.md media workflow section so the guidance is actionable rather than a jargon summary.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 19-line body is lean and dense with rules and routing instructions only — no padding, no explanations of concepts Claude already knows, and every line carries a constraint or a pointer. | 5 / 5 |
Actionability | The task-mapped reading list with real markdown links to references/slides-ppt.md, references/shared-guidelines.md, and references/layout.md is concrete, but bullets like "apply the shared media workflow, including live capabilities, authorized model selection, actual placement and plan/check outcomes" and the garbled "Initial/full authoring plans needs before layout" are too compressed or ambiguous to act on without guessing. | 3 / 5 |
Workflow Clarity | Content is organized by task type rather than as a sequence, and verification is only implicit ("plan/check outcomes", "the PPT acceptance section", "check editor/export behavior when affected") — there is no explicit edit→validate→deliver order with checkpoints, and batch preview/acceptance steps lack a feedback loop. | 3 / 5 |
Progressive Disclosure | All three referenced files exist, are relevant, and are one level deep with clear markdown links; loading is task-conditioned ("Read Layout selection only when selecting or recomposing a layout", "Do not load layout catalogs or media guidance for unchanged assets") making navigation and conditional loading exemplary. | 5 / 5 |
Total | 16 / 20 Passed |