Content
61%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 well-structured with highly actionable query syntax and API examples, and it models progressive disclosure better than most (consult-when sections, grep patterns, loading strategy). Weaknesses are verbosity in user-interface and support sections, workflows lacking validation checkpoints for batch API operations, and reference files that are signaled but not actually present in the bundle.
Suggestions
Trim or move to reference files the My NCBI/RSS/clipboard UI features, Support Resources (reversed email, phone number), and Limitations sections — they consume context without adding executable guidance.
Add validation checkpoints to the workflows: check the ESearch result count before fetching, verify HTTP status codes and XML/JSON parse success, and include a rate-limit backoff/retry loop in the API example rather than describing it as a best practice.
Ensure the three cited reference files (references/api_reference.md, references/search_syntax.md, references/common_queries.md) actually ship with the skill, since the body's navigation depends on them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Core sections (query syntax, MeSH, API access, workflows) are dense and concrete, but padding is scattered throughout: the overview explains what PubMed is, sections 7/9/Support/Limitations cover My NCBI UI features, clipboard limits, a reversed support email, and a phone number — content Claude doesn't need or that belongs in reference files. | 3 / 5 |
Actionability | Provides an executable ESearch/EFetch Python example with real URLs and parameters, copy-paste-ready query examples with field tags, endpoint names, rate limits, and the ECitMatch citation format. Minor gaps: the elink and batch-export examples are bare URL fragments rather than executable code, and no error-handling implementation is shown. | 4 / 5 |
Workflow Clarity | Five workflows present coherent numbered sequences, but none include validation checkpoints — 'Implement rate limiting and error handling' is a final step mention, not a verify/retry loop. Batch API operations without validation cap this dimension at 3 per the rubric. | 3 / 5 |
Progressive Disclosure | Excellent signaling: per-section 'When to consult X.md' guidance, grep patterns for discovery, one-level-deep references, and an explicit loading strategy. However, the three referenced files (api_reference.md, search_syntax.md, common_queries.md) are absent from the bundle, and sections 7, 9, Support, and Limitations inline content that belongs in those files. | 4 / 5 |
Total | 14 / 20 Passed |