Analytics Product
sickn33/agentic-awesome-skills
Analytics de produto — PostHog, Mixpanel, eventos, funnels, cohorts, retencao, north star metric, OKRs e dashboards de produto.
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Install Investigate Metric
$ npx skills add PostHog/posthog --skill investigate-metric -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog investigate-metric --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/product_analytics/skills/investigate-metric .claude/skills/investigate-metric && 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 "investigate-metric" agent skill from https://github.com/PostHog/posthog/tree/master/products/product_analytics/skills/investigate-metric into .claude/skills/investigate-metric/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigate-metric", 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/product_analytics/skills/investigate-metricType 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 investigate-metric -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog investigate-metric --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/product_analytics/skills/investigate-metric .agents/skills/investigate-metric && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "investigate-metric" agent skill from https://github.com/PostHog/posthog/tree/master/products/product_analytics/skills/investigate-metric into .agents/skills/investigate-metric/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigate-metric", 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 investigate-metric -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog investigate-metric --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/product_analytics/skills/investigate-metric .cursor/skills/investigate-metric && 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 "investigate-metric" agent skill from https://github.com/PostHog/posthog/tree/master/products/product_analytics/skills/investigate-metric into .cursor/skills/investigate-metric/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigate-metric", 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/product_analytics/skills/investigate-metric--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 investigate-metric -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog investigate-metric --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/product_analytics/skills/investigate-metric .gemini/skills/investigate-metric && 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 "investigate-metric" agent skill from https://github.com/PostHog/posthog/tree/master/products/product_analytics/skills/investigate-metric into .gemini/skills/investigate-metric/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigate-metric", 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 investigate-metricInstalls 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 investigate-metric -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/product_analytics/skills/investigate-metric .github/skills/investigate-metric && 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 "investigate-metric" agent skill from https://github.com/PostHog/posthog/tree/master/products/product_analytics/skills/investigate-metric into .github/skills/investigate-metric/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigate-metric", 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 investigate-metric -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 investigate-metric --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/product_analytics/skills/investigate-metric .opencode/skills/investigate-metric && 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 "investigate-metric" agent skill from https://github.com/PostHog/posthog/tree/master/products/product_analytics/skills/investigate-metric into .opencode/skills/investigate-metric/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigate-metric", 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
investigate-metric- GitHub stars
- 40k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 626 words
- Files
- 12 (incl. scripts, references)
- Skills in repo
- 254
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
- Works in 5 steps: Classify the metric → Common opening moves → Run the playbook → …
- The user reports an anomaly
- SKILL.md covers Tools, Helper scripts, Step 1 — Classify the metric and Step 2 — Common opening moves, plus 4 more sections
- Runs Python scripts from its folder; calls python3, kind and git
What it does
Investigate Metric is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries. Use when the user reports an anomaly, asks "why did X change?", or needs root-cause analysis for a trend, funnel, retention, stickiness, or lifecycle metric.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts and reference files (for example `references/box-plot-playbook.md`, `references/common-causes.md` and `references/funnel-playbook.md`).
It sits in Product & Project Management, covering Root cause analysis and Product metrics. It works with PostHog. 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
- The user reports an anomaly
- Asks why did X change?
- Needs root-cause analysis for a trend
- Lifecycle metric
Example prompts
- “why did X change?”
- “/investigate-metric”
Requirements
- Python 3
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Classify the metric
- Common opening moves
- Run the playbook
- Cross-check
- Write findings
What it can do on your machine
Read from SKILL.md and the folder at commit 9d4bb2f. 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
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3kindgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Investigate Metric loads about 1.9k tokens when it runs, and up to ~7.3k if it reads all its reference files. Until then it costs about 84 tokens; SKILL.md has 626 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); the scripts in this folder 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 626 words (~1,911 tokens).
“For "why did X change?" questions about a saved insight, dashboard tile, or pasted query. Don't load this skill for plain "what is X?" questions — only when there's an observed change to explain.”
- name
- investigate-metric
Files
SKILL.md and 11 other files (scripts, references) in products/product_analytics/skills/investigate-metric of PostHog/posthog.
- SKILL.md
- references/box-plot-playbook.md
- references/common-causes.md
- references/funnel-playbook.md
- references/lifecycle-playbook.md
- references/paths-playbook.md
- references/retention-playbook.md
- references/shared-patterns.md
- references/stickiness-playbook.md
- references/trend-playbook.md
- scripts/breakdown_attribution.py
- scripts/compare_to_prior_periods.py
Open the folder on GitHubat commit 9d4bb2f
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
Investigate Metric 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 |
|---|---|---|---|---|---|---|
| Investigate Metric this skillPostHog/posthog | 40k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Analytics Productsickn33/agentic-awesome-skills | 47k | 2 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Product Health Analysismohitagw15856/pm-claude-skills | 1.4k | — | ~1.5k | Automated safety check: Pass | MIT | |
| After Action Reportrampstackco/claude-skills | 945 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Counterexample ExplainerArabelaTso/Skills-4-SE | 253 | — | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| Swarmaglitch-rabin/swarma | 173 | — | ~4.4k | Automated safety check: Notes | MIT |
Similar skills
Product Health Analysis
mohitagw15856/pm-claude-skills
Interpret product metrics against goals and surface actionable signals.
After Action Report
rampstackco/claude-skills
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.
Counterexample Explainer
ArabelaTso/Skills-4-SE
Explain why counterexamples violate specifications by analyzing formal specifications (temporal logic, invariants, pre/postconditions, code contracts), informal requirements (user stories…
Swarma
glitch-rabin/swarma
Agent teams that run growth experiments and build their own playbook.
Management Consultant
DogInfantry/claude-skill-management-consultant-B1
MBB-level management consultant with mastery over structured thinking, frameworks, guesstimation, industry analysis, and executive-grade deliverables.
More from PostHog/posthog
All 254 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
QA Team
PostHog/posthog
Multi-agent QA review team for code changes. An agent skill from PostHog/posthog.
Related
Works with
Categories
Questions about Investigate Metric
What does Investigate Metric do?
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries. Investigate Metric is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
When should I use Investigate Metric?
Investigate Metric fits situations like: the user reports an anomaly; asks why did X change?; needs root-cause analysis for a trend; lifecycle metric.
How do I install Investigate Metric in Claude Code?
Run `npx skills add PostHog/posthog --skill investigate-metric -a claude-code`. Or copy the skill folder (products/product_analytics/skills/investigate-metric in PostHog/posthog) into .claude/skills/investigate-metric in your project. Claude Code loads it when a task matches its description.
How do I install Investigate Metric in Codex?
Run `npx skills add PostHog/posthog --skill investigate-metric -a codex`. Or copy the skill folder (products/product_analytics/skills/investigate-metric in PostHog/posthog) into .agents/skills/investigate-metric in your project. Codex loads it when a task matches its description.
Can I use Investigate Metric 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 investigate-metric -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/investigate-metric, .gemini/skills/investigate-metric, .github/skills/investigate-metric and .opencode/skills/investigate-metric in your project.
What does Investigate Metric need to run?
Going by SKILL.md and its folder, Investigate Metric needs Python for the scripts in its folder and the command-line tools its instructions call (python3, kind and git). Our summary lists: Python 3.
Does Investigate Metric access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Investigate Metric 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Investigate Metric use?
Investigate Metric 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 Investigate Metric use?
About 1.9k tokens (SKILL.md is roughly 7.6k 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 5.4k tokens, read only when the agent opens those files.
What are the alternatives to Investigate Metric?
Skills that share tags, products or a category with Investigate Metric: Analytics Product (sickn33/agentic-awesome-skills, 47k stars), Product Health Analysis (mohitagw15856/pm-claude-skills, 1.4k stars), After Action Report (rampstackco/claude-skills, 945 stars) and Counterexample Explainer (ArabelaTso/Skills-4-SE, 253 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Investigate Metric?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,219 GitHub stars. The repository holds 254 skills in this directory. The repository was last updated on October 11, 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.