Content
75%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 well-structured, actionable diagnostic skill that loads Claude with genuine PostHog-specific knowledge (materialisation eligibility, the JOIN+variable trap, TTL enum) and provides a clear sequenced workflow with validation. Slight gains available from trimming the example interaction and splitting the detailed rewrite bullets into a reference file.
Suggestions
Trim the "Example interaction" block or move it to a reference file — its reasoning largely restates the decision tree above it, which would lift conciseness toward the score-5 anchor.
Split the Step 3 rewrite bullets (cohort breakdown, JOIN+variables, missing variables, HogQL `*`) into a dedicated reference file linked from the body, improving progressive_disclosure for this ~200-line skill.
Intersperse validation checkpoints through the numbered Workflow (e.g. after steps 2–4) rather than only at the final "confirm before applying" step, which would move workflow_clarity to the score-5 anchor.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with product-specific knowledge (materialisation semantics, the JOIN+variable trap, the TTL enum) that Claude would not already know, so most tokens earn their place; minor restating in "Important notes" and a somewhat long example interaction keep it just below the lean score-5 anchor. | 4 / 5 |
Actionability | Names specific tools, gives exact TTL enum values, and provides a copy-paste SQL query against `query_log`; the rewrite guidance is necessarily prose rather than code, leaving minor gaps versus the fully-executable score-5 anchor. | 4 / 5 |
Workflow Clarity | A numbered 6-step workflow plus a sequenced Step 1–4 decision tree, with explicit validation ("confirm before applying", "get sign-off") and a validate→compare→apply→confirm feedback loop for the AI rewrite; the destructive-operation cap does not bind because validation is present, but per-step checkpoints are concentrated at the end of the numbered workflow rather than interspersed. | 4 / 5 |
Progressive Disclosure | Self-contained with clear section headers (When to use, Available tools, Decision tree, Workflow, Example, Important notes) and no bundle files; at ~200 lines some detail such as the Step 3 rewrite bullets could be split into a reference file, keeping it just below the score-5 anchor. | 4 / 5 |
Total | 16 / 20 Passed |