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, instruction-only skill body with a clear ordered workflow, identifier-resolution checkpoints, destructive-change confirmation, and a troubleshooting feedback loop, appropriately deferring detail to runtime tool and docs discovery. The main weaknesses are mild redundancy between the tips sections and the workflow, and the lack of any example HogQL query or post-write verification step.
Suggestions
Fold "Tips for Maximum Productivity" into the workflow steps and HogQL section — "batch related reads before writes" and "confirm identifiers up front" already appear in Steps 2–3, and the final troubleshooting bullet repeats the docs-search advice from the Overview.
Add one short example HogQL query (e.g., a narrow date-ranged events count) to anchor the querying guidance and make the "read the schema, confirm event/property names" advice concrete.
Add an explicit post-write verification step to the workflow (e.g., re-fetch the created flag, experiment, or dashboard to confirm it was created with the intended fields) to close the validation loop for write operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient and assumes competence (e.g., "Don't build workarounds for 'query-time' person properties"), but "Tips for Maximum Productivity" restates Step 2/3 guidance ("Batch related reads before writes; confirm identifiers up front") and the closing troubleshooting bullet repeats the docs-search advice from the Overview and Step 2. Not a 5 because of this duplicated material; not a 3 because the rest is lean with no concept explanations Claude already knows. | 4 / 5 |
Actionability | Guidance is specific and executable in context: Step 2 names the exact identifiers to resolve (project ID, flag key, experiment ID, insight/dashboard ID, error issue ID), Step 3 gives a concrete read-first batching order with a destructive-change checkpoint, and natural-language examples are quoted ("signups by week this quarter"). Not a 5 because there is no sample HogQL query or example tool invocation to anchor the querying guidance; as an instruction-only skill relying on runtime-discovered tools, the absence of code is otherwise justified. | 4 / 5 |
Workflow Clarity | Steps 0–4 are explicitly ordered ("Follow these steps in order. Do not skip steps.") with checkpoints (resolve identifiers before calling tools; state impact and confirm before destructive or broad changes) and a troubleshooting feedback loop (empty results → re-check names, date range, filters, timezone; confirm via a small query). Not a 5 because there is no explicit post-write verification step (e.g., re-fetch the created flag/experiment to confirm). The destructive/batch cap at 3 does not apply since validation and confirmation steps are present. | 4 / 5 |
Progressive Disclosure | A single-file skill with no bundle files and well-organized sections, a routing capability-map table, and correct deferral of syntax/product detail to the runtime docs-search tool rather than inlined reference material. Not a 5 because the ~85-line body is slightly more than a pure overview — the HogQL tips and productivity tips could fold into the workflow sections — though nothing here warrants separate files. | 4 / 5 |
Total | 16 / 20 Passed |