Amplitude

Deep-dives into specific AI agent sessions or failure patterns to explain why something went wrong. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when investigating a specific session ID, debugging agent failures, understanding why quality is low, tracing tool errors, or when monitor-ai-quality surfaces an issue that needs root cause analysis.

Monitors all active and recently completed experiments across Amplitude projects, triages them by importance, then runs deep analysis and reporting on the most impactful ones. Use when the user asks to "check on experiments", "experiment status", "experiment review", "what experiments are running", or wants a periodic experiment health report.

Monitors AI agent health across quality, cost, performance, and errors. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when the user asks "how are our AI agents doing", "AI quality check", "agent health", "AI errors", "agent performance", "LLM cost", or wants a proactive health report on their AI/LLM features.

Lists projects for an employee-accessible organization or writes organization/project AI context with `manage_amp_context`; use `get_amplitude_context` for reads.

Investigates live product issues against Amplitude data — "is X firing today", "did the release break Y", "which users are affected by Z". Covers the verify-then-query loop, query_amplitude_data parameterization, and its common failure modes. Use for incident analysis, instrumentation checks, and affected-user discovery.

Creates, edits, and archives Amplitude Guides and Surveys through `run_amp`, including step content blocks, buttons, and survey questions. Use before changing a guide's or survey's copy, steps, questions, buttons, targeting, or settings.

Given a change_brief YAML (output from diff-intake), generates an exhaustive list of candidate analytics events to instrument. Takes the perspective of an engineer with a PM mindset — surfaces everything worth considering so a PM can decide what actually matters. Use this as step 2 of the analytics instrumentation workflow, immediately after diff-intake produces a change_brief. Trigger whenever a user has a change_brief YAML and wants to know what analytics events to add, or asks "what should I track for this PR", "what events should I instrument", "generate event candidates", or any request to surface analytics coverage gaps for a code change.

Discovers product opportunities by analyzing Amplitude analytics, experiments, session replays, and customer feedback. Synthesizes evidence into prioritized, actionable opportunities with RICE scoring. Use when the user asks to "find opportunities", "what should we build", "where are we losing users", "product gaps", or wants a data-driven backlog of improvements.

Prompteus — AI Orchestration

prompteus.com

Streamline AI workflows with Prompteus' no-code platform.

ABATA AI

abata.in

Streamline your processes, boost productivity, and unlock powerful insights—designed specifically for your…

Upstream

upstreamapi.com

AI-native feature flagging with intelligent rollout decisions, anomaly detection, and auto-rollback.

Pipedream

pipedream.com

Managed auth and 10,000+ tools across 3,000+ APIs for the agents you’re building — and a secure gateway for…

Pendo.io

pendo.io

Pendo feeds product context to the apps and AI agents you build or buy, so you can understand your users, act…

Feeedbackr

feeedbackr.com

Feeedbackr lets indie developers collect and analyze user feedback with a single button.