Content
63%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, actionable phased workflow with concrete tool signatures and useful domain thresholds. Its main weaknesses are repeated/educational content that inflates length and a monolithic single-file layout that underuses progressive disclosure for a skill of this size.
Suggestions
Remove the restated-description opening paragraph and the 'EM resolution determines what you see' background aside; consolidate the duplicated resolution ranges into one canonical table referenced from both Phase 1 and Phase 6.
Move the per-phase tool input/output specifications and the IDR 'Related Resource' section into separate reference files (e.g. references/tools.md, references/idr.md) and link to them one level deep from the body.
Add one copy-paste tu.run_tool(...) example per phase (not just IDR) so the actionability reaches fully executable coverage across all seven phases.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and domain-specific, but contains removable padding: the opening paragraph restates the description, 'EM resolution determines what you see' explains background Claude already knows, and resolution ranges appear twice (Phase 1 interpretation table and the Phase 6 decision matrix). | 3 / 5 |
Actionability | Each tool is listed with concrete input/output signatures and one full invocation example (tu.run_tool('IDR_search_studies', {...})); numeric thresholds (>0.7 cross-correlation, pLDDT<70, FSC 0.143) make guidance executable, though most phases describe I/O rather than showing copy-paste calls. | 4 / 5 |
Workflow Clarity | A clearly sequenced 7-phase pipeline (Phase 0–7) with a diagram, per-phase numbered steps, a decision matrix, a quality-assessment checklist, and an Edge Cases & Fallbacks section; no error-recovery feedback loop is present, but the operations are read-only so the destructive/batch validation cap does not apply. | 4 / 5 |
Progressive Disclosure | Well-organized with clear headers, tables, and a workflow diagram, but it is a single ~295-line monolithic file with no bundle/reference files; per-tool I/O specs and the IDR 'Related Resource' section are API-reference-style content that could be split into one-level-deep reference files. | 3 / 5 |
Total | 14 / 20 Passed |