Content
96%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 well-engineered orchestration skill: lean rule-dense prose, copy-paste-ready commands and exact branch/merge procedures, and a clearly sequenced workflow with validation checkpoints, feedback loops, and stuck-detection for batch operations. The only structural weakness is navigation: the central handoff format doc is unlinked from the main file and several doc links point outside the bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is extremely dense with zero filler: no concept explanations, differences between batch types compressed into a table, and every sentence stating an operational rule (writer assignments, end conditions, label transitions), assuming Claude's competence throughout. | 5 / 5 |
Actionability | Guidance is fully concrete: exact commands with flags ('scripts/batch-poll.sh --spec <N>', '--issues <N,...>', 'scripts/ledger.sh --new', '--scope-issues <N,...>'), branch naming 'afk/<batch-id>/stage-<K>', '--force-with-lease' push, expected-head rebase merge, and GitHub API fields ('headRefOid', 'mergeable=MERGEABLE'). Only trivial gap: scripts/repo-context.sh is never mentioned. | 5 / 5 |
Workflow Clarity | The multi-stage process is explicitly sequenced (plan → serial stages with a writer/end-condition table for integration, review, PR → pause → wrap-up) with strong validation checkpoints (green HEAD, full-mode QA, a four-condition merge checklist) and genuine feedback loops (fixer → re-verify repetition until no failures or stuck detection '同一失败特征第 2 次出现'), so the batch-operation cap does not apply. | 5 / 5 |
Progressive Disclosure | The overview links eight one-level-deep reference files (spawn-prompts, herdr-teammate, implementer, stage-reviewer, qa-verifier, review-looper, fixer, recovery), all present in the bundle, with content appropriately split. Minor gaps: references/handoff.md — a concept used throughout the body — is never linked from SKILL.md itself (only reachable via role docs), and four links (../../../docs/agents/*, ../model-routing/SKILL.md) point outside the bundle and do not resolve in it. | 4 / 5 |
Total | 19 / 20 Passed |