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.
The body is highly actionable with executable CLI syntax and realistic examples for every subcommand, and it stays lean by assuming Claude's competence. The main improvements are adding an error-recovery step to the workflow and trimming or externalizing the dense MCP-tool and wos/scopus behavioral detail.
Suggestions
Add an explicit error-recovery step to the Workflow section (e.g., 'if download or read fails, retry with an alternate source or -s unpaywall') to close the workflow validation gap.
Trim the MCP-tool behavioral prose (exit-code semantics, --list configuration notes, MCP result semantics) to the essentials needed to run commands, or move it next to the tool examples as a compact table.
If the skill grows further, move the full source list and the wos/scopus option details into a reference file so SKILL.md remains a lean overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and operational with no re-teaching of concepts Claude already knows, but minor behavioral caveats ('exit code 1... exits with code 2', '--list shows only tools enabled by the current configuration') and the wos/scopus detail could be trimmed or condensed. | 4 / 5 |
Actionability | Copy-paste-ready commands with real arguments throughout, e.g. 'paper-search tool search_crossref "transformer attention" --filter from-pub-date:2024-01-01 --sort published --order desc --max-results 2' and 'paper-search tool get_crossref_paper_by_doi 10.1038/nature12373', covering search, download, read, sources, and tool subcommands. | 5 / 5 |
Workflow Clarity | The '## Workflow' section gives a clear 4-step sequence (search, present table, read, download and report path), but there is no explicit validation or error-recovery checkpoint such as what to do when a download or source fails, leaving minor validation gaps per the anchor-4 description. | 4 / 5 |
Progressive Disclosure | A single-file skill with well-organized section headers and no dead references (no bundle files exist); reference-grade detail like the full source list, wos/scopus options, and MCP tool behavioral notes sits inline rather than in a separate file, which is acceptable at ~95 lines but keeps it below the anchor-5 clear-overview pattern. | 4 / 5 |
Total | 17 / 20 Passed |