Content
58%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 strong on actionability with concrete, executable code across the major workflows and well-organized one-level-deep references, but it is weighed down by generic templated boilerplate and lacks validation checkpoints around its batch operations.
Suggestions
Remove or collapse the generic boilerplate sections (When to Use, Implementation Details, Output Contract, Validation and Safety Rules, Failure Handling, Quick Validation, Required Inputs) that restate process truisms and duplicate the description, keeping only domain-specific guidance.
Add explicit validation/verification checkpoints to the batch-operation and virtual-screening patterns (e.g., check every workflow status, retry failures, report incomplete results) so the batch workflow has a clear feedback loop.
Trim the inlined full code examples and Common Patterns into the reference files, leaving a lean overview in SKILL.md that points to them, to reduce token cost while preserving actionability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The technical sections (code examples, methods, references) are efficient, but the body carries substantial generic boilerplate—'When to Use', 'Implementation Details', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling', 'Quick Validation'—that states process truisms Claude already knows and re-states the description verbatim in 'Key Features'. | 3 / 5 |
Actionability | Provides multiple concrete, largely copy-paste-ready code blocks (pKa, conformer search, optimization, docking, cofolding, RDKit-native, batch ops, error handling), with only minor gaps such as a missing stjames import in the docking block and placeholder variables (mol1, compound_library, [x, y, z]). | 4 / 5 |
Workflow Clarity | The submit → wait_for_result → fetch_latest → access pattern is clearly sequenced with status checking, but the batch operations (batch_submit_workflow, virtual screening) lack explicit validation/verification checkpoints, which caps workflow clarity per the batch-operation rule. | 3 / 5 |
Progressive Disclosure | Six reference files exist and are clearly signaled one level deep with one-line descriptions in the 'Reference Documentation' section, and content is appropriately split; however the body itself inlines a large volume of full workflow examples and generic sections rather than trimming to a lean overview. | 4 / 5 |
Total | 14 / 20 Passed |