Content
85%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.
This is a tightly engineered policy skill: an event-decision table with explicit validation gates (conflict probes, merge preflight, expiry re-checks), concrete numeric cadences, and clean deferral of mechanics to clearly annotated owner documents. The only deductions are minor: a version-specific tracker link and two required specifics (attribution footer text, canonical prompt) that are deferred rather than shown.
Suggestions
Move the version-specific "0.28.0 release tracker" link out of the body (e.g., into the release-process owner document it already references) so the skill stays evergreen and trims a time-sensitive token.
Inline the exact required attribution footer text (or a one-line template of it) next to "End authored GitHub comments with the required attribution footer" so the rule is executable without a doc round-trip.
Consider replacing the self-referential "Keep this skill at or below 120 lines" line with nothing or a maintainer-note comment; it spends body tokens on upkeep rather than on driving the PR.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and rule-dense ("conflicts never wait", "first check near 50 minutes and later checks near four hours") with no concept padding, but the time-sensitive "0.28.0 release tracker" link and the self-referential "Keep this skill at or below 120 lines" line are tokens that do not earn their place for executing the skill, per the time-sensitivity guideline. | 4 / 5 |
Actionability | The guidance is largely executable policy — the event-to-decision table, "never whole-array replacement or `gh pr edit`", and "Stop after three quiet checks" are concrete — but a few required specifics live only in referenced docs (the "required attribution footer" text, the canonical reviewer prompt), leaving minor gaps versus anchor 5's copy-paste readiness. | 4 / 5 |
Workflow Clarity | Sequencing and validation are explicit throughout: "Probe conflict first" ordering, "Run live exact-head/base preflight, then merge only when every item passes", the expiry re-check ("probe the live base and read CI once more"), and the six-round boundary checkpoint, with feedback loops (round retry, conflict recovery) and an event-decision checklist for a complex process — matching anchor 5 rather than anchor 4, which requires actual validation gaps. | 5 / 5 |
Progressive Disclosure | The body is a lean overview with well-signaled one-level-deep references, each annotated with its owned scope ("Round orchestration: candidate locks, rounds, recovery, waits, review state, carry-forward, and merge preflight"); no nested references exist and mechanics are appropriately split to owner documents, matching anchor 5. | 5 / 5 |
Total | 18 / 20 Passed |