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.
The body is an exemplar of its genre: a tight, fully actionable handoff protocol with exact paths, copy-paste templates, an explicit state-check before writing, and a user-review feedback loop before finishing. The only flaw is minor repetition — the same checklist of pending items is enumerated three times across §1, §3, and the §5.2 template. It scores at or near the top on every dimension.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence — no concept re-teaching, exact paths, and dense templates — but the enumeration "pending alignment decisions, accepted limitations and verification gaps with source paths" is repeated three times (§1, §3, and the §5.2 template) and §2's instruction repeats the §5.1 Working Context placeholder nearly verbatim. This matches 'efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place of anchor 5. | 4 / 5 |
Actionability | Guidance is fully concrete for an instruction-only skill: exact file paths (`.apm/memory/handoffs/manager/handoff-<NN>.log.md`, `.apm/bus/manager/handoff.md`), a zero-padding naming convention, complete copy-paste markdown templates with frontmatter fields, and an explicit terminal action ("invoke `apm-2-initiate-manager` in a new chat"). This matches 'copy-paste ready… specific examples cover the common cases'. | 5 / 5 |
Workflow Clarity | A clear four-step sequence (check state → write log → write prompt → user review) with an up-front validation checkpoint ("check the current state before writing either file", enumerating Tracker, bus files, and git branches/worktrees/merges) and an explicit feedback loop ("Apply their corrections and ask again. After they approve…"). Writing two markdown files is not destructive or batch, so no cap applies; this matches the anchor with explicit validation and error-recovery loops. | 5 / 5 |
Progressive Disclosure | No bundle files exist and every part of the body is used on each invocation, so nothing belongs in a separate file; sections are numbered and navigable, and the single external pointer is clearly signaled ("per `{SKILL_PATH:apm-2-initiate-manager}`"). There is no monolithic wall, inlined content that should be external, or nested references, matching the well-organized self-contained ideal. | 5 / 5 |
Total | 19 / 20 Passed |