Content
85%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 content is highly actionable with executable commands, a clear command table, and a strong error-recovery workflow for fabrication detection. Its main weakness is progressive disclosure: it references a REFERENCE.md that is not present in the bundle and inlines substantial reference-style material rather than splitting it into separate files.
Suggestions
Either ship the referenced REFERENCE.md (and any other linked files) in the bundle or remove the broken link, since absent references undercut progressive disclosure.
Move the full command table and per-command option detail into a separate reference file, keeping SKILL.md to a concise quick-start overview with one-level-deep, clearly-signaled links.
Trim the per-command prose where it repeats options already shown in the command table to nudge conciseness toward the lean-5 anchor.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and token-efficient — a compact command table and terse copy-paste examples with no padding of concepts Claude already knows — but the per-command prose and error-recovery loop, while justified for a fabrication-detection workflow, add minor length that keeps it just below the lean-5 anchor. | 4 / 5 |
Actionability | Provides fully executable, copy-paste-ready `scholar` commands covering format, export, verify, audit, retraction, and oa, plus parsing guidance (`--json | jq`), matching the fully-executable anchor. | 5 / 5 |
Workflow Clarity | The verify error-recovery loop is explicitly sequenced with exit-code checkpoints and a feedback path (re-run with --json, distinguish verdict vs error, report exactly what the tool returned), and audit exposes --fail-on-issues for CI gating — matching the explicit-validation-and-feedback-loops anchor. | 5 / 5 |
Progressive Disclosure | No references/scripts/assets bundle exists, yet the body references REFERENCE.md which is absent, and a large command reference plus per-command prose is inlined that could be split out — structurally organized but references are not real and content that could be separate is inline. | 3 / 5 |
Total | 17 / 20 Passed |