posthog-analytics
PostHog analytics, event tracking, feature flags, dashboards
38
37%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/posthog-analytics/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is a bare comma-separated list of capability areas without concrete actions or explicit trigger guidance. While 'PostHog' provides some distinctiveness, the lack of a 'Use when...' clause and the absence of specific verbs or actions significantly weaken its utility for skill selection among many options.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user mentions PostHog, product analytics, event tracking setup, feature flag configuration, or building PostHog dashboards.'
Replace the noun list with concrete action phrases, e.g., 'Configures PostHog event tracking, creates and manages feature flags, builds analytics dashboards, and sets up funnels and cohorts.'
Include common related terms users might say, such as 'A/B testing', 'experiments', 'funnels', 'cohorts', 'product analytics', or 'user behavior tracking'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (PostHog) and lists some capabilities (analytics, event tracking, feature flags, dashboards), but these are more like category labels than concrete actions. It doesn't describe specific actions like 'create dashboards', 'configure feature flags', or 'instrument event tracking'. | 2 / 3 |
Completeness | It partially answers 'what does this do' with a list of capability areas, but there is no 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak enough to warrant a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'PostHog', 'analytics', 'event tracking', 'feature flags', and 'dashboards' that users might naturally mention. However, it's missing common variations and related terms like 'A/B testing', 'experiments', 'funnels', 'user analytics', or 'product analytics'. | 2 / 3 |
Distinctiveness Conflict Risk | 'PostHog' is a distinctive product name that helps differentiate this skill, but terms like 'analytics', 'dashboards', and 'feature flags' are generic enough to potentially overlap with other analytics or feature flag skills (e.g., LaunchDarkly, Mixpanel, Grafana). | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with comprehensive, executable code examples across multiple frameworks and use cases. However, it is severely over-long and monolithic—much of the content (dashboard templates, multi-framework installation, event catalogs) should be split into separate reference files. The philosophy section and extensive dashboard checklists add bulk without adding value for Claude, who already understands analytics concepts.
Suggestions
Split dashboard templates (SaaS, E-Commerce, Content, AI/LLM) into separate reference files (e.g., DASHBOARDS_SAAS.md) and link from the main skill with a brief summary table.
Reduce installation to one primary framework (e.g., Next.js) inline, and move other frameworks (React, Python, Node.js) to a separate INSTALLATION.md reference file.
Remove the Philosophy section entirely—Claude already understands analytics principles—and trim the event naming convention to just the format rule and 2-3 examples.
Add a validation step after initial setup (e.g., 'Verify events appear in PostHog Live Events view before proceeding to dashboard creation') to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~600+ lines. It explains basic concepts Claude already knows (what analytics questions to ask, what a SaaS dashboard is), includes extensive dashboard checklists that are more product management templates than actionable instructions, and provides installation boilerplate for 4 different frameworks when 1-2 with a note would suffice. The philosophy section and dashboard template sections are particularly padded. | 1 / 3 |
Actionability | The code examples are fully executable and copy-paste ready across multiple frameworks (Next.js, React, Python, Node.js). Event tracking patterns include concrete naming conventions with good/bad examples, and the feature flag, testing, and privacy sections all contain working code. | 3 / 3 |
Workflow Clarity | The MCP dashboard creation workflow has a clear sequence (check existing → create dashboard → create insights → add to dashboard), but lacks validation checkpoints. There's no verification step after event tracking setup (e.g., confirming events appear in PostHog), and the overall document reads more as a reference catalog than a guided workflow. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files to offload content to. The dashboard templates for 4+ project types, installation guides for 4 frameworks, and extensive event catalogs should be split into separate reference files. Everything is inline with no references to supporting documents. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (957 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- alinaqi/claude-bootstrap
- Commit
7e5f7a2
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.