Conciseness

Every section carries non-derivable, repo-specific knowledge (synced table names, underscore aliases, sync lag, output rules) with no explanation of concepts Claude already knows; directives like "Do not stop at `system.insights` when the question spans teams" earn their tokens. This matches anchor 5 (lean, every token earns its place); it is not 4 because there is no over-explanation to trim.

Actionability

Three copy-paste-ready SQL blocks (catalog check via system.information_schema, column verification, a full example aggregate query), exact table names for US and EU, explicit `team_id` grouping, join guidance, and the concrete tool name `posthog:execute-sql`. This matches anchor 5 (fully executable, covers the common cases); it is not 4 because no key detail or executable step is missing.

Workflow Clarity

A numbered workflow with a pre-flight validation step ("Confirm columns before projecting — synced schemas drift with the Django models"), explicit failure handling ("If a query fails with a permissions error, report it and stop — do not look for another route"), a catalog-check fallback before declaring data inaccessible, and a sync-lag caveat. This matches anchor 5 (clear sequence, explicit validation, error-recovery paths); it is not 4 because checkpoints and failure behavior are explicit rather than implied.

Progressive Disclosure

No bundle files exist and nothing that belongs in a separate file is inlined; sections are well-organized (Synced tables, Workflow, Output handling, Related) and the one cross-reference (querying-production-databases-via-metabase) is clearly signaled. Per the simple-skill scoring note, a self-contained well-organized SKILL.md matches anchor 5; it is not 4 because there is no organization gap or buried content.

Specificity

"Analyze PostHog insights, dashboards, or teams beyond the current project by querying the prod Postgres replicas synced into the dogfood data warehouse" names concrete actions with their mechanism, and "Covers the synced table names for US and EU and the column-verification workflow" completes the coverage. It matches anchor 5 (multiple specific concrete actions, comprehensive coverage); it is not 4 because no capability is left as a generic hint.

Completeness

The what is explicit ("Analyze PostHog insights, dashboards, or teams... by querying the prod Postgres replicas") and the when is an explicit trigger clause ("Use when asked to analyze insights across all teams or projects, another team's insights, or fleet-wide insight/dashboard usage"). Both answered with concrete triggers matches anchor 5; the when is fully explicit, so 4 does not fit.

Trigger Term Quality

Natural user phrasings are all present: "analyze insights across all teams or projects", "another team's insights", "fleet-wide insight/dashboard usage", covering both region scopes. Comprehensive synonym coverage matches anchor 5; it is not 4 because no commonly used variation is missing.

Distinctiveness Conflict Risk

The niche is clear and delimited ("cases where `system.insights` only returns the current project's rows"), but a closely related sibling skill exists for cross-team analytics (querying-production-databases-via-metabase) and the description does not state the entity-metadata vs event-data boundary. That is anchor 4 (mostly distinct, minor overlap risk); not 5 because that boundary omission leaves a small chance of triggering the wrong skill.