Content
88%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.
A lean, well-sequenced validation workflow with genuine feedback loops, explicit pass criteria, and a properly disclosed one-level reference to a real, detailed checklist. The weaknesses are localized: the step-4 validator script path is unresolvable within this bundle and no command invocation is shown for it.
Suggestions
Resolve the step-4 dependency: either bundle the validator (e.g. as scripts/validate_package.py with an invocation example like 'python scripts/validate_package.py deck.pptx -o report.json') or state where it lives and how to locate it.
Note in step 4 or the artifacts section what to do when the validator is unavailable for non-production decks, so the workflow degrades explicitly rather than silently.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 24-line body is lean and dense: 'Treat deterministic failures as repair work, not exceptions' and the one-line pass criteria earn their tokens, with zero explanation of concepts Claude already knows (no 'what is OOXML' padding). This matches anchor 5 ('lean and efficient; assumes Claude's competence; every token earns its place') and exceeds anchor 4, which requires trimming some over-explanation — there is none to trim. | 5 / 5 |
Actionability | Most guidance is concrete and executable: apply the real 'references/audit-checklist.md' (verified to exist and to contain concrete checks like the overlap predicate and OOXML validation), compare slide count/bounds/hidden slides, and check named accessibility items. It sits between anchors 3 and 4: below 5 because step 4's 'pptx-reference-deck-analysis/scripts/validate_package.py' path does not exist in this bundle and no invocation syntax is given, but noticeably above 3 since six of seven steps are fully actionable with a resolvable reference. | 4 / 5 |
Workflow Clarity | The 7-step workflow has an explicit sequence, validation checkpoints (steps 2–6 audit geometry, actual bounds, accessibility, and package integrity), an explicit feedback loop ('Repair the spec or task-local builder, rebuild, and rerun the same checks'), a checklist for the complex process, and a separate pass-criteria section. This matches anchor 5 exactly, including the required validate→fix→retry loop for XML/document manipulation. | 5 / 5 |
Progressive Disclosure | The body is a short overview with a well-signaled, one-level-deep reference ('See references/audit-checklist.md for the complete checklist') that resolves to a real file — close to anchor 5. It drops to 4 because 'pptx-reference-deck-analysis/scripts/validate_package.py' points outside the bundle and does not resolve, leaving a navigation gap; anchor 5 requires all referenced content appropriately split and easy to navigate. | 4 / 5 |
Total | 18 / 20 Passed |