Content
82%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 highly actionable, well-structured reference with executable JSON and SQL recipes and a valuable Gotchas section. The main gaps are mild trigger-phrase redundancy with the description and all content living inline despite the skill exceeding 50 lines.
Suggestions
Trim the "When to use this skill" bullet list, since its trigger phrasing largely duplicates the description's "Use when..." clause.
Consider moving the "Adding a bot PostHog doesn't know yet" and "Seeing bots that don't run JavaScript" sections into one-level-deep reference files (e.g. references/custom-bot-rules.md) and linking from the body.
Add an explicit validate-fix-retry sequence for custom bot rule creation (e.g. list rules, create, confirm the pattern compiled, iterate) rather than relying solely on PostHog's save-time rejection.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and largely assumes Claude's competence (no padding about what PostHog or a user agent is), but the intro bullets and "When to use this skill" section partly restate trigger phrasing already in the description, a minor redundancy that could be trimmed. | 4 / 5 |
Actionability | Provides copy-paste-ready JSON filter objects, exact HogQL function signatures, and complete SQL recipes using the coalesce(nullIf(...)) pattern, covering the common cases (exclude, measure share, identify bots, AI-agent specifically). | 5 / 5 |
Workflow Clarity | Recipes are sequenced by surface (virtual properties vs functions) and the mutating bot-rule section notes save-time rejection as a validation safeguard; the core analytics work is read-only so a destructive feedback loop is not required, but the rule-creation path lacks an explicit validate-fix-retry checklist. | 4 / 5 |
Progressive Disclosure | Well-organized with clear section headers and no nested references, but at ~200 lines all content is inline with no bundle files; secondary topics (custom bot rules, JS-less bots) could arguably live in one-level-deep reference files. | 4 / 5 |
Total | 17 / 20 Passed |