From amplitude
Analyzes Amplitude charts to explain trends, anomalies, spikes, drops, and drivers via segmentation, experiments, deployments, and feedback insights.
npx claudepluginhub amplitude/mcp-marketplace --plugin amplitudeThis skill uses the workspace's default tool permissions.
- A metric spiked or dropped unexpectedly
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Builds scalable data pipelines, modern data warehouses, and real-time streaming architectures using Spark, dbt, Airflow, Kafka, and cloud platforms like Snowflake, BigQuery.
Builds production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. For data pipelines, workflow orchestration, and batch job scheduling.
Amplitude:getting_data_from_url to extract the chart IDCapture and restate:
Use Analyzing chart to characterize what’s happening:
Explicitly identify:
Instead of broad slicing, use guided segmentation:
Amplitude:query_chartsAvoid testing more than 9 properties in aggregate unless the user explicitly asks for deeper exploration.
For spikes, drops, or unexpected shifts, gather contextual signals in the same timeframe:
Amplitude:get_feedback_insights to search customer feedback trends that might explain the changeAmplitude:get_feedback_mentions to pull in specific customer mentions if there's a likely feedback trend tied to what's being explained.Determine whether any contextual changes align temporally with the chart pattern.
Present a structured, decision-ready analysis:
What Happened
Clear description of the observed pattern and magnitude
When
Exact timeframe and comparison baseline
Primary Hypothesis
Most likely explanation based on chart data and contextual signals
Supporting Evidence
Alternative Explanations
1–3 plausible alternatives and why they are less likely
Impact
Quantify impact where possible (users, events, conversion, revenue proxy)
Recommended Next Step
One clear follow-up action (e.g. deeper segment, experiment review, instrumentation check)
Always include: