Content
71%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 a dense, well-structured operational contract: executable commands with explicit validation loops, precise artifact-path rules, and disciplined delegation of detail to reference files. Its main weaknesses are broken navigation — several linked files (workflows/, schemas/review-finding.md) are missing from the bundle while two reference files are orphaned — and a reliance on ecosystem jargon and sibling-skill anchors that the bundle alone does not fully support.
Suggestions
Ship the referenced files (workflows/review.md, workflows/mutation-stability.md, schemas/review-finding.md) in the bundle, or restructure so every path the body links to resolves within it.
Reference references/perf-qa.md and references/ui-screenshots.md from SKILL.md (or from a bundled workflow file) so no bundle file is orphaned and each is discoverable in one hop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with rules and assumes Claude's competence throughout — no padding, no explanation of known concepts, e.g. "Verify before reporting: if the repo contains the caller, config, test, or doc that settles a suspicion, read it." Not 5 because the hooks paragraph ("Where installed and running, `reviewer-read-only` refuses edits…") and the repeated "judge against code-quality, not the change" theme across several Ethos bullets could be consolidated and trimmed. | 4 / 5 |
Actionability | Concrete, copy-paste-ready commands with explicit success criteria: `orch-runtime review-artifact --text check --file [ARTIFACT_PATH] --worktree [WORKTREE_PATH]` with "Fix until this prints `\"ok\": true`", and `review-depth --base REF --head REF --repo DIR`. Not 5 because roughly half the body (the Ethos rules) is policy prose with no worked example of a finding or artifact, leaving minor gaps between rule and execution. | 4 / 5 |
Workflow Clarity | The Output Contract is a clear sequence (capture starting fields → write artifact → self-validate → return) with an explicit validate-fix-retry checkpoint and a precise artifact path format. Not 5 because the core review workflow (diff → findings → verdict) is delegated to `workflows/review.md`, which is not present in the bundle, so the end-to-end sequence with checkpoints is never shown in one place. | 4 / 5 |
Progressive Disclosure | In-document structure is good and one-level references to real bundle files exist (references/finding-disposition.md, scripts/review-depth, scripts/mutation-stability), but the body links to workflows/review.md, workflows/mutation-stability.md and schemas/review-finding.md that are absent from the bundle, and references/perf-qa.md and ui-screenshots.md are unreachable from SKILL.md (reachable only via a missing workflows/ file). Scored against the actual bundle structure, navigation is broken in both directions, matching anchor 3 rather than 4. | 3 / 5 |
Total | 15 / 20 Passed |