Content
75%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 well-engineered overview: routing, safety rules, freshness policy, and invariants are all imperative and specific, with details correctly pushed to reference files. The main defects are a dangling reference to a missing templates/starter-kit/README.md path, some over-packed multi-clause sentences, and the absence of any inline executable snippet to anchor the code-form rules.
Suggestions
Fix the progressive_disclosure gap: the routing table points to templates/starter-kit/README.md, which is absent from the bundle — either add the templates/starter-kit/ files or re-route starter-kit requests to an existing reference until they are added.
Improve actionability by inlining one short canonical example of the rule-5 getter (the exact `returns (int256 price, uint8 decimals)` named-return form with the tuple destructuring) so the most-quoted code shape is verifiable without loading a reference file.
Tighten conciseness by splitting the longest compound rules (the starter-kit table row and the SVR configuration rule) into short bullet clauses; they currently pack 5+ requirements into single sentences.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean — a dense routing table, imperative safety rules, and policies with no explanations of concepts Claude already knows. It falls short of the top anchor because several over-packed sentences (the starter-kit table row, the SVR configuration rule, and the live-feed-address invariant) mix many clauses and could be trimmed or split. | 4 / 5 |
Actionability | Guidance is concrete and executable: exact interface selection per case ('IBundleAggregatorProxy' for MVR, 'AggregatorV2V3Interface' for sequencer uptime), an exact named-return signature with tuple destructuring, an exact standalone sentence to emit, and a 3600-second grace period. It misses the top anchor because all executable code lives in reference files and no inline snippet anchors the tuple-form rule. | 4 / 5 |
Workflow Clarity | The freshness policy is a clearly numbered escalation sequence with an explicit unverified fallback ('If unverified, say so and name the URL'), and the safety rules act as checkpoints. It lacks the explicit validate-then-fix feedback loops of the top anchor, though no destructive/batch cap applies. | 4 / 5 |
Progressive Disclosure | The trigger-to-file table clearly signals one-level-deep references, and all seven referenced files exist in the bundle. The gap is that 'templates/starter-kit/README.md' — the routing target for an entire request category — does not exist in the bundle, so that route cannot resolve. | 4 / 5 |
Total | 16 / 20 Passed |