CtrlK
BlogDocsLog inGet started
Tessl Logo

analyzing-insights-across-teams

Analyze PostHog insights, dashboards, or teams beyond the current project by querying the prod Postgres replicas synced into the dogfood data warehouse (US project 2, "PostHog App + Website"). Use when asked to analyze insights across all teams or projects, another team's insights, or fleet-wide insight/dashboard usage — cases where `system.insights` only returns the current project's rows and the agent would otherwise report the data as inaccessible. Covers the synced table names for US and EU and the column-verification workflow.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured body that gives executable SQL, a sequenced workflow with verification and error handling, and clear output-handling constraints — all without padding or restating concepts Claude already knows.

DimensionReasoningScore

Conciseness

Lean and efficient: it assumes Claude knows what PostHog/Postgres are and adds only the non-obvious internal facts (dogfood replication, scoped `system.insights`), with every section earning its place.

3 / 3

Actionability

Provides fully executable SQL (catalog lookup, column verification, analysis query) with concrete table names, the `posthog:execute-sql` tool, and specific filters like `team_id` and `NOT deleted AND saved` — copy-paste ready.

3 / 3

Workflow Clarity

A clear 3-step sequence with an explicit verification gate ("Confirm columns before projecting — synced schemas drift") and an error-recovery checkpoint (permissions error → report and stop); appropriate validation for a read-only analysis flow.

3 / 3

Progressive Disclosure

Self-contained and well-organized into focused sections (Synced tables, Workflow, Output handling, Related) with no nested references; the single Related pointer to `query-clickhouse-via-metabase` is a clear one-level cross-reference.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that answers what the skill does and precisely when to use it, with natural trigger terms and a clearly distinct niche. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Analyze PostHog insights, dashboards, or teams", "querying the prod Postgres replicas", and "the column-verification workflow" — rather than vague language.

3 / 3

Completeness

Clearly states what it does (analyze cross-team insights via replicated Postgres tables) and has an explicit "Use when..." trigger, satisfying both halves the rubric requires.

3 / 3

Trigger Term Quality

The "Use when asked to analyze insights across all teams or projects, another team's insights, or fleet-wide insight/dashboard usage" clause covers natural phrasings a PostHog user would actually say.

3 / 3

Distinctiveness Conflict Risk

The niche is highly specific (dogfood warehouse cross-team queries) with a distinct trigger — "cases where `system.insights` only returns the current project's rows" — making conflict with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
PostHog/posthog
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.