Content
67%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 strongly operational skill document: executable commands, a clear routing tree, typed failure statuses, and genuinely progressive references for the heavy browser/delivery detail. Its main costs are rule repetition across sections, a ~350-line body that inlines content the references could hold, and two dead references (`src/wizard.py`, `requirements.txt`) plus one internal contradiction about school presets.
Suggestions
State each governing rule (SI gate, routing, CNKI-only, browser-state, API fallback) once in its authoritative section and cross-reference it elsewhere instead of restating it 2-4 times.
Fix the preset contradiction: either remove the 'no school presets' claim or replace the `configure_school.py preset`/`src/wizard.py` instruction in Preconditions with the actual first-run flow.
Remove or ship the referenced `src/wizard.py` and `requirements.txt`, and move the institutional-domain tables and full status catalog into the delivery/browser reference to slim the router.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is information-dense and mostly avoids explaining concepts Claude already knows, but it repeats its own rules: the SI gate appears both as a top blockquote and again in 'Download Intake', the API-first/OA fallback routing is stated in the workflow blockquote, the ASCII tree, the 'Publisher API fallback' blockquote, and the 'API-First and Open-Access Fallback' section, and the browser-state principle appears twice. It could be tightened to one authoritative statement per rule with cross-references. | 3 / 5 |
Actionability | Concrete, copy-paste-ready commands cover the common cases: `configure_school.py infer/url/show/health`, `configure_credentials.py set/validate`, and a full battery of `batch_download.mjs` examples with real DOIs, titles, and flags. Not 5 because two referenced paths do not exist in the bundle — `src/wizard.py` (Preconditions step 2) and `requirements.txt` — so those instructions are not executable as written. | 4 / 5 |
Workflow Clarity | Sequencing is strong: an explicit SI confirmation gate first, a routing decision tree, a numbered preconditions checklist, a 29-entry typed status taxonomy with handoff-vs-failure semantics, and bounded retry/user-handoff feedback loops appropriate to a batch operation. Not 5 because Preconditions step 2 directly contradicts the earlier statement 'The distributed skill contains no school presets' by instructing `configure_school.py preset "<school name>"` when config is missing. | 4 / 5 |
Progressive Disclosure | The router keeps browser-workflow and delivery/failure detail in two real, one-level-deep reference files, each with an explicit load condition, and the 20 helper scripts under scripts/lib are appropriately left undocumented in the overview. Not 5 because the ~350-line body still inlines material (institutional domain tables, the full status list, PowerShell node-resolution) that belongs in the references, making the overview heavier than a router needs to be. | 4 / 5 |
Total | 15 / 20 Passed |