Build And Verify
timeplus-io/proton
Build, compile, run server/client/cluster, execute unit/stateless/SQL tests, verify results, and troubleshoot build/test failures.
Converts engineering analytics (PR / CI) data into saved PostHog insights, dashboards, and subscriptions, and explains how to query the product data directly with SQL.
Install Turning Engineering Analytics Into Insights
$ npx skills add PostHog/posthog --skill turning-engineering-analytics-into-insights -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog turning-engineering-analytics-into-insights --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/engineering_analytics/skills/turning-engineering-analytics-into-insights .claude/skills/turning-engineering-analytics-into-insights && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "turning-engineering-analytics-into-insights" agent skill from https://github.com/PostHog/posthog/tree/master/products/engineering_analytics/skills/turning-engineering-analytics-into-insights into .claude/skills/turning-engineering-analytics-into-insights/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "turning-engineering-analytics-into-insights", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PostHog/posthog/tree/master/products/engineering_analytics/skills/turning-engineering-analytics-into-insightsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PostHog/posthog --skill turning-engineering-analytics-into-insights -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog turning-engineering-analytics-into-insights --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/products/engineering_analytics/skills/turning-engineering-analytics-into-insights .agents/skills/turning-engineering-analytics-into-insights && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "turning-engineering-analytics-into-insights" agent skill from https://github.com/PostHog/posthog/tree/master/products/engineering_analytics/skills/turning-engineering-analytics-into-insights into .agents/skills/turning-engineering-analytics-into-insights/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "turning-engineering-analytics-into-insights", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill turning-engineering-analytics-into-insights -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog turning-engineering-analytics-into-insights --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/products/engineering_analytics/skills/turning-engineering-analytics-into-insights .cursor/skills/turning-engineering-analytics-into-insights && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "turning-engineering-analytics-into-insights" agent skill from https://github.com/PostHog/posthog/tree/master/products/engineering_analytics/skills/turning-engineering-analytics-into-insights into .cursor/skills/turning-engineering-analytics-into-insights/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "turning-engineering-analytics-into-insights", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PostHog/posthog.git --path products/engineering_analytics/skills/turning-engineering-analytics-into-insights--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PostHog/posthog --skill turning-engineering-analytics-into-insights -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog turning-engineering-analytics-into-insights --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/products/engineering_analytics/skills/turning-engineering-analytics-into-insights .gemini/skills/turning-engineering-analytics-into-insights && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "turning-engineering-analytics-into-insights" agent skill from https://github.com/PostHog/posthog/tree/master/products/engineering_analytics/skills/turning-engineering-analytics-into-insights into .gemini/skills/turning-engineering-analytics-into-insights/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "turning-engineering-analytics-into-insights", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PostHog/posthog turning-engineering-analytics-into-insightsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PostHog/posthog --skill turning-engineering-analytics-into-insights -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .github/skills && cp -r skills-src/products/engineering_analytics/skills/turning-engineering-analytics-into-insights .github/skills/turning-engineering-analytics-into-insights && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "turning-engineering-analytics-into-insights" agent skill from https://github.com/PostHog/posthog/tree/master/products/engineering_analytics/skills/turning-engineering-analytics-into-insights into .github/skills/turning-engineering-analytics-into-insights/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "turning-engineering-analytics-into-insights", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill turning-engineering-analytics-into-insights -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog turning-engineering-analytics-into-insights --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/products/engineering_analytics/skills/turning-engineering-analytics-into-insights .opencode/skills/turning-engineering-analytics-into-insights && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "turning-engineering-analytics-into-insights" agent skill from https://github.com/PostHog/posthog/tree/master/products/engineering_analytics/skills/turning-engineering-analytics-into-insights into .opencode/skills/turning-engineering-analytics-into-insights/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "turning-engineering-analytics-into-insights", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
turning-engineering-analytics-into-insights- GitHub stars
- 40k
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,189 words
- Files
- 2 (incl. references)
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Converts engineering analytics (PR / CI) data into saved PostHog insights, dashboards, and subscriptions, and explains how to query the product data directly with SQL.
- Works in 4 steps: discover the team's tables → write HogQL that carries the curated… → save it as an insight → …
- Asked to save this as an insight
- SKILL.md covers Step 1: discover the team's…, Step 2: write HogQL that…, Step 3: save it as an insight and Step 4: subscribe, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Turning Engineering Analytics Into Insights is an agent skill from PostHog/posthog, published by the product's own GitHub organization. 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 engineeringanalytics warehouse views where product logic is involved (CI cost, fingerprinted failure lines, commit attribution), saving queries with insight-create, and scheduling delivery with…
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/hogql-recipes.md`).
It sits in Testing & QA, covering Failing and flaky tests and SQL. It works with PostHog, GitHub and SQL. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…
When your agent uses it
- Asked to save this as an insight
- Put CI health / merge times on a dashboard
- Email me PR throughput weekly
- Track time to first review
Example prompts
- “save this as an insight”
- “put CI health / merge times on a dashboard”
- “email me PR throughput weekly”
- “/turning-engineering-analytics-into-insights”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- discover the team's tables
- write HogQL that carries the curated semantics
- save it as an insight
- subscribe
What it can do on your machine
Read from SKILL.md and the folder at commit 812e5c6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Turning Engineering Analytics Into Insights loads about 2.9k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 254 tokens; SKILL.md has 1,189 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,189 words (~2,878 tokens).
“The engineering analytics dashboard and MCP tools (pull-requests, workflow-health, pr-lifecycle, engineering-analytics-broken-tests, …) run curated HogQL privately: nothing in the UI or the tool output names the underlying tables, and the endpoints cannot themselves be saved as insights or subscribed to…”
- name
- turning-engineering-analytics-into-insights
Files
SKILL.md and 1 other file (references) in products/engineering_analytics/skills/turning-engineering-analytics-into-insights of PostHog/posthog.
- SKILL.md
- references/hogql-recipes.md
Open the folder on GitHubat commit 812e5c6
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Turning Engineering Analytics Into Insights next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Turning Engineering Analytics Into Insights this skillPostHog/posthog | 40k | — | ~2.9k | Automated safety check: Pass | Custom licence | |
| Build And Verifytimeplus-io/proton | 2.3k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Close Flaky IssuesClickHouse/ClickHouse | 50k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Migrating Oracle To Postgres Stored Proceduresgithub/awesome-copilot | 40k | — | ~788 | Automated safety check: Pass | MIT | |
| Migrating Oracle To Postgres Stored Proceduresboshi-xixixi/TraeSkill | 275 | — | ~576 | Automated safety check: Pass | MIT | |
| Dinobase Business Data Querieskappa90/dinobase | 263 | — | ~1.5k | Automated safety check: Pass | Custom licence |
Similar skills
Close Flaky Issues
ClickHouse/ClickHouse
Audit open "flaky test" GitHub issues and close those whose tests are no longer failing on master.
- Official
Migrating Oracle To Postgres Stored Procedures
github/awesome-copilot
Migrates Oracle PL/SQL stored procedures to PostgreSQL PL/pgSQL.
Migrating Oracle To Postgres Stored Procedures
boshi-xixixi/TraeSkill
Migrates Oracle PL/SQL stored procedures to PostgreSQL PL/pgSQL.
Dinobase Business Data Queries
kappa90/dinobase
Sets up Dinobase, a local DuckDB database that syncs data from 100+ business sources, then answers questions across them with SQL joins and previewed write-backs.
Forge Project Init
yaomindong1996/forge-admin
Bootstrap a new project from this Forge template end to end, or reset a Forge database into a clean template system.
More from PostHog/posthog
All 252 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
- Official
Exploring Apm Traces
PostHog/posthog
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Categories
Questions about Turning Engineering Analytics Into Insights
What does Turning Engineering Analytics Into Insights do?
Converts engineering analytics (PR / CI) data into saved PostHog insights, dashboards, and subscriptions, and explains how to query the product data directly with SQL. Turning Engineering Analytics Into Insights is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Converts engineering analytics (PR / CI) data into saved PostHog insights, dashboards, and subscriptions, and explains how to query the product data directly with SQL.
When should I use Turning Engineering Analytics Into Insights?
Turning Engineering Analytics Into Insights fits situations like: asked to save this as an insight; put CI health / merge times on a dashboard; email me PR throughput weekly; track time to first review.
How do I install Turning Engineering Analytics Into Insights in Claude Code?
Run `npx skills add PostHog/posthog --skill turning-engineering-analytics-into-insights -a claude-code`. Or copy the skill folder (products/engineering_analytics/skills/turning-engineering-analytics-into-insights in PostHog/posthog) into .claude/skills/turning-engineering-analytics-into-insights in your project. Claude Code loads it when a task matches its description.
How do I install Turning Engineering Analytics Into Insights in Codex?
Run `npx skills add PostHog/posthog --skill turning-engineering-analytics-into-insights -a codex`. Or copy the skill folder (products/engineering_analytics/skills/turning-engineering-analytics-into-insights in PostHog/posthog) into .agents/skills/turning-engineering-analytics-into-insights in your project. Codex loads it when a task matches its description.
Can I use Turning Engineering Analytics Into Insights in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog --skill turning-engineering-analytics-into-insights -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/turning-engineering-analytics-into-insights, .gemini/skills/turning-engineering-analytics-into-insights, .github/skills/turning-engineering-analytics-into-insights and .opencode/skills/turning-engineering-analytics-into-insights in your project.
What does Turning Engineering Analytics Into Insights need to run?
SKILL.md names no scripts, command-line tools or credentials: Turning Engineering Analytics Into Insights is instructions for the agent only.
Does Turning Engineering Analytics Into Insights access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Turning Engineering Analytics Into Insights safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Turning Engineering Analytics Into Insights use?
Turning Engineering Analytics Into Insights has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Turning Engineering Analytics Into Insights use?
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.
What are the alternatives to Turning Engineering Analytics Into Insights?
Skills that share tags, products or a category with Turning Engineering Analytics Into Insights: Build And Verify (timeplus-io/proton, 2.3k stars), Close Flaky Issues (ClickHouse/ClickHouse, 50k stars), Migrating Oracle To Postgres Stored Procedures (github/awesome-copilot, 40k stars) and Migrating Oracle To Postgres Stored Procedures (boshi-xixixi/TraeSkill, 275 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Turning Engineering Analytics Into Insights?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,200 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 9, 2026.
Source: PostHog/posthog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.