Content
93%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 tight, expert-level reference: executable commands, exact CSV/output contracts, and a rare set of operational gotchas (silent precompute, YAML-overrides-CLI, prefix-matched flag) that Claude could not discover without burning runs. The only gap is a missing post-run verification step for batch runs, which leaves workflow clarity just short of the top anchor.
Suggestions
Add a short post-run verification step for batch runs, e.g. 'after a batch, check every complex_name has a rank1.sdf under --out_dir before comparing ligands — rows with a bad ligand_description fail silently.'
State how to obtain $DIFFDOCK_REPO (clone github.com/gcorso/DiffDock) and where default_inference_args.yaml lives, so the first command is runnable without inference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~70-line body is lean and every non-obvious fact earns its place — the YAML-overwrites-CLI gotcha ("replaces every key it finds, so passing --samples_per_complex 40... is silently ignored"), the silent ~11-minute SO(3) precompute with its 32 GB RAM requirement, and the --ligand prefix-matching trap. No concepts Claude already knows are re-explained. Matches the 'every token earns its place' anchor. | 5 / 5 |
Actionability | The main invocation is copy-paste ready with real flags (python3 -m inference --config default_inference_args.yaml --protein_path target.pdb --ligand_description "COc1ccc(C#N)cc1"), the batch path specifies the exact four CSV columns, the output convention (rank{N}_confidence{score}.sdf) is documented, and the error table gives concrete fixes (sed the setrlimit constant to min(64000, rlimit[1])). Matches the fully-executable top anchor. | 5 / 5 |
Workflow Clarity | The single-complex path is unambiguous and the "Errors worth recognizing" table provides explicit error-to-fix recovery loops, but there is no post-run verification checkpoint for the batch/fragment-library path (e.g., confirm each complex produced a rank1.sdf before comparing ligands). This sits between 'most checkpoints present' (4) and 'explicit validation steps with feedback loops' (5). | 4 / 5 |
Progressive Disclosure | The body keeps the single-complex path inline and correctly splits batch docking and the ESMFold sequence-only path into references/workflows.md (a real file, one level deep, clearly signaled in context: "that path and a larger-library screening recipe are in references/workflows.md"). Structure is well organized with earned section headings; matches the top anchor. | 5 / 5 |
Total | 19 / 20 Passed |