Content
82%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, highly actionable skill body: every workflow step is an executable command, and failure modes get concrete WHY/BAD/GOOD treatment. The main improvements are integrating validation checkpoints into the workflow steps rather than isolating them in Anti-Patterns, trimming the 'gotcha' narration, and fixing the dead requirements.txt reference.
Suggestions
Inline the validation checkpoints into the workflow steps (e.g. after step 7, add 'review the final summary printed by batch_extract.py and re-run failed files with --print') so the sequence is self-contained.
Remove the dead [requirements.txt](requirements.txt) link from the References section, or add the file to the bundle.
Tighten the Mindset section and Anti-Pattern WHYs by dropping the repeated 'a production gotcha is...' framing — state the failure mode once in plain terms.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Commands are lean and copy-paste ready, and setup detail is correctly delegated to the reference file, but there is trimmable phrasing — the Mindset section's "a gotcha is assuming..." framing and the repeated "a production gotcha is..." constructions across Anti-Patterns add words without adding information. Not 5 due to these minor instances of over-explanation; not 3 because nothing explains concepts Claude already knows and no section is padded. | 4 / 5 |
Actionability | Every workflow step is a fully executable command with real flags and outputs — "./scripts/extractor.py paper.pdf --template enzyme -o results.md", "--format csv", "--ocr mathpix", "-p" custom prompt example, "batch_extract.py ./literature/ ./output/ --template enzyme --format csv", and "--print". Covers the common cases (presets, custom prompt, CSV, OCR, batch) copy-paste ready. Not 4 because there are no gaps in executable detail. | 5 / 5 |
Workflow Clarity | The eight-step sequence is clearly ordered and validation is genuinely documented (spot-check 3 rows against the source PDF, read the batch failed-files summary, check extracted text length before switching OCR), so the batch-operation cap does not apply. Not 5 because those checkpoints live in the Anti-Patterns section rather than being integrated into the workflow steps themselves — e.g. step 7 (batch) doesn't inline 'then review the final summary'. | 4 / 5 |
Progressive Disclosure | Good structure: the body stays a readable overview, setup/troubleshooting is properly pushed to a real one-level-deep reference (references/setup-and-troubleshooting.md exists and is linked inline and in a References section), and scripts exist as referenced. Not 5 because the References section links [requirements.txt](requirements.txt) which is absent from the bundle — a dead reference — a minor organization gap fitting the level-4 anchor. | 4 / 5 |
Total | 17 / 20 Passed |