Content
78%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.
A well-organized, token-efficient review skill with a clear sequenced procedure and an unusually thorough Validation section. Its weaknesses are deferred detail that the bundle does not actually deliver: severity definitions, the findings template, and the canonical contract are all pointed at files missing from this bundle, and the one file that does exist (references/context-preservation.md) is not clearly linked.
Suggestions
Ship the referenced detail in the bundle or inline it: either include Infrastructure/references/contract.yaml and finding.md.tmpl, or inline a minimal findings-output example and one-line P0-P3 severity definitions directly in SKILL.md so reviewers can classify findings without external files.
Fix the References section to match the actual bundle: link references/context-preservation.md explicitly (or remove the 'compatibility mirror' pointer), and drop or correct paths to files that don't exist (contract.yaml, evals.yaml, task-profile.json, finding.md.tmpl, assets/icons).
Attach the three dangling 'Read when:' lines to the specific references they describe (e.g. domain-model-routing.md and qa-intake-routing.md) as bolded lead-ins, so each read-condition is unambiguously tied to its target file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean fragment-style throughout ("Findings first, implementation second.", "Resolve mode and target; stop if unusable.") with zero concept explanations Claude already knows and no padded sections. Every section (Philosophy through Subagent Routing) carries operational content, matching 'every token earns its place'; there is no over-explanation to trim, so anchor 4 does not apply. | 5 / 5 |
Actionability | Concrete, executable instruction-style guidance: a 6-step procedure, an explicit output contract ("findings (`P0-P3`) with location, impact, minimal fix, confidence", "feedback_response_plan (`accept`, `clarify`, `push_back_with_evidence`)"), and concrete QA verification steps ("compare reported behavior, expected behavior, reproduction path, and proposed fix evidence"). Not a 5 because key details are deferred to files missing from the bundle — the finding template (finding.md.tmpl) and the canonical contract (Infrastructure/references/contract.yaml) — leaving no worked example of an actual finding; it clearly exceeds anchor 3's 'pseudocode / missing key details' level. | 4 / 5 |
Workflow Clarity | The Procedure is a clear numbered sequence and the Validation section supplies explicit checkpoints ("Ensure mode matches target and findings contain severity, location, impact, minimal fix, confidence", "Fail fast: stop at first blocking prerequisite or failed validation gate"). Not a 5 because the severity scale itself is undefined in the body — P0-P3 are named but never characterized, so a reviewer cannot consistently classify findings without the missing contract file; not a 3 because validation gates are explicit, not merely implicit. | 4 / 5 |
Progressive Disclosure | The body is well-sectioned, but scored against the actual bundle: the References section points to files that do not exist here (./Infrastructure/references/contract.yaml, ./finding.md.tmpl, ./assets/icon-*.png), while the one real bundle file, references/context-preservation.md, is never individually linked — it is only gestured at as a 'Compatibility mirror (non-canonical): ./references' directory pointer. The three trailing 'Read when:' lines are also ambiguously detached from their intended targets. That is 'references present but not clearly signaled / could be better organized' (anchor 3); it is not anchor 2 since the SKILL.md is not a monolithic inline dump. | 3 / 5 |
Total | 16 / 20 Passed |