Content
71%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 skill body with clear tool-selection workflows and explicit validation gates, especially in the semantic-layer section. Its main weakness is progressive disclosure: the body points to roughly thirty reference files that are not present in the bundle, so the otherwise-excellent navigation structure resolves to dead links.
Suggestions
Ship the ./references/*.md files referenced in the Data Schema, HogQL References, and Analytics Query Examples sections, or remove links to files that are not bundled — the current body resolves ~30 paths to missing files.
Add one or two short inline HogQL/SQL snippets for the most common query paths so the body is self-sufficient for the common cases instead of always delegating to external examples.
Tighten the semantic-layer section: factor the prompt-injection/untrusted-markdown rationale and repeated method-selection reminders into a single concise statement to reduce over-explanation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean and action-oriented with no basic-concept padding, but the semantic-layer section carries verbose embedded rationale (e.g., the prompt-injection paragraph about never obeying embedded instructions) and some repeated method-selection guidance that could be trimmed, fitting the 'efficient with minor over-explanation' 4 anchor rather than the lean 5. | 4 / 5 |
Actionability | Gives concrete executable guidance — specific tools (posthog:query-trends, posthog:execute-sql, posthog:metric-list, posthog:data-catalog-metric-run) and concrete gates (status approved AND is_drifted false) — but the actual code/SQL examples live in external files rather than inline, leaving minor gaps versus the copy-paste-ready 5 anchor. | 4 / 5 |
Workflow Clarity | The semantic-layer workflow is a clearly numbered 5-step sequence with explicit validation gates (empty-catalog / unknown-table handling, approved+non-drifted check, user-confirmation gate before metric-create), but it lacks explicit validate→fix→retry feedback loops, so it lands at 4 rather than 5. | 4 / 5 |
Progressive Disclosure | The structure is well-signaled with one-level-deep categorized reference links (Data Schema, HogQL References, Analytics Query Examples), but the ./references/*.md files do not exist in the bundle, so the ~30 referenced paths are broken and navigation is non-functional — a real gap that pulls it down from the 4/5 anchors despite good organization. | 3 / 5 |
Total | 15 / 20 Passed |