Content
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable skill body with clear end-to-end simulation and analysis workflows, weakened by verbosity and an orphaned reference file that is never linked from the main content.
Suggestions
Link references/mdanalysis_analysis.md from the body (e.g., a '## Advanced Analysis' section pointing to it) and move the inline contact/PCA/FES detail there to slim the main file.
Add explicit validation gates between stages, e.g. 'Confirm minimized energy is stable before starting NVT' and 'Verify NVT temperature has equilibrated before NPT'.
Trim repeated import blocks and lengthy docstrings, and remove the generic overview sentence defining molecular dynamics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient executable code, but padded with verbose docstrings, repeated `from openmm.app import *` import blocks, and an overview explaining what MD is — concepts Claude already knows; it could be tightened. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready code for system prep, minimization, NVT/NPT, and RMSD/RMSF/contact analysis, plus a force-field selection table and parameterization snippet. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered (System Preparation → Minimization → NVT → NPT → Analysis) with energy logging and checkpoints, but there are no explicit 'proceed only when X' validation gates, so checkpoints remain implicit. | 2 / 3 |
Progressive Disclosure | Sections are well-organized and a reference file (references/mdanalysis_analysis.md) exists, but the body never links to it and inlines analysis code that could live in the reference, so the bundle structure is underused and references are not signaled. | 2 / 3 |
Total | 9 / 12 Passed |