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 procedural skill with executable commands and a clear multi-step workflow. The main gaps are minor verbosity in an illustrative output block and the absence of an explicit validate->retry feedback loop for the batch/destructive operations.
Suggestions
Tighten conciseness: replace the fabricated issue titles/dates in the Step 2 output example with generic placeholders (e.g. #N <title> (closed <date>)) so the block shows format only without filler content.
Strengthen workflow_clarity for the batch/destructive steps: add an explicit post-close verification (re-fetch milestone to confirm state==closed) and a retry-once-then-log feedback loop for issue label updates, rather than only log-and-continue.
Improve progressive_disclosure/navigation: add a one-line quick-start pointer at the top that references the Workflow section, since the file is over 50 lines and a single self-contained procedure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean with executable commands and no concept over-explanation, but the Step 2 illustrative output block carries filler placeholders (e.g. '#12 SAM: Error Recovery (closed 2026-02-20)') that could be trimmed to generic format placeholders. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready commands throughout — backlog_list_milestones, uv run ...github_project_setup.py issue set-milestone/close/remove-milestone, milestone close --dry-run, project update-status — covering all four open-issue handling options with concrete placeholders. | 5 / 5 |
Workflow Clarity | Clear six-step sequence with explicit pre-checks (already closed -> stop; open_count==0 -> skip to Step 4), a --dry-run preview, and a non-zero exit signal; however the batch/destructive reassignment and close steps lack an explicit post-close verification or validate->fix->retry feedback loop (error handling is log-and-continue), which keeps it below a 5. | 4 / 5 |
Progressive Disclosure | Well-organized into Arguments, Workflow (Steps 1-6), and Error Handling sections with no monolithic wall of reference material; it is a single self-contained procedural file with no bundle references, and the 5-level anchor's 'appropriately split / one-level-deep references' criterion is not met since nothing is split out. | 4 / 5 |
Total | 17 / 20 Passed |