Content
92%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 exemplar of a lean orchestrator overview: a mandatory staged lifecycle with built-in verification and reconciliation, bright-line safety invariants, and a well-organized one-level-deep reference bundle whose files all exist and carry the operational detail. The only notable gap is the absence of any concrete example invocation or command in the body itself.
Suggestions
Include one short concrete example in the body (e.g. a sample preflight check or outward verification probe) so the execution shape is visible before descending into references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~60-line body is dense and lean — a lifecycle list, an operations table, classification rules, and invariants with zero explanation of concepts Claude already knows; every rule earns its place. | 5 / 5 |
Actionability | Concrete policy rules ("Read-Only Mode Lock: `verify`, `monitor`, and `diagnose` cannot execute writes"), explicit acceptance criteria ("Root response, valid TLS, 404 on unknown path"), and read-conditions for each reference make the routing and gating actionable; however, no example invocations or commands appear in the body itself — all execution mechanics are delegated to the reference files. | 4 / 5 |
Workflow Clarity | Seven mandatory numbered stages include an explicit validation stage ("Independently Verify: Inspect outward system behavior from target origin, separate from mutation operator"), a reconcile-and-report stage, and a feedback rule ("reconcile actual resource state before re-attempting"), satisfying the checklist + feedback-loop pattern for destructive operations. | 5 / 5 |
Progressive Disclosure | The body is a clear overview and every cited bundle file exists (five core references plus providers/aws, gcp, cloudflare, vercel, and extension-contract.md), one level deep, each link annotated with its scope and a when-to-read condition ("Read the matching file before any provider operation"). | 5 / 5 |
Total | 19 / 20 Passed |