Content
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, domain-rich skill with an excellent phased workflow, decision matrices, and edge-case handling. Its main weaknesses are mild verbosity from background explanation and a tangential IDR section, a lack of executable call examples for the core EM tools, and no progressive disclosure to bundle files.
Suggestions
Add at least one executable `tu.run_tool(...)` example for each core EM phase (EMDB, PDB, EMPIAR, CryoET, AlphaFold) so the main pipeline is copy-paste ready, not just the IDR aside.
Trim background Claude already knows (the TEM/Cryo-EM/SEM modality primer) and consolidate the resolution-band tables into one reference to remove repetition.
Move the detailed per-phase tool input/output specs and the IDR resource section into separate reference files (e.g., TOOLS.md, IDR.md) and link to them from SKILL.md for proper progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The core tool specs and workflows are efficient and domain-specific, but the body pads in background Claude already knows ('TEM resolves individual protein complexes (~2nm). Cryo-EM achieves near-atomic resolution (<4Å)... SEM shows surface topology.'), repeats resolution bands across three sections, and devotes a long inline aside to the tangential IDR resource. | 2 / 3 |
Actionability | Each phase names concrete tools with exact input parameters and output fields, and a runnable `tu.run_tool("IDR_search_studies", {...})` example appears — but the six core EM phases give only prose input/output specs with no executable call examples, leaving the main pipeline not copy-paste ready. | 2 / 3 |
Workflow Clarity | A clear 8-phase sequence with an overview diagram and per-phase numbered steps, plus a quality-assessment checklist, fitting-quality indicators, and edge-case fallbacks (e.g., no EMDB entries → PDB method filter) that serve as error recovery; the read-only nature means the destructive-operation cap does not apply. | 3 / 3 |
Progressive Disclosure | Internally well-organized with clear headers and tables, but it is a single ~290-line monolithic file with no bundle files or one-level-deep references; content such as the detailed per-phase tool specs and the lengthy IDR aside could be split into separate reference files. | 2 / 3 |
Total | 9 / 12 Passed |