Content
66%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-structured, largely actionable workflow with a clear 11-phase pipeline and transparent scoring. Its main weakness is progressive disclosure: four referenced bundle files are cited but do not exist, so the navigation signals point to missing material.
Suggestions
Create the four referenced bundle files (INPUT_REFERENCE.md, SCORING_TABLES.md, REPORT_TEMPLATE.md, TOOLS_REFERENCE.md) under references/ so the signaled detail is actually reachable, or inline the essential content and remove the links.
Trim the 'Reasoning Before Searching' biological explanations (e.g., the neoantigen/T-cell paragraph) to thresholds and rules only, since Claude already knows the underlying biology.
Add an explicit validation checkpoint after each phase (e.g., 'Verify all required biomarker scores are populated before Phase 10 integration') to convert the report-first principle into concrete feedback loops.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and largely actionable with minimal padding, though the 'Reasoning Before Searching' section re-explains biology Claude already knows (e.g., 'More somatic mutations produce more neoantigens, which are recognized by T cells') and could be trimmed. | 4 / 5 |
Actionability | Concrete tool calls with named parameters and a transparent scoring formula (TMB 5-30, MSI 5-25, penalties STK11 -10) are provided throughout, with only minor gaps such as the neoantigen estimate being a rough heuristic rather than validated code. | 4 / 5 |
Workflow Clarity | The 11-phase workflow is clearly sequenced with per-phase numbered steps and explicit 'LOOK UP DON'T GUESS' verification guidance, but the phases lack explicit validation checkpoints confirming each phase's output before proceeding and the report-first loop is stated as a principle rather than wired into the sequence. | 4 / 5 |
Progressive Disclosure | The body references INPUT_REFERENCE.md, SCORING_TABLES.md, REPORT_TEMPLATE.md, and TOOLS_REFERENCE.md, but none of these files exist in references/, scripts/, or assets/ — the references are dangling and the promised detail is unreachable, leaving a structured-looking but effectively broken disclosure hierarchy. | 2 / 5 |
Total | 14 / 20 Passed |