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.
A mature, dense operational contract with best-in-class reference routing and strong validation checkpoints including a pre-present checklist and bounded regeneration loop. Its weakness is repetition and sheer length in the root body, which could be meaningfully tightened by delegating exception detail to the references it already routes to.
Suggestions
Deduplicate instructions stated twice (SKILL_DIR/env retention in Bootstrap and Dispatch; ScrapeCreators Reddit backfill rules in Dispatch and Security) and drop the version number from the H1, keeping it in frontmatter only.
Move each LAW's mode-specific exceptions (comparison, discovery, hiring, agent-mode) into their respective references, leaving one-sentence laws in the root.
Trim the Security & Permissions section to endpoints and consent boundaries, moving credit-spending thresholds and backend lists into a reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body avoids general-concept padding and assumes competence, but it is noticeably repetitive: SKILL_DIR/env-var retention instructions appear nearly verbatim twice, the ScrapeCreators backfill credit rules are stated in both dispatch and the security section, and the laws restate their exceptions multiple times. The version number "v3.39.0" in the H1 is time-sensitive detail that will stale, and much of the output-contract density could be tightened or delegated to references. | 3 / 5 |
Actionability | Concrete guidance dominates: a complete executable first-run gate command (`grep -q "SETUP_COMPLETE=true" ~/.config/last30days/.env ...`), exact flags (`--plan -` with quoted heredoc, `--resolve-save-dir`, `--diagnose --cached --json`, the three `--discover` legs), and precise env-var handling. It falls short of anchor 5 because the primary engine invocation itself lives in the runbook reference rather than the body. | 4 / 5 |
Workflow Clarity | A clear dispatch sequence (bootstrap → reference routing → first-run gate → topic routes → output contract → pre-present self-check) with genuine validation checkpoints: the gate's one-token branch, the 9-item pre-present checklist, the LAW 8 post-synthesis check, and a regenerate-at-most-once feedback loop. Minor gaps remain because step ordering (Steps 0.45–0.75) and mode-specific sequences are delegated to references, so the body alone does not carry the full sequence. | 4 / 5 |
Progressive Disclosure | The routing table is exemplary: 16 condition → required-read → return-point rows, every referenced file (references/runtime.md through references/save-html-brief.md) verified to exist on disk, one level deep with each mode returning to the root for further loads. The body is a true dispatch hub over well-signaled, appropriately split references. | 5 / 5 |
Total | 16 / 20 Passed |