Content
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A lean, highly actionable body that leads with the one non-obvious data fact, gives complete executable HogQL recipes plus typed-tool alternatives, and cleanly splits the headline query inline from the rest in a shared one-level-deep reference. Workflow sections are clearly sequenced with explicit guardrails appropriate to read-only analytics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Opens with the non-obvious fact Claude would not know ("no dedicated ClickHouse table — every field lives as a `$mcp_*` property on `events`") and never pads with basic PostHog/ClickHouse/MCP explanations; the 'two rules that matter most' framing keeps every token earning its place, matching the 'lean and efficient' anchor. | 3 / 3 |
Actionability | Provides two complete, copy-paste-ready HogQL queries with exact property names, required casts (toBool/toFloat), HAVING volume floors and LIMIT clauses, plus named typed tools with their toolName + dateRange parameters and concrete UI link templates — fully executable, not pseudocode. | 3 / 3 |
Workflow Clarity | The canonical 'which tool has the highest error rate' workflow is fully sequenced with explicit guardrails (effective-tool-name rule, mandatory time range, volume floor) and a report-both-rate-and-volume follow-up; the read-only nature means the destructive-ops validation cap does not apply, fitting the top anchor. | 3 / 3 |
Progressive Disclosure | Inlines only the headline query and defers matrix/latency/harness recipes to a single shared, well-signaled one-level-deep reference with explicit 'Read it before writing queries' navigation; the local bundle dirs (references/scripts/assets) are empty, so scoring reflects the clean repo-external reference structure rather than bundle files. | 3 / 3 |
Total | 12 / 12 Passed |