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 dense, highly actionable orchestration body with executable commands, complete card/table templates, and fail-closed validation at every step. Remaining polish is trimming the repeated write-prohibitions, adding worker-failure recovery guidance, and signaling when to open the label contract.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Telegraphic, imperative prose with zero explanation of concepts Claude already knows; e.g. the selection contract is compressed to "fetch_queue.py owns list + eligibility (closed, locked, empty, template-only; sweep-only spam)". Not 5 because the write-prohibition ("never assigns, never requests reviewers", "do not comment/label/close") is restated roughly five times across the intro, activation card rules, Invocation, Selection, and Hard nos, and "Do not implement" appears three times — more than the 'minor trimming' of the 5 anchor. | 4 / 5 |
Actionability | Copy-paste-ready commands with a fallback: "python <this-skill>/scripts/fetch_queue.py --kind issue --mode sweep --repo microsoft/apm > batch.json" then "python <this-skill>/scripts/triage_state.py < batch.json", named mode "--mode dispatch --number N", and "If gh is unavailable, pass --records-json and --labels-json". The queue table and activation card are fully specified with exact columns and fields. | 5 / 5 |
Workflow Clarity | The numbered Procedure has explicit fail-closed checkpoints ("Missing -> stop", "A helper failure stops the run", "Missing table, missing column, or blank rationale -> stop", "write: on -> stop") plus a recovery path for gh unavailability, and the batch nature is guarded by the mandatory queue table. Not 5 because there is no recovery or retry guidance when a worker slot itself fails mid-drain — a minor validation gap in an otherwise checkpoint-dense workflow; the batch cap at 3 does not apply since validation steps are present. | 4 / 5 |
Progressive Disclosure | References are one level deep and resolve to real files: "Load [assets/fan-out-pool.md](assets/fan-out-pool.md)" is clearly signaled at the point of use, and scripts/fetch_queue.py, scripts/triage_state.py, and assets/label-contract.json all exist in the bundle. Not 5 because "assets/label-contract.json" and ".github/workflows/triage-panel.md" are named as canonical owners without a load signal or one-line summary of when the agent should open them. | 4 / 5 |
Total | 17 / 20 Passed |