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.
The content is an exceptionally actionable, well-sequenced operational runbook dense with domain-specific signal and copy-paste SQL/tooling, with only minor trimmable framing prose. Its main weakness is progressive disclosure: everything lives in one ~220-line file with no reference offloading.
Suggestions
Move the 'MCP tools' catalog into a references/ file (e.g. references/tools.md) and keep a one-line pointer in the body, reducing inline reference bulk and lifting progressive disclosure.
Tighten the opening framing paragraph ('A pipeline is a promise...') to the essential signal-vs-noise model to push conciseness toward the 5-anchor.
Consider extracting the detailed Explore pattern catalog (watcher interventions, delivery-failure shift, batch exports, flow concentration) into a references/patterns.md referenced one level deep.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with PostHog-specific signal Claude would not already know (watcher state codes, HogQL footguns, MCP tool signatures, dedupe key conventions) and avoids explaining generic concepts; only minor framing prose ('a pipeline is a promise that data flows somewhere else') could be trimmed, sitting above the 3-anchor but short of the 5-anchor's fully lean ideal. | 4 / 5 |
Actionability | Provides copy-paste-ready SQL (the batch_exports count and roster queries), exact MCP tool calls with JSON params and pagination notes, concrete thresholds (share >= ~10% over 24h with >= ~50 triggered), and explicit footguns — fully executable guidance covering the common cases per the 5-anchor. | 5 / 5 |
Workflow Clarity | A clearly sequenced run (Get oriented -> Explore -> Save memory -> Decide -> Close out) with a Disqualifiers checklist, a profile-shape decision table, and confirm-before-file validation; the validation is advisory ('use judgment, these are the rails') rather than a hard gate, so it stays just below the 5-anchor's explicit gated checkpoints. | 4 / 5 |
Progressive Disclosure | The body is a ~220-line monolithic file with no reference files (references/scripts/assets absent); reference-like content such as the MCP tools catalog and detailed Explore patterns is inlined rather than offloaded to one-level-deep files, fitting the 3-anchor's 'content that should be separate is inline' despite decent section organization. | 3 / 5 |
Total | 16 / 20 Passed |