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.

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%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 tight, expert-aimed skill body: concrete executable guidance, a clearly sequenced workflow with a validation checkpoint, and well-structured progressive disclosure via a single real reference file. Nothing essential is missing and nothing is padded.

DimensionReasoningScore

Conciseness

Lean and dense with domain-specific rules (PR-number attribution, Nullable JSON unwrapping, stale-conclusion watermarks); assumes Claude's competence and explains nothing basic, so every token earns its place.

5 / 5

Actionability

Provides concrete MCP tool names, a complete copy-paste-ready insight-create JSON payload, specific HogQL functions, and a referenced recipes file with executable SQL covering the common cases.

5 / 5

Workflow Clarity

Clear four-step sequence (discover → write/test → save → subscribe) with an explicit validation checkpoint ('Test the query with the execute-sql MCP tool… before saving anything') gating save/subscribe actions.

5 / 5

Progressive Disclosure

Body is a well-organized overview with a single one-level-deep, clearly signaled reference to the real references/hogql-recipes.md file where the bulk SQL lives; content is appropriately split for easy navigation.

5 / 5

Total

20

/

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, specific description that pairs concrete actions with a rich set of natural user trigger phrases and explicit boundary guidance against neighboring skills. It cleanly answers both what and when without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (discovering warehouse tables via engineering-analytics-sources, replicating HogQL semantics, reading engineering_analytics_* views, saving with insight-create, scheduling with subscriptions-create) — comprehensive coverage matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers both 'what' (converts engineering analytics into insights/dashboards/subscriptions and explains direct SQL querying) and 'when' with concrete trigger phrases, matching the score-5 anchor exactly.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases quoted verbatim ('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'), covering synonyms and variations a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers; explicitly disambiguates from diagnosing-ci-and-merge-bottlenecks and investigating-ci-failures, minimizing wrong-skill triggering.

5 / 5

Total

20

/

20

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.