Content
88%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 body is a dense, actionable investigation playbook built around executable SQL and tool calls, with a clearly sequenced workflow and decision/recovery branches that anticipate failure modes. Its main limitation is mild verbosity in a few explanatory tables and the absence of any bundle-file offloading.
Suggestions
Consider moving the detailed `$app_version` / `$exception_releases` / `$lib_version` comparison table into a reference file and keeping only the decision rule inline, to tighten the main workflow.
Trim the prose around 'Picking the right version property' to the actionable rule (prefer `$app_version`, fall back to `$exception_releases`, avoid `$lib_version` for app-version questions) since the table already carries the detail.
A short 'Prerequisites' note stating that `execute-sql` access and (optionally) session replay are needed would let the reader gauge fit before starting Step 1.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean and focused on PostHog-specific knowledge Claude lacks (the `$app_version` vs `$lib_version` distinction, the `issue_id` virtual-field fallback, the ClickHouse nullable-JSONExtract gotcha); a few explanatory passages like the version-property table could be trimmed without losing clarity. | 4 / 5 |
Actionability | Provides copy-paste-ready tool-call JSON and executable SQL for each step, covering the common cases (release breakdown, feature-flag enumeration, surrounding-events timeline, console logs, OTEL logs) with concrete, runnable patterns. | 5 / 5 |
Workflow Clarity | Six numbered steps with explicit decision branches (sparkline shape → first breakdown) and recovery checkpoints ('If recent and earliest events look materially different ... Flag for `grouping-noisy-errors`', 'If `query-logs` returns nothing ... say so and move on'); read-only investigation, so no destructive-validation cap applies. | 5 / 5 |
Progressive Disclosure | Well-organized into clearly headed Steps 1–6 with subsections 5a–5d and a 'Related skills' section that signals peer skills; no bundle files exist so everything is inline, which is appropriate for a workflow skill but keeps it just shy of the one-level-deep reference ideal. | 4 / 5 |
Total | 18 / 20 Passed |