UModel Root Cause Analysis
alibaba/UnifiedModel
Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.
Investigates server/infrastructure metric anomalies in PostHog Metrics — from "this metric is rising/dropping/spiking" or a fired alert to a probable cause with evidence.
Install Investigating Metric Anomalies
$ npx skills add PostHog/posthog --skill investigating-metric-anomalies -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog investigating-metric-anomalies --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/metrics/skills/investigating-metric-anomalies .claude/skills/investigating-metric-anomalies && 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 "investigating-metric-anomalies" agent skill from https://github.com/PostHog/posthog/tree/master/products/metrics/skills/investigating-metric-anomalies into .claude/skills/investigating-metric-anomalies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-metric-anomalies", 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/metrics/skills/investigating-metric-anomaliesType 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 investigating-metric-anomalies -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog investigating-metric-anomalies --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/metrics/skills/investigating-metric-anomalies .agents/skills/investigating-metric-anomalies && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "investigating-metric-anomalies" agent skill from https://github.com/PostHog/posthog/tree/master/products/metrics/skills/investigating-metric-anomalies into .agents/skills/investigating-metric-anomalies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-metric-anomalies", 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 investigating-metric-anomalies -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog investigating-metric-anomalies --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/metrics/skills/investigating-metric-anomalies .cursor/skills/investigating-metric-anomalies && 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 "investigating-metric-anomalies" agent skill from https://github.com/PostHog/posthog/tree/master/products/metrics/skills/investigating-metric-anomalies into .cursor/skills/investigating-metric-anomalies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-metric-anomalies", 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/metrics/skills/investigating-metric-anomalies--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 investigating-metric-anomalies -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog investigating-metric-anomalies --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/metrics/skills/investigating-metric-anomalies .gemini/skills/investigating-metric-anomalies && 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 "investigating-metric-anomalies" agent skill from https://github.com/PostHog/posthog/tree/master/products/metrics/skills/investigating-metric-anomalies into .gemini/skills/investigating-metric-anomalies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-metric-anomalies", 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 investigating-metric-anomaliesInstalls 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 investigating-metric-anomalies -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/metrics/skills/investigating-metric-anomalies .github/skills/investigating-metric-anomalies && 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 "investigating-metric-anomalies" agent skill from https://github.com/PostHog/posthog/tree/master/products/metrics/skills/investigating-metric-anomalies into .github/skills/investigating-metric-anomalies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-metric-anomalies", 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 investigating-metric-anomalies -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 investigating-metric-anomalies --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/metrics/skills/investigating-metric-anomalies .opencode/skills/investigating-metric-anomalies && 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 "investigating-metric-anomalies" agent skill from https://github.com/PostHog/posthog/tree/master/products/metrics/skills/investigating-metric-anomalies into .opencode/skills/investigating-metric-anomalies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-metric-anomalies", 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
investigating-metric-anomalies- GitHub stars
- 40k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 750 words
- Files
- 1
- Skills in repo
- 254
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Investigates server/infrastructure metric anomalies in PostHog Metrics — from "this metric is rising/dropping/spiking" or a fired alert to a probable cause with evidence.
- Works in 5 steps: Pin down the metric → Characterize first — one call, three… → Sharpen with targeted metric queries → …
- Asked why a metric looks wrong (ingestion lag rising
- SKILL.md covers The loop, Worked example: "ingestion lag… and Pitfalls
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Investigating Metric Anomalies is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Investigates server/infrastructure metric anomalies in PostHog Metrics — from "this metric is rising/dropping/spiking" or a fired alert to a probable cause with evidence. Use when asked why a metric looks wrong (ingestion lag rising, error rate spiking, latency degrading, queue depth growing, throughput dropping), when an alert fires on an OTel/Prometheus metric, or for any incident triage that starts from a metric symptom. Composes characterize-metric-anomaly, query-metrics, and metric-names-list with logs…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Monitoring and alerting and Root cause analysis. It works with PostHog, OpenTelemetry and Prometheus. 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 why a metric looks wrong (ingestion lag rising
- Error rate spiking
- Latency degrading
- Queue depth growing
Example prompts
- “this metric is rising/dropping/spiking”
- “Use the investigating-metric-anomalies skill to investigate server/infrastructure metric anomalies in PostHog Metrics — from "this metric is…”
- “/investigating-metric-anomalies”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Pin down the metric
- Characterize first — one call, three answers
- Sharpen with targeted metric queries
- Correlate across signals at the onset
- Conclude with evidence, not vibes
What it can do on your machine
Read from SKILL.md and the folder at commit c012c8d. 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.
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
Investigating Metric Anomalies loads about 1.5k tokens when it runs. Until then it costs about 156 tokens; SKILL.md has 750 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 750 words (~1,483 tokens).
“The job: go from a metric symptom ("ingestion lag is rising") to a probable cause with evidence, fast. The metric tells you what and when; logs and traces tell you why. Follow the loop below — it front-loads the cheap…”
- name
- investigating-metric-anomalies
Files
Just SKILL.md in products/metrics/skills/investigating-metric-anomalies of PostHog/posthog.
Open the folder on GitHubat commit c012c8d
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
Investigating Metric Anomalies 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 |
|---|---|---|---|---|---|---|
| Investigating Metric Anomalies this skillPostHog/posthog | 40k | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| UModel Root Cause Analysisalibaba/UnifiedModel | 415 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Signozqjoly/GitOps | 112 | — | ~6.1k | Automated safety check: Pass | WTFPL | |
| Developing Funboost Mixinydf0509/funboost | 895 | — | ~2.1k | Automated safety check: Pass | None | |
| Archestra Dev Observabilityarchestra-ai/archestra | 4.4k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Frontmcp Observabilityagentfront/frontmcp | 146 | — | ~4.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Signoz
qjoly/GitOps
Manage the self-hosted SigNoz observability stack in this GitOps repo.
Developing Funboost Mixin
ydf0509/funboost
当需要为 funboost 创建 Consumer 或 Publisher 的 Mixin 扩展类时使用。触发场景：添加监控、熔断、限流、链路追踪等横切关注点，编写自定义前置/后置处理钩子。关键词：mixin, consumeroverridecls, publisheroverridecls, ConsumerMixin, 自定义消费者, hook, 拦截器, 熔断器, 监控…
Archestra Dev Observability
archestra-ai/archestra
A skill your agent uses when changing Archestra tracing, metrics, OpenTelemetry, Tempo, Grafana, Prometheus, LLM/MCP spans, observability labels, or local observability setup.
Frontmcp Observability
agentfront/frontmcp
A skill your agent uses when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server.
Monitoring Observability
ahmedasmar/devops-claude-skills
Monitoring and observability strategy, implementation, and troubleshooting.
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
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
Works with
Categories
Questions about Investigating Metric Anomalies
What does Investigating Metric Anomalies do?
Investigates server/infrastructure metric anomalies in PostHog Metrics — from "this metric is rising/dropping/spiking" or a fired alert to a probable cause with evidence. Investigating Metric Anomalies is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Investigates server/infrastructure metric anomalies in PostHog Metrics — from "this metric is rising/dropping/spiking" or a fired alert to a probable cause with evidence.
When should I use Investigating Metric Anomalies?
Investigating Metric Anomalies fits situations like: asked why a metric looks wrong (ingestion lag rising; error rate spiking; latency degrading; queue depth growing.
How do I install Investigating Metric Anomalies in Claude Code?
Run `npx skills add PostHog/posthog --skill investigating-metric-anomalies -a claude-code`. Or copy the skill folder (products/metrics/skills/investigating-metric-anomalies in PostHog/posthog) into .claude/skills/investigating-metric-anomalies in your project. Claude Code loads it when a task matches its description.
How do I install Investigating Metric Anomalies in Codex?
Run `npx skills add PostHog/posthog --skill investigating-metric-anomalies -a codex`. Or copy the skill folder (products/metrics/skills/investigating-metric-anomalies in PostHog/posthog) into .agents/skills/investigating-metric-anomalies in your project. Codex loads it when a task matches its description.
Can I use Investigating Metric Anomalies 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 investigating-metric-anomalies -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/investigating-metric-anomalies, .gemini/skills/investigating-metric-anomalies, .github/skills/investigating-metric-anomalies and .opencode/skills/investigating-metric-anomalies in your project.
What does Investigating Metric Anomalies need to run?
SKILL.md names no scripts, command-line tools or credentials: Investigating Metric Anomalies is instructions for the agent only.
Does Investigating Metric Anomalies 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 Investigating Metric Anomalies 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 Investigating Metric Anomalies use?
Investigating Metric Anomalies 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 Investigating Metric Anomalies use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Investigating Metric Anomalies?
Skills that share tags, products or a category with Investigating Metric Anomalies: UModel Root Cause Analysis (alibaba/UnifiedModel, 415 stars), Signoz (qjoly/GitOps, 112 stars), Developing Funboost Mixin (ydf0509/funboost, 895 stars) and Archestra Dev Observability (archestra-ai/archestra, 4.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Investigating Metric Anomalies?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,209 GitHub stars. The repository holds 254 skills in this directory. The repository was last updated on October 10, 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.