Content
77%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.
An exceptionally actionable, rigorously validated state-machine procedure where every failure path has a specified next step — the workflow and actionability are near-ideal for a complex orchestration skill. Its weaknesses are density (run-on conditional paragraphs that resist quick parsing) and a total absence of progressive disclosure, with all reference-worthy material inlined in one monolithic file.
Suggestions
Move the refusal-code catalog (## Refusals), the fix-agent brief template, and the In-place variant into reference files under references/, keeping SKILL.md as an overview that points to them one level deep.
Break the giant single-paragraph steps (notably Start steps 3 and 5) into shorter bullets or a decision table pairing each condition (localUnpushedCommits, checkedRecently, wasEnded, etc.) with its required action.
Consolidate the repeated gate-matching incantation ("a task whose gate contains autofix-pr snapshot <n> --gate") into one named helper description defined once and referenced by short label elsewhere.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | There is no concept-teaching padding (nothing explains what a PR or CI is) and nearly every sentence carries operational detail, so it is above 2; but the ~330-line body packs conditions into enormous run-on paragraphs (Start steps 3 and 5 are ~400-word single paragraphs) that could be markedly tightened into tables, bullets, or shorter sentences — matching the 3 anchor (mostly efficient but could be tightened) rather than 4, where only minor trimming would be needed. | 3 / 5 |
Actionability | Guidance is fully executable: exact commands ("${QWEN_CODE_CLI:-qwen}" autofix-pr prepare <n> --repo <owner>/<repo> --host <host>), explicit parameter mappings (--take-over is take_over: true), a complete fill-in brief template, and a concrete JSON reply-plan example. This matches the 5 anchor: copy-paste ready and covering the common cases. | 5 / 5 |
Workflow Clarity | Start, Round, Stop, Status, Resume, and After-a-background-fix are each numbered and ordered, with explicit validation ("Commit only when they pass", verified: false discards the worktree) and pervasive feedback loops (retry limits for busy/partial, resync restarts once per turn, fix_plan correct-and-rerun, refusal next codes routing every failure to a specified action). Validation is present for destructive operations, so no cap applies; this matches the 5 anchor (explicit validation steps, feedback loops for error recovery). | 5 / 5 |
Progressive Disclosure | No bundle files exist and all content is inline in a single 330-line file. Real section structure is present (## Refusals, ## Arguments, ## In-place, ## Trust, etc.) so it is above the 2 anchor's "minimal structure", but content that clearly belongs in separate files — the refusal-code catalog, the fix-agent brief template, the in-place variant, the status-interpretation rules — is inlined, matching the 3 anchor. | 3 / 5 |
Total | 16 / 20 Passed |