querying-posthog-data — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited querying-posthog-data (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
The guidelines contain the same instructions as posthog:execute-sql. If you've already read posthog:execute-sql, you don't need to read them again.
When the user wants to find a specific entity created in PostHog (insights, dashboards, cohorts, feature flags, experiments, surveys, hog flows, data warehouse items, etc.), or when a list/search tool returns too many results to narrow down:
posthog:execute-sql to query the system table and find the matching entity (typically returning its ID).posthog:insight-get, posthog:dashboard-get) to retrieve the full entity by ID.Don't try to reconstruct the entity from SQL — execute-sql is for discovery, the read tool is for retrieval.
When the user wants analytics data (trends, funnels, retention, paths, sessions, LLM traces, web analytics, errors, logs, etc.) and the existing insight schemas don't fit the request:
posthog:execute-sql. If no example fit, compose the query from scratch using the Data Schema and HogQL References.Schema reference for PostHog's core system models, organized by domain:
posthog.trace_spans)heatmaps data + system.heatmaps_saved)posthog.ai_events)logs data plane + saved views and alerts)$mcp_tool_call events)posthog.metrics)$survey_dismissed/{id}, $feature/{key} that don't appear in tool resultsperson.properties.* to understand if values are historical or current.Use the examples below to create optimized analytical queries.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.