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 body is highly actionable with concrete code and commands, but it is markedly verbose and monolithic — reusing tables and fabricated example outputs — while its workflow lacks an explicit validate->fix->retry loop and its references are mislabeled.
Suggestions
Trim redundant content: collapse the per-section 'Best Practices' and 'Common Issues' blocks and remove fabricated 'Output Example' result summaries from the Common Patterns so each token earns its place.
Add an explicit validate->fix->retry feedback loop to the rendering workflow (e.g., validate config syntax, render, on failure diagnose and re-run) so workflow clarity can exceed the cap of 3.
Fix the References section to point to the real references/runtime_checklist.md instead of stating 'No reference files currently available', and move the Color Scheme Reference / Parameters / Troubleshooting material into separate reference files to reduce the inlined wall of text.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~1150-line body is noticeably verbose: capabilities are restated in tables after prose, repeated 'Best Practices'/'Common Issues' blocks appear for every section, and 'Common Patterns' include fabricated-looking output examples ('Key findings visible', 'Publication ready') that pad tokens without adding instruction; it falls below the mostly-efficient 3 anchor. | 2 / 5 |
Actionability | Most guidance is executable — concrete CLI commands ('python scripts/main.py --data ... --type variation'), parameter tables, and Python examples referencing real symbols (CircosConfig, CHROMOSOME_SIZES, COLOR_SCHEMES) — with minor gaps such as an unclosed code fence (line 44) and an inline-defined generate_and_render function that is not in scripts/main.py. | 4 / 5 |
Workflow Clarity | A sequenced Workflow exists and there are checkpoint commands (py_compile Quick Check, Audit-Ready Commands), but for the batch/rendering operation there is no explicit validate->fix->retry feedback loop, and the feedback_loops note caps workflow_clarity at 3 for such operations. | 3 / 5 |
Progressive Disclosure | The body is structured with headers, but bulk content (color references, parameter tables, troubleshooting) that belongs in separate files is inlined, references are not clearly signaled — the References section even states 'No reference files currently available' while references/runtime_checklist.md exists — so it is below the good-structure 4 anchor. | 3 / 5 |
Total | 12 / 20 Passed |