Content
50%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 content is highly actionable with concrete commands and a thorough case structure, but it is weighed down by verbose generic boilerplate, weak workflow validation tied to the actual operation, and a broken plus several orphaned references.
Suggestions
Remove or merge the generic boilerplate sections (Lifecycle Status, Evaluation Criteria, Response Template, Output Requirements, Audit-Ready Commands) to reduce padding and respect token budget.
Fix the broken 'references/conditions/' reference (create the directory or remove the line) and add references for the existing orphaned bundle files (guidelines.md, sample_input.json, sample_output.json).
Replace the generic Workflow with concrete checkpoints specific to case generation (e.g., validate topic/step inputs against topics.json, run py_compile, verify output against case structure).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is padded with large generic boilerplate sections (Output Requirements, Response Template, Input Validation, Error Handling, Lifecycle Status, Evaluation Criteria, Audit-Ready Commands duplicating Quick Check) that are not USMLE-specific and add little Claude does not already know. | 2 / 5 |
Actionability | Provides concrete, copy-paste-ready commands ('python scripts/main.py --step 1 --topic cardiology --difficulty medium'), a full parameters table, a 15-point case structure, and an example output, with only minor gaps. | 4 / 5 |
Workflow Clarity | A sequenced Workflow with validation/fallback steps exists, but it is generic process boilerplate rather than concrete checkpoints tied to the case-generation operation, leaving validation implicit. | 3 / 5 |
Progressive Disclosure | Section structure is reasonable and references are one-level-deep in a dedicated References section, but the referenced 'references/conditions/' path does not exist, several bundle files (guidelines.md, sample_input/output.json, requirements.txt) are never referenced, and 'See ## Features above' style pointers are awkward. | 3 / 5 |
Total | 12 / 20 Passed |