Content
71%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-organized, token-efficient instruction-only skill with a clearly sequenced research workflow and explicit verification gates and boundaries. Its main weakness is actionability: guidance states what to extract and verify but not where to search or how to verify, leaving execution details to guesswork.
Suggestions
Name concrete scholarly sources in the tool routing or workflow (e.g., Crossref/OpenAlex APIs, PubMed, arXiv, Google Scholar) and map each to web_fetch or browser_use.
Add one example search-query formulation showing how to combine concepts, synonyms, and year filters.
Add a recovery rule to the completion gates, e.g. "If a DOI does not resolve, search the title on Crossref or the venue record before citing."
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — it never explains what a preprint, DOI, or peer review is — matching the 'efficient with minor trimmable instances' anchor. It falls short of 5 because the "Purpose" section ("Search, screen, synthesize, and cite scholarly literature and author metadata") verbatim repeats the frontmatter description and the copyright line is non-instructional boilerplate. | 4 / 5 |
Actionability | Concrete specifics exist ("Verify DOI, title, authors, venue, and year"; "Extract design, population, intervention or exposure, outcomes, limitations, and identifiers"; the tool routing table for web_fetch/browser_use), but key execution details are missing: no named portals or APIs (Crossref, OpenAlex, PubMed, arXiv), no example query formulations, and no method for verifying a citation. This matches the anchor for some concrete guidance that is incomplete. | 3 / 5 |
Workflow Clarity | The workflow is a clearly sequenced five-step process ("Translate the question into concepts, synonyms, exclusions, years, and study types" through "Synthesize agreements, conflicts, gaps, and confidence") with a "Completion gates" verification section — matching the anchor for a clear sequence with most checkpoints present. It is not 5 because there is no error-recovery loop (e.g., what to do when a DOI fails to resolve or records conflict). | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines, needs no external references (none exist in references/, scripts/, or assets/ and none are dangled), and is organized into clear sections (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery). This meets the simple-skill exception: well-organized sections alone earn a 5. | 5 / 5 |
Total | 16 / 20 Passed |