Content
82%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, highly actionable instruction-only skill body that names exact tools, parameters, and accepted values with clear sequencing and a preflight validation step. It is dense in places and could trim redundancy and consider splitting the tool catalog.
Suggestions
In Step 0, state the 'do not run tool names in a terminal / do not self-install the server' rule once instead of repeating it in both the intro paragraph and the bold note.
Consider moving the per-tool catalog in Step 1 (resolveIdentifier/verifyCitation/auditBibliography etc.) into a references file linked from SKILL.md, keeping only the decision table inline to lighten the overview.
Tighten the verifyCitation rationale (the 'Topaz et al., Lancet 2026' sentence) to a one-line justification so the fabrication-pattern note stays concise.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and information-dense about tool specifics without explaining concepts Claude already knows, but Step 0 repeats the 'do not run tool names in a terminal' guidance twice and a few passages (e.g. the verifyCitation fabrication rationale) could be trimmed — matching the 'minor over-explanation' score-4 anchor rather than the lean score-5 anchor. | 4 / 5 |
Actionability | Gives fully concrete, executable guidance: exact tool names, parameter names (text, id, style, format, title, doi...), accepted values (vancouver/ama/apa/ieee/cse; bib/ris/csl/endnote-xml...), and batch rules (max 25 per call, single id for retraction/OA) — the instruction-only equivalent of copy-paste-ready guidance. | 5 / 5 |
Workflow Clarity | Steps 0–5 are clearly sequenced with an explicit Step 0 validation/stop checkpoint ('If these tools are not in your available toolset ... say so plainly and stop') and batch-failure handling for auditBibliography, but there is no validate→fix→retry feedback loop, which sits just below the score-5 anchor. | 4 / 5 |
Progressive Disclosure | No bundle files exist and the single-file body is well organized into clear, navigable sections (When to Use, How to Use, Guidelines, When NOT to Use) with no nested references; the dense Step 1 tool catalog keeps it at good-but-could-split rather than the cleanly-partitioned score-5 anchor. | 4 / 5 |
Total | 17 / 20 Passed |