Content
92%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 exemplarily lean orchestrator skill: a nine-step pipeline with explicit done conditions, validation loops, held-decision rules, and load-on-demand references to the sub-skills that do each step's work. The only minor weakness is a few actionability gaps where specifics (focused tests, Greptile review mechanics) are deferred to external documents.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~46-line body is lean and assumes competence: no concept explanations, no padding, and every clause carries non-obvious project-specific information (e.g., "a subagent cannot read this conversation", "origin/next moves during a session", "The reviews compare commits, so they do not see uncommitted work"). It matches the anchor where every token earns its place. | 5 / 5 |
Actionability | Guidance is mostly executable: exact commands (`cd code && yarn fmt:write`), concrete branch instruction ("Branch from `origin/next` and record the base SHA"), copy-paste-ready PR body formats (`Closes #<number>`, `Closes [SB-<number>](<Linear URL>)`), and explicit per-step done conditions. Minor gaps keep it below a 5 — "Run the focused tests" never says which tests, and mechanics like "Ask Greptile for a review, as [Pull requests] says" are deferred to external docs rather than given inline. | 4 / 5 |
Workflow Clarity | Nine clearly sequenced steps, each with an explicit done condition ("Done when the focused tests pass and the working tree is clean"; "Done when the only unresolved bot threads are the high-severity findings you disagree with") and built-in validation feedback loops ("run it again until only findings judged and left on purpose remain", re-review after fixes). The hand-over step even specifies the exact report structure per reviewer. This matches the top anchor with checkpoints and error-recovery loops. | 5 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent), and the under-50-line body is well organized into "Steps" and "After the hand-over" sections. Cross-references to sub-skills are one level deep, clearly signaled with links, and explicitly load-on-demand ("Read that skill when you reach the step, not before"), which is the essence of appropriate progressive disclosure for an orchestrator skill. | 5 / 5 |
Total | 19 / 20 Passed |