Content
71%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 well-structured with excellent progressive disclosure via verified reference files and a prescriptive output structure, but it is held back by structural redundancy across its overview-style sections and the absence of a worked example and explicit self-review loop.
Suggestions
Consolidate the overlapping enumerations in Core Function, Workflow Standard, Mandatory Output Structure, and Quality Standard so each design dimension is defined once and cross-referenced, reducing token redundancy.
Add one short worked example (e.g. a skeleton blueprint for the GLP-1RA/kidney-outcome trigger) showing the expected A–L output to make the guidance copy-paste concrete.
Add an explicit self-review step at the end of the Workflow Standard (validate output against the Hard Rules and section completeness, fix gaps, re-check) to close the feedback-loop gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body avoids explaining concepts Claude already knows, but the core design dimensions (time zero, exposure, confounding, censoring, target-trial emulation) are restated across Core Function, Workflow Standard, Mandatory Output Structure, Hard Rules, and Quality Standard, producing noticeable redundancy that could be tightened. | 3 / 5 |
Actionability | Guidance is concrete and prescriptive — a fixed A–L section structure, a redirect-and-stop template, and ten numbered hard rules — but a worked example of a completed blueprint output is missing, leaving a minor gap below the fully-copy-paste-ready anchor. | 4 / 5 |
Workflow Clarity | A clear 10-step Workflow Standard is present with checkpoints (out-of-scope redirect-and-stop, the 'incomplete if reference module not used' completeness gate, bias-review section), but there is no explicit self-review/fix-retry feedback loop, so it sits just below the top anchor. | 4 / 5 |
Progressive Disclosure | A dedicated Reference Module Integration section maps each of nine real, one-level-deep reference files to a specific output section, with all referenced paths verified to exist, giving clear overview-with-signaled-references navigation. | 5 / 5 |
Total | 16 / 20 Passed |