Content
88%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 thorough, highly actionable skill body for a complex batch/destructive operation, with strong validation checkpoints and executable code throughout. The main weakness is repetition of the consent/push/safety rules across sections, which inflates token cost without adding clarity.
Suggestions
Consolidate the consent ('--apply is consent, do not wait for a second yes'), push-is-part-of-rebase, and never-merge/comment/force rules into the Safety section once, and reference it from Modes and Apply instead of restating each rule 3-4 times.
Consider moving the full embeddable per-PR agent prompt and apply-child prompt into a references file (e.g. references/agent-prompts.md) and linking, to reduce SKILL.md body length while keeping the prompts copy-paste ready.
The snapshot JSON schema and SWEEP report template could live in references/ to further slim the body, leaving SKILL.md as an overview with one-level-deep pointers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Largely lean operational guidance (gh commands, JSON schemas, safety rules) with no beginner-concept padding, but the consent/push-is-part-of-rebase/never-merge-or-comment rules are repeated 3-4 times across Modes, Safety, and Apply sections and could be tightened. | 4 / 5 |
Actionability | Fully executable: exact `gh pr list`/`gh pr view` field lists, copy-paste rebase+`git push --force-with-lease` bash with BEFORE/AFTER SHA verification, `gh api -X POST .../actions/runs/<RUN_ID>/approve`, and complete JSON return schemas for both read and apply agents. | 5 / 5 |
Workflow Clarity | Destructive/batch operation with explicit validation checkpoints — `gh auth status` gate, security gate before mutations, BEFORE/AFTER head-SHA comparison as the done-criterion, conflict abort with `git rebase --abort` → blocked-conflicts, and push-403 no-retry feedback loop — sequenced 1-6 with a hard-rules checklist. | 5 / 5 |
Progressive Disclosure | Clear section structure (Args, Modes, Daily, Prerequisites, Safety, Procedure, Orchestrator tips, Reference) with a one-level-deep, clearly signaled reference to references/security-checklist.md (verified present), but the large embeddable per-PR and apply-child prompts are inlined rather than split out. | 4 / 5 |
Total | 18 / 20 Passed |