diagnose-errors

Diagnoses product errors by correlating network failures, JavaScript errors, and error clicks in Amplitude.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/amplitude/amplitude-copilot-plugin --skill diagnose-errors-amplitude
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose-errors
Source: https://github.com/amplitude/amplitude-copilot-plugin/tree/main/skills/plugins/amplitude/diagnose-errors
Command: npx skills add https://github.com/amplitude/amplitude-copilot-plugin --skill diagnose-errors-amplitude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When users report that something is broken or error rates spike, teams need to quickly identify what failed, which users are affected, and why. This Skill triages errors across Amplitude's three auto-captured error events to surface root causes instead of isolated symptoms. ## Core Features & Use Cases - Cross-Event Correlation: Links failed network requests, JavaScript errors, and error clicks by page path to reveal causal chains such as a 500 response triggering a TypeError that users then click on. - Impact Quantification: Counts affected users, segments errors by platform or plan tier, and classifies severity from Critical to Low based on user impact percentages. - Root Cause Hypothesis: Correlates error spikes with deployments, experiments, and customer feedback, then attaches session replay links for visual confirmation. - Use Case: After a deploy, ask what broke. The Skill compares pre- and post-deploy error volumes, identifies new error messages, maps them to failing API endpoints, and delivers a triage report with replay links and recommended fixes. ## Quick Start Ask your AI assistant to investigate what's broken in your Amplitude project over the last 7 days and rank the top errors by user impact.

Frequently Asked Questions about diagnose-errors

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find what's causing errors in my product analytics?

Query the three auto-captured Amplitude events — Network Request, Error Logged, and Error Click — and group them by page path. Pages showing all three signals reveal full causal chains from failed API calls to user-facing errors.

How to investigate an error spike after a deployment?

Compare error volumes in the window before the deploy against the period after it, then isolate error messages that appear only in the new window. Cross-reference with deployment timestamps to confirm the regression source.

Does this work without Amplitude Session Replay enabled?

No. The network request, error logged, and error click events require Session Replay or the autocapture plugin. Without them, the Skill reports that these events are missing and suggests checking the SDK configuration.

Can I investigate a specific error message like a TypeError?

Yes. Filter the Error Logged event by Error Message or Error Type, then group by file name and page path. The Skill skips the broad landscape scan and goes directly to the targeted error with correlated network failures.

What is the difference between diagnose-errors and monitor-reliability?

Diagnose-errors is reactive: it investigates a known signal like a spike or complaint. Monitor-reliability is proactive, continuously watching error rates to catch problems before users report them.