Content
85%Reviews 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, well-structured owner/contract router with clear sequencing, explicit validation checkpoints, and clean one-level-deep reference disclosure. Its only gap is the absence of executable code or commands for the build/transaction steps, keeping actionability at the mid anchor.
Suggestions
Add one or two concrete, copy-paste-ready commands or code snippets for the most common build/transaction steps (e.g., the focused test invocation pattern or the exact rg search seeds) to lift actionability to the top anchor.
In the Owner Router 'Load' column, pair each reference with a single concrete entry command or search seed so routing jumps straight to executable action rather than a doc to read.
Optionally include a minimal 'identify the stable owner' checklist snippet (e.g., the exact rg flags or file glob) so the 'smallest stable owner' step is reproducible rather than descriptive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — owner-router tables, terse contracts, and hard-stop bullets each earn their tokens without restating what a DeFi protocol or staking is. No padding or concept explanation detected. | 3 / 3 |
Actionability | Guidance is concrete at the routing level (e.g., 'Find the closest current implementation with `rg`', owner-table start points) but contains no executable code or copy-paste commands for the actual build/transaction steps, which the top anchor expects. | 2 / 3 |
Workflow Clarity | The numbered 'Working Loop' sequences observe → locate → edit → test with an explicit feedback checkpoint ('If the fix fails, revisit the owner and contract'), and 'Done When' provides terminal validation criteria for the destructive/batch-style contract operations. | 3 / 3 |
Progressive Disclosure | Clear overview with well-signaled one-level-deep references — an Owner Router table and a Reference Routing section both link the five real files in references/, each annotated with scope; no nested reference chains. | 3 / 3 |
Total | 11 / 12 Passed |