Content
80%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 tight, highly actionable orchestration body with real commands and a clear three-phase sequence. Its one substantive weakness is the absence of validation between the parallel map step and the reduce step, which the batch-operation guideline caps at 3 for workflow clarity.
Suggestions
Add a checkpoint between Map and Reduce, e.g. 'Before reducing, verify every worker outfile in ./findings/workers/ exists and matches the candidate schema; re-run or re-prompt any missing worker.'
Provide a short worker prompt template so the map step is fully copy-paste ready rather than a list of ingredients.
State the expected outcome of each command (planner emits worker assignment + keep-threshold; reduce emits ranked findings) so failures are detectable at each phase.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and entirely operational: fixed paths, two commands, and worker-assignment instructions, with no explanation of concepts Claude already knows. Even the wordiest passage (resolving the ensemble scripts path, 'the runner may pass an absolute path instead — use whichever it provides') is necessary operational detail, not padding, matching 'every token earns its place'. | 5 / 5 |
Actionability | Two concrete `uv run` commands with real arguments ('--report-dir "$(pwd)/findings/workers" --window 2 --json', "--keep-threshold 2") are executable, and worker spawn instructions list exact inputs (groups, rules, targets, outfile, location format). Minor gaps keep it below 5: the `<scripts>` placeholder must be resolved by the reader, and the map step gives worker-prompt ingredients rather than a copy-paste prompt template. It is above 3 because the guidance is genuinely executable, not pseudocode. | 4 / 5 |
Workflow Clarity | The Plan → Map → Reduce sequence is clearly numbered and labeled deterministic vs. parallel, but the batch map step (one worker agent per group, run in one parallel batch) has no explicit validation checkpoint — e.g., verifying each worker's outfile exists and is well-formed before reducing. Per the judging guidelines, batch operations without validation cap workflow clarity at 3, matching 'sequence present but checkpoints missing or implicit'. | 3 / 5 |
Progressive Disclosure | The skill is under 50 lines, has no bundle files of its own, and is well organized (a fixed-paths list followed by numbered steps). Its only external dependency (the ensemble scripts) is referenced one level deep with an explicit path ('../../../plugins/plugin-creator/skills/ensemble-rule-review/scripts/'). Per the simple-skill exception, this can score 5 with just well-organized sections. | 5 / 5 |
Total | 17 / 20 Passed |