Content
100%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is a well-structured, actionable procedure that respects token budget, sequences work with explicit validation and recovery loops, and cleanly offloads detail to verified one-level-deep references. It meets the top anchor on every dimension.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — it never explains what GraphQL or Guillotine is, and each step delivers only actionable specifics (exact field names, type-name transformation rules, validation checks) with no padding. | 3 / 3 |
Actionability | Guidance is concrete and specific — e.g. "Execute `node scripts/find-guillotine-targets.mjs .`", the exact descriptor→type-name rule with a worked example, and precise field requirements ("Each `QueryDSLInput` must contain exactly one expression field"); per the rubric's code-vs-instruction note, actionable instruction-only guidance is not penalized for lacking inline code. | 3 / 3 |
Workflow Clarity | Nine explicitly sequenced steps culminate in a dedicated validation checklist (Step 9) and a separate Error Handling section that provides fix-and-retry feedback loops (e.g. "simplify to `matchAll: {}` to confirm data exists, then re-add filters one at a time"). | 3 / 3 |
Progressive Disclosure | The body is an organized overview that signals one-level-deep references to real bundle files (references/guillotine-reference.md, compatibility.md, examples.md, troubleshooting.md, scripts/find-guillotine-targets.mjs, assets/guillotine-query.template.ts), all verified to exist, with no nested-reference chains. | 3 / 3 |
Total | 12 / 12 Passed |