monitor-metrics

Installation
SKILL.md

Monitor Metrics

Engine required — resolve an engine per ENGINE.md: one named in the conversation or loaded instructions is mandatory (not set up → offer /mixpanel:install for it); otherwise use the Mixpanel MCP server, or offer /mixpanel:install if it's unavailable.

A focused diagnostic skill for a single metric at a time. Works for any project the user has access to. Requires a Mixpanel engine. Answers three questions cleanly:

  1. Is a recent point weird? (anomaly detection — metric-anomaly)
  2. Has the baseline itself shifted? (drift detection — metric-drift)
  3. Where is the movement coming from? (root-cause attribution — metric-rca)

Separation matters because the customer conversation is different for each: an anomaly is an incident, drift is a trend, and RCA is the segmentation story that makes either of the first two actionable.

metric-rca runs on top of an existing anomaly or drift diagnosis — it consumes the diagnosis payload, fans out across segmentation branches, and appends its findings to the diagnosis board. It does not perform detection itself.


Commands

This skill has three commands. Route to the right one based on the user's ask.

Installs
15
GitHub Stars
18
First Seen
Jul 26, 2026