CtrlK
BlogDocsLog inGet started
Tessl Logo

turning-engineering-analytics-into-insights

Converts engineering analytics (PR / CI) data into saved PostHog insights, dashboards, and subscriptions, and explains how to query the product data directly with SQL. Covers discovering per-team GitHub warehouse tables via engineering-analytics-sources, replicating curated column semantics in HogQL, reading exposed engineering_analytics_* warehouse views where product logic is involved (CI cost, fingerprinted failure lines, commit attribution), saving queries with insight-create, and scheduling delivery with subscriptions-create. Use when asked to "save this as an insight", "put CI health / merge times on a dashboard", "email me PR throughput weekly", "chart CI cost", "track time to first review", "subscribe to these numbers", "alert on CI success rate", or "what data/tables/views does engineering analytics read". For ad-hoc CI and merge questions use diagnosing-ci-and-merge-bottlenecks; to investigate one specific CI failure use investigating-ci-failures.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The body is dense, domain-specific, and well-sequenced with a real validation checkpoint and a concrete insight-create example. Its main defect is a broken progressive-disclosure link: the hogql-recipes.md reference it leans on for the executable SQL is missing from the bundle.

Suggestions

Add the missing references/hogql-recipes.md (or inline the base HogQL subqueries) so the 'Copy the base subqueries' instruction resolves to real content.

Add an explicit feedback loop after the execute-sql test step (e.g., 'if the query errors or returns unexpected rows, fix the parse/attribution rules and re-test before saving').

Trim the overlap between the opening prose and the 'What the product shows' table to tighten token use.

DimensionReasoningScore

Conciseness

High-signal domain rules (prefix handling, curated views, attribution-by-PR-number, bot detection, honest naming) with no padding about concepts Claude already knows, though the prose intro and the data-location table overlap somewhat and could be tightened.

4 / 5

Actionability

Gives concrete tool names, a working insight-create JSON payload, and specific HogQL rules (parseDateTimeBestEffort, ifNull-unwrap, JSONExtractArrayRaw); the main gap is that the actual base subqueries are delegated to references/hogql-recipes.md, which is not present in the bundle.

4 / 5

Workflow Clarity

Clear four-step sequence (discover → write HogQL → save insight → subscribe) with an explicit validation checkpoint ('Test the query with the execute-sql MCP tool ... before saving anything'), though an explicit error-recovery feedback loop is only implied.

4 / 5

Progressive Disclosure

Structure is well-organized with a clearly signaled one-level-deep reference to references/hogql-recipes.md, but that referenced file does not exist in the bundle, so the navigation promise is broken — scoring against the actual (empty) bundle structure lowers it below 4.

3 / 5

Total

15

/

20

Passed

Description

100%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, third-person description that states concrete capabilities, gives a rich set of natural trigger phrases, and disambiguates against adjacent skills. It fully satisfies the what/when and distinctiveness criteria.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Converts engineering analytics ... into saved PostHog insights, dashboards, and subscriptions', 'discovering per-team GitHub warehouse tables', 'replicating curated column semantics in HogQL', 'saving queries with insight-create', 'scheduling delivery with subscriptions-create' — covering the domain comprehensively in third person.

5 / 5

Completeness

Explicitly answers both what (convert analytics into insights/dashboards/subscriptions, query via SQL) and when via a concrete 'Use when...' clause with many trigger phrases, matching the anchor example.

5 / 5

Trigger Term Quality

Packs in natural user phrasings — 'save this as an insight', 'put CI health / merge times on a dashboard', 'email me PR throughput weekly', 'chart CI cost', 'track time to first review', 'subscribe to these numbers', 'alert on CI success rate' — exactly what a user would say, with broad synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (engineering analytics → PostHog insights) and explicitly distinguishes sibling skills ('For ad-hoc CI and merge questions use diagnosing-ci-and-merge-bottlenecks; to investigate one specific CI failure use investigating-ci-failures'), minimizing wrong-skill triggering.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

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.