Content
56%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 skill has a genuinely strong core workflow with executable R/Python commands and a defined output contract, but it is weighed down by heavy generic boilerplate and a serious accuracy problem: multiple validation and example sections reference the wrong packaged script (extract_criteria.py instead of the forest plot scripts).
Suggestions
Correct every reference to `scripts/extract_criteria.py` (Example Usage, Validation Shortcut, Quick Validation, Key Features) to point at `scripts/forest_binary.R` / `scripts/forest_binary.py`, the actual forest-plot entry points.
Remove the generic templated boilerplate sections (When to Use, Key Features, Implementation Details, Deterministic Output Rules, Completion Checklist, Required Inputs, Output Contract) that restate what Claude already knows; keep only the data format, workflow, dependencies, and failure-handling guidance.
Consolidate the three redundant validation sections (Validation Shortcut, Quick Validation, Validation and Safety Rules) into a single concise verification step tied to the real script.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Roughly half the body is generic templated boilerplate ("When to Use", "Key Features", "Implementation Details", repeated validation/checklist sections) that restates what Claude already knows and pads the token budget without adding domain value. | 2 / 5 |
Actionability | The core workflow gives copy-paste-ready commands (`Rscript scripts/forest_binary.R ...` and `python scripts/forest_binary.py ...`) plus a concrete output template, but the Example Usage and Quick Validation sections repeatedly point to `scripts/extract_criteria.py`, a script unrelated to forest plotting. | 4 / 5 |
Workflow Clarity | A clear three-step sequence (validate input → execute R with Python fallback → output results) with a validation checkpoint and an error-recovery fallback, though the input validation is light and the surrounding checklist is generic boilerplate. | 4 / 5 |
Progressive Disclosure | The body is a monolithic 215-line SKILL.md with section headers and clear inline script paths, but there are no separate reference files and substantial generic content is inlined rather than offloaded. | 3 / 5 |
Total | 13 / 20 Passed |