Content
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is well-structured and mostly actionable, but it is held back by a missing bundled script dependency, no validation checkpoint in the batch workflow, and a dangling file reference.
Suggestions
Ship the referenced run_actor.js in a scripts/ bundle directory (or inline its logic) so the run commands are actually executable end-to-end.
Add an explicit verification step between Step 4 and Step 5, e.g. check the run status/output exists before summarizing results.
Collapse the three Quick/CSV/JSON command blocks into one command showing optional --output/--format flags to remove repetition.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean and avoids explaining concepts Claude already knows, but the three near-identical Quick/CSV/JSON bash blocks repeat the same command with one flag differing, and the time-sensitive 'Node.js 20.6+' version pin adds maintenance noise. | 2 / 3 |
Actionability | Commands are concrete with justified placeholders, but every run path depends on ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js, which is not present in the bundle (no scripts/ directory), leaving the executable chain incomplete. | 2 / 3 |
Workflow Clarity | The five steps are clearly sequenced with a progress checklist, but this batch data-extraction workflow has no validation/verification checkpoint (e.g. confirm the run succeeded before summarizing), which caps workflow clarity at 2. | 2 / 3 |
Progressive Disclosure | Sections are well organized, but all content lives inline in SKILL.md and the one referenced path (reference/scripts/run_actor.js) does not exist in the bundle, making it a dangling reference rather than a cleanly signaled one-level-deep file. | 2 / 3 |
Total | 8 / 12 Passed |