Name: analyzing-insights-across-teams
Rating: 71.2 (1 reviews)
Author: PostHog

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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%Weight 40%Scale 1-5

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

A lean, actionable skill body with copy-paste SQL, a clear sequenced workflow, and sensible output-handling guardrails. The only weak spot is the absence of an explicit retry feedback loop and a little trimmable administrative prose.

Suggestions

Add an explicit validate-then-retry loop for the column-verification step (e.g., 'if a needed column is absent, fall back to the catalog query before proceeding') to reach the top workflow_clarity anchor.

Tighten the repo-local paragraph and remove the restated 'Do not stop at system.insights' sentence to push conciseness toward the lean anchor.

Optionally split the catalog and column-verification SQL into a reference file to keep the core workflow even tighter, though the current single-file organization is already strong.

Dimension	Reasoning	Score
Conciseness	The body is dense and information-rich, avoiding explanations of concepts Claude already knows, but the repo-local administrative paragraph and the restated 'Do not stop at `system.insights`' line could be trimmed, so it sits just below the lean top anchor.	4 / 5
Actionability	Provides fully executable, copy-paste-ready SQL for catalog discovery, column verification, and a concrete analytics example with specific table names and filters, covering the common cases.	5 / 5
Workflow Clarity	A clear three-step sequence with a validation checkpoint (confirm columns before projecting) and a permissions-error stop rule, but it lacks an explicit validate-fix-retry feedback loop, leaving a minor gap below the top anchor.	4 / 5
Progressive Disclosure	A single-purpose skill with no external bundle files, well-organized into clear sections (Synced tables, Workflow, Output handling, Related) and one cleanly signaled one-level cross-reference to another skill, matching the simple-skill exception.	5 / 5
	Total	18 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 clearly states both capability and trigger conditions with concrete domain language. Minor room to sharpen the lead verb and add a few more synonyms, but it cleanly avoids vagueness and overlap.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Analyze PostHog insights, dashboards, or teams', 'querying the prod Postgres replicas synced into the dogfood data warehouse', 'column-verification workflow' — but the lead verb 'Analyze' stays somewhat abstract compared to fully concrete verbs, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Analyze PostHog insights, dashboards, or teams beyond the current project by querying the prod Postgres replicas') and when ('Use when asked to analyze insights across all teams or projects...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say — 'analyze insights across all teams or projects', 'another team's insights', 'fleet-wide insight/dashboard usage' — with good keyword coverage, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (cross-team querying of synced prod Postgres replicas in the dogfood warehouse) with distinct triggers and explicit contrast against `system.insights`, giving minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: PostHog/posthog
Path: .agents/skills/analyzing-insights-across-teams/SKILL.md
Commit: 6fca5f8

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.