Content
57%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 orchestrator skill with a coherent seven-step PRISMA workflow and domain-specific tool selection, but it reads as a high-level plan rather than executable guidance: no commands or code, no validation checkpoints inside the workflow, and dependent sub-skills referenced without paths. The truncated checklist-mapping section promises detail it does not contain.
Suggestions
Add concrete, executable anchors: example database-specific search string patterns and the meta-analysis tool or code approach (e.g., a Python/R snippet for pooled estimates and forest plots), plus paths or invocation syntax for the literature-search, scienceclaw-ie, and paper-writing sub-skills.
Insert validation checkpoints between steps, e.g., reconcile PRISMA flow counts after deduplication, verify inter-rater kappa before full-text screening, and confirm heterogeneity assumptions before choosing fixed vs. random effects.
Either inline a compact step-to-checklist-item mapping or move the full 27-item PRISMA 2020 checklist mapping into a reference file (e.g., references/prisma-checklist.md) and link it from the Checklist Reference section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and directive without explaining concepts Claude already knows, but minor trims are possible: the PICO acronym expansion and the "PRISMA 2020 Checklist Reference" section, which promises a step-to-item mapping without delivering it, add tokens without actionable content. | 4 / 5 |
Actionability | The guidance names concrete domain tools and statistics ("RoB 2 for RCTs, ROBINS-I", "Cohen's kappa", "SMD, OR, RR, HR", "I-squared", "trim-and-fill") but includes no commands, code, or search-string templates, and the three sibling skills it depends on are referenced by name only with no paths or invocation details — concrete guidance that remains incomplete to execute. | 3 / 5 |
Workflow Clarity | Seven steps are clearly and logically sequenced from protocol registration through PRISMA reporting, and an input-validation guardrail exists, but there are no in-workflow checkpoints such as PRISMA count reconciliation after deduplication, kappa thresholds for screening agreement, or stop/verify rules before synthesis — validation is left implicit. | 3 / 5 |
Progressive Disclosure | Sections are well organized for a single-file skill, but no bundle files exist; the Integration Points reference sibling skills without links or paths, and the 27-item PRISMA checklist mapping is described but neither inlined nor moved to a reference file, so navigation and content placement could be substantially better. | 3 / 5 |
Total | 13 / 20 Passed |