Command
Audits the dashboard estate in a project: identifies stale (not touched in a long time), duplicate, empty, and sparse boards. Recommends archive or delete.
Command
Audits the dashboard estate in a project: identifies stale (not touched in a long time), duplicate, empty, and sparse boards. Recommends archive or delete.
Command
Creates a new dashboard from a natural language description.
Command
Lists all dashboards in a project with report counts, ownership, and metadata. Produces a governance-ready catalog. Read-only.
Command
Creates a copy of an existing dashboard within the same project. Optionally renames and updates the description.
Command
Reproduces a reference dashboard in another project, renames it, and optionally updates the description. This is the core enabler for standardized onboarding dashboard templates across accounts.
Command
Modifies an existing dashboard's metadata, rows, or cell layout. The most flexible command — it handles renames, description edits, adding/removing rows, reordering rows, and updating cell content.
Command
Design a Mixpanel experiment before launch. A well-designed experiment starts from the hypothesis and works backward: the hypothesis dictates the metrics that test it, the metrics dictate the sample size, the sample size + traffic dictate duration and testing model. This command stops at DRAFT — the irreversible…
Command
Interpret a Mixpanel experiment's results and health checks. This command consumes the verdicts the platform already returns. Never recompute thresholds (SRM, significance, sufficient-exposures, etc.). If a verdict field is missing, say so — do not synthesize one from raw values.
Command
Launch a designed Mixpanel experiment. This is the irreversible transition from DRAFT to ACTIVE — once exposures start, variants are locked, the statistical model is fixed, and mid-flight configuration changes invalidate the test. This command exists to give that transition a deliberate seam.
Command
Mid-flight safety checks on a running experiment. This command answers "is it safe to keep this experiment running?" — distinct from interpret, which answers "did the experiment work?" Monitor is for the middle of the experiment, before there's enough signal to interpret. Peek only at what's safe to peek at; surface…
Command
Auto-generate display names, descriptions, and tags for events and properties that are missing them. One combined preview, one confirmation, then three sequential write groups: events → tags → properties. Execute silently.
Command
Rename or delete existing Lexicon tags. Execute silently.
Command
Clear descriptions, display names, and/or tags from events and properties. Destructive — always preview, then require literal CONFIRM before any writes. Execute silently.
Command
Fetch open data quality issues, triage by severity, produce a prioritised report. Execute silently.
Command
Audit Lexicon metadata coverage and compute a health score (0–100). Self-contained pipeline: fetch → audit → score → report. Execute silently — no phase announcements.
Command
Detect point-in-time anomalies in a single metric — recent spikes, drops, and clusters. Produces a verdict on whether something unusual happened at a specific moment. Does not test for trend-level drift (run metric-drift for that).
Command
Detect trend-level drift in a single metric — whether the baseline itself has shifted over recent weeks. Produces a verdict on whether the metric is in a new regime. Does not test for point-in-time anomalies (run metric-anomaly for that).
Command
Root-cause investigation for a flagged metric. Takes the diagnosis payload from a prior metric-anomaly or metric-drift run and fans out across a set of segmentation branches to localise where the movement concentrated. Produces a ranked list of findings and appends them to the diagnosis board the user already created.
Command
Set up the Lexicon metadata the agent needs to understand the data itself: event descriptions, property descriptions, and tags. This command delegates to the manage-lexicon skill run inline — it does not reimplement enrichment. Its job is to hand off cleanly and capture the result for the unified readiness status.
Command
Pull business knowledge the customer has already written down and turn it into template-conformant context, then write on CONFIRM. This is the preferred starting path — most customers have something already, and adapting it beats a cold interview.
Command
Build business context from scratch via a guided interview, when the customer has nothing written down to import. Pulls schema facts first to make questions concrete, drafts to the fixed template, previews with a diff, and writes on CONFIRM. Handles org level, project level, or both.
Command
The unified AI-readiness readout. Scores both layers in one view — business context completeness and Lexicon coverage — and tells the user exactly what's missing and which command fixes it. This is the re-engagement hook: run it on any account to see where it stands and what to do next. It is read-only.
Command
Change which level(s) the skill writes business context to: org-level, project-level, or both.