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 information-dense, highly actionable body with strong sequencing and validation checkpoints. Its main weakness is progressive disclosure: the routing table points to five doc files that are not present in the bundle.
Suggestions
Ship the referenced jobs/*.md (finding, enriching, researching, automating) and shared/authoring.md files, or remove the routing table entries that point to them, so navigation resolves.
Either reference references/api-reference.md from the body or drop it from the bundle, so the present-but-unreferenced file does not confuse discovery.
Confirm the <skill-root> placeholder used in the script paths resolves at runtime, since the bundle relies on it for every scaffold/run/cost command.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — terse imperatives ("Marginal, never amortized.", "One shape.") with no over-explanation of concepts; every line encodes product-specific operational knowledge or a concrete failure mode. | 5 / 5 |
Actionability | It provides copy-paste-ready commands with concrete flags and arguments across install, auth, preflight, catalog, scaffold, run, export, cost-receipt, and feedback — covering the common cases fully. | 5 / 5 |
Workflow Clarity | An explicit contract pipeline ("contract → compare → exploit → recover → export → price"), a completion-receipt checkpoint ("{ok: true, runId, output} is the completion receipt"), the COST RECEIPT, receipt-label feedback loops (CUT CANDIDATE / NEVER REACHED / cached calls), and a deliverable checklist give clear sequencing with validation for the batch operations. | 5 / 5 |
Progressive Disclosure | Signaling and one-level-deep routing are excellent, but scored against the actual bundle the navigation is broken: jobs/finding.md, jobs/enriching.md, jobs/researching.md, jobs/automating.md and shared/authoring.md are referenced yet absent, while references/api-reference.md exists but is never referenced — more than a minor organization gap. | 3 / 5 |
Total | 18 / 20 Passed |