Content
85%Reviews 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 MCP tool-routing skill with a clear stepped workflow and explicit validation/error-handling checkpoints. Its only real weakness is mild verbosity from repeated warnings and a decorative citation that could be trimmed for token efficiency.
Suggestions
Deduplicate the 'don't run tool names as shell commands' guidance — state it once in Step 0 and reference it rather than repeating near-verbatim in the same section.
Consolidate the 'single identifier per call' notes for checkRetraction/checkOpenAccess/verifyCitation into one place instead of restating across Steps 1 and 3.
Drop the illustrative '(Topaz et al., Lancet 2026)' study citation from the verifyCitation bullet; the fabrication pattern is already described concretely without it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is information-dense and mostly assumes Claude's competence, but repeats guidance — 'Do not try to run the tool names in a terminal' / 'do not try to invoke the tool names as shell commands' appears twice in Step 0, 'single identifier per call' recurs across Steps 1 and 3 — and includes a non-essential flourish citation ('Topaz et al., Lancet 2026'), so it could be tightened. | 2 / 3 |
Actionability | Concrete, executable routing guidance throughout: named tools, their parameters ('text', 'id', 'style', 'format'), accepted values (five builtins plus CSL IDs; bib/ris/csl/endnote-xml/...), and an explicit chaining recipe (resolveIdentifier → formatCitation → exportCitation) — copy-paste ready for an MCP-routing skill. | 3 / 3 |
Workflow Clarity | Clear sequenced Steps 0–5 with an explicit validation checkpoint in Step 0 ('If these tools are not in your available toolset, the server is not connected — say so plainly and stop') and error-handling guidance (a failing entry becomes status:'error' without failing the batch), matching the 'clear sequence with explicit validation' anchor. | 3 / 3 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ absent) and none are needed; the skill is a single self-contained file with well-organized sections (When to Use, How to Use Steps 0–5, Guidelines, When NOT to Use), which satisfies the simple-skill allowance for scoring 3 on well-organized structure without external references. | 3 / 3 |
Total | 11 / 12 Passed |