Communitygithub.com

amplitude/builder-skills

Synthetisiert Kundenfeedback zu umsetzbaren Themen wie Feature-Wünschen, Fehlern, Schmerzpunkten und Lob. Verwenden Sie dies bei der Planung der Produkt-Roadmap, zum Verständnis der Nutzerstimmung, zur Untersuchung spezifischer Probleme oder zur Erstellung von Voice-of-Customer-Berichten.

Was ist builder-skills?

Diese Fähigkeit ermöglicht es KI-Agenten, umfassende Feedback-Analysen durchzuführen, indem sie Kundenfeedback aus verschiedenen Quellen (z. B. Umfragen, Support-Tickets, App-Bewertungen) thematisch zusammenfassen. Sie ist besonders nützlich für Produktmanager und Entwickler, die schnell verstehen möchten, welche Funktionen gewünscht werden, welche Fehler gemeldet wurden oder wo Schmerzpunkte liegen. Die Skill-Schritte führen den Agenten durch die Identifizierung verfügbarer Feedback-Kanäle, die Filterung nach Typ und Datumsbereich, das Aufrufen thematischer Erkenntnisse und das Herunterbrechen in konkrete Nutzerzitate. Anschließend können die Ergebnisse mit Nutzersegmenten (z. B. nach Nutzungsdauer oder Tarif) verknüpft werden. Die Präsentation erfolgt strukturiert mit einer Zusammenfassung, dringenden Problemen, Top-Feature-Wünschen, Lob, einer Sentiment-Analyse (1–5) und priorisierten Handlungsempfehlungen (p0–p3). Die Fähigkeit unterstützt die Plattformen Claude Code, Cursor und Codex und basiert auf der Amplitude-API sowie den Tools `Amplitude:get_feedback_sources`, `Amplitude:get_feedback_insights`, `Amplitude:get_feedback_mentions` und `Amplitude:get_cohorts`.

Funktioniert mit~Claude Code~Codex CLI~Cursor
Part ofDesign & UI
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/analytics-skills/skills/analyze-feedback
Original anzeigen→Alle Skills durchsuchen

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Dokumentation

Feedback analysieren

Führen Sie umfassende Feedback-Überprüfungen durch, untersuchen Sie spezifische Feature-Wünsche, verstehen Sie die Kundenstimmung und erstellen Sie prägnante, aber umsetzbare Voice-of-Customer-Präsentationen.

Anleitung

Schritt 1: Verfügbare Quellen verstehen

Verwenden Sie Amplitude:get_feedback_sources, um zu sehen, welche Feedback-Kanäle verbunden sind (Umfragen, Support, App-Bewertungen usw.).

Schritt 2: Thematische Erkenntnisse gewinnen

Verwenden Sie Amplitude:get_feedback_insights mit geeigneten Filtern:

  • Nach Typen filtern: request, complaint, lovedFeature, bug, painPoint
  • Nach Datumsbereich für aktuelles Feedback filtern
  • Nach Quelle für kanalspezifische Analyse filtern

Schritt 3: In spezifische Themen eintauchen

Verwenden Sie für die wichtigsten Erkenntnisse Amplitude:get_feedback_mentions, um das tatsächliche Nutzerfeedback zu sehen, das jedem Thema zugrunde liegt.

Schritt 4: Mit Nutzersegmenten verknüpfen

Verwenden Sie Amplitude:get_cohorts, um zu verstehen, ob Feedback-Themen mit Folgendem korrelieren:

  • Nutzungsdauer (neue vs. etablierte Nutzer)
  • Tariftyp (kostenlos vs. kostenpflichtig)
  • Nutzungsintensität (Power-User vs. Gelegenheitsnutzer)

Schritt 5: Ergebnisse präsentieren

Strukturieren Sie wie folgt:

  1. Zusammenfassung: Prägnanter Einzeiler, der die Anzahl der analysierten Feedback-Quellen und -Erwähnungen sowie die wichtigsten Erkenntnisse aus der Analyse erläutert.
  2. Dringende Probleme 🚩: Top-Fehler, Probleme oder Schmerzpunkte, die von Kunden genannt wurden. Teilen Sie hier 3–4 Themen, sofern nicht anders angewiesen.
  3. Top-Feature-Wünsche 💡: Top-Feature-Wünsche, die von Kunden genannt wurden. Teilen Sie hier 3–4 Themen, sofern nicht anders angewiesen.
  4. Lob ❤️: Top-Lob oder geliebte Funktionen, die von Kunden genannt wurden. Teilen Sie hier 1–2 Themen, sofern nicht anders angewiesen.
  5. Sentiment-Analyse: Teilen Sie eine sehr prägnante Übersicht über die Themen, das Sentiment auf einer Skala von 1–5 (5 ist der höchste Wert) und Ausschnitte als Belege.
  6. Priorisierte Empfehlungen: Ein sehr prägnanter Abschnitt, der die wichtigsten 3–7 spezifischen, umsetzbaren Empfehlungen (sofern nicht anders angewiesen) zur Nachverfolgung zusammenfasst. Fügen Sie [p0], [p1], [p2], [p3] vor jedem Titel hinzu, um die Priorität zu kennzeichnen, wobei p0 die dringendste und p3 die geringste Priorität darstellt.

Best Practices

  • Seien Sie umfassend in Ihrer Untersuchung und Analyse, aber prägnant und umsetzbar in Ihrer Antwort.
  • Wiederholen Sie keine doppelten Abschnitte oder dieselbe Erkenntnis mehrmals.
  • Fügen Sie 1–2 repräsentative Zitate zu jedem Thema hinzu. Bevorzugen Sie die besten Zitate, die das Thema erklären. Geben Sie an, wann es eingegangen ist und aus welcher Quelle es stammt. Wenn das Zitat lang ist, zitieren Sie nur den relevanten Teil, der mit dem Thema zusammenhängt.
  • Beschreiben Sie bei der Darstellung eines Themas prägnant die Erwähnungsvolumina, die wichtigsten Quellen und die Aktualität.
  • Jedes Thema sollte eine konsistente Formatierung aufweisen wie: Prägnanter, aber beschreibender Themenname (X Erwähnungen) Umsetzbare einzeilige Beschreibung oder mehrere prägnante Aufzählungspunkte, die erklären, worum es bei dem spezifischen Problem, Wunsch oder Lob geht, für welchen Zeitraum das Feedback relevant war und aus welchen Hauptquellen das Thema stammt.
    • "Kundenzitat, das das Thema untermauert" - Quellenname (Eingangsdatum)
    • "Kundenzitat, das das Thema untermauert" - Quellenname (Eingangsdatum)
  • Für den Abschnitt „Priorisierte Empfehlungen“ sollte jede Empfehlung nur ein prägnanter, aber umsetzbarer Aufzählungspunkt sein, anstatt einer langen Themenübersicht.
  • Fassen Sie am Ende nicht zusammen, was Sie getan haben, sondern enden Sie direkt nach den prägnanten priorisierten Empfehlungen.
  • Verknüpfen Sie Feedback nach Möglichkeit mit Verhaltensdaten.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

amplitude/builder-skills

Performs deep analysis of a specific Amplitude chart to explain trends, anomalies, and likely drivers. Use when a metric looks unusual, investigating a spike or drop, or understanding the "why" behind numbers.

amplitude/builder-skills

Deeply analyze Amplitude dashboards by analyzing key charts, surfacing top areas for concern and takeaways, identify anomalies, then explain changes using customer feedback trends.

amplitude/builder-skills

Designs A/B tests with proper metrics and variants, analyzes running or completed experiments, and interprets results with statistical rigor. Use when setting up experiments, checking experiment status, analyzing results, or making ship decisions.

amplitude/builder-skills

Analyze MCP server usage instrumented with Amplitude's MCP Analytics SDK: break usage and errors down by tool, read the rationales within each tool to see what callers are trying to do, and produce a prioritized write-up of actionable fixes. Use this skill whenever the user asks to understand how their MCP server is being used, what agents/users are trying to do with it, why tool calls are failing, what to fix or improve in their MCP server, or asks for an "MCP usage report", "tool error analysis", "intent analysis", "rationale clustering", or "MCP insights". Also trigger when the user mentions [MCP]-prefixed events, tool rationale, tool call errors, or just finished instrumenting their MCP server and wants to see what the data says. Requires the Amplitude MCP connector.

amplitude/builder-skills

Read lost deals and churned accounts from your CRM, extract reasons clustered by theme (missing features, pricing, competitors, UX), and write a prioritized weekly analysis with product improvement recommendations. Use before roadmap planning or to build the case for prioritizing retention work.

amplitude/builder-skills

Creates Amplitude charts from natural language descriptions, handling event selection, filters, groupings, and visualization choices. Use when you know what you want to measure but prefer not to build the chart manually.

amplitude/builder-skills

Guide an Amplitude user through building a custom agent by suggesting use cases grounded in their role and data, shaping the idea into a well-formed spec, and generating a ready-to-run Global Agent deeplink that creates it. Use to create, build, or set up a custom agent, automate a recurring analysis, or put a repeated report on a schedule.

amplitude/builder-skills

Builds comprehensive Amplitude dashboards from requirements or goals, organizing charts into logical sections with appropriate layouts. Use when creating a complete dashboard from scratch or assembling existing charts into a cohesive view.

amplitude/builder-skills

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.

amplitude/builder-skills

Pull Intercom tickets and Slack support messages from the past 7 days, classify each signal, enrich with CRM data (ARR, plan, renewal), score by customer value and churn risk, and output a tiered priority report saved to Drive. Use when you need a fast, data-driven view of what support signals matter most.

amplitude/builder-skills

Use this skill whenever a user wants to improve existing pages on their website to get cited more by AI models — whether they say "our pages aren't getting cited", "improve this page for AI visibility", "which of our pages should we update", "make this article more cite-worthy", "our competitors are getting cited instead of us", "update our content for AI search", or any variation where the goal is improving an existing asset rather than creating something new. This skill pulls owned pages from AI Visibility, identifies which ones have citation potential but are underperforming, compares them against the external pages that are winning citations on the same topics, and produces section-level rewrites or a full-page update — then pushes the revision to the CMS as a draft. Trigger even if the user just says "help me get cited more" or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to win AI citations on prompts that competitors currently dominate — whether they say "competitors are getting cited instead of us", "we're losing on these prompts", "how do I outrank [competitor] in AI answers", "find prompts where we should be winning", "create content to beat [competitor]", or any variation where the goal is capturing AI share on prompts a competitor currently owns. This skill pulls competitor visibility data from AI Visibility, identifies the specific prompts where competitors win and Amplitude is absent, clusters them by intent, and produces targeted comparison pages, alternatives content, or rebuttal assets — then pushes drafts to CMS. Trigger on any mention of competitor, prompt hijack, outrank, or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to turn AI Visibility data into published content — whether they say "find content gaps", "what should we write about", "which topics have low visibility", "help me get cited by AI models", "create a blog post from our AI Visibility gaps", "we're losing to competitors on these prompts", or any variation where they want to go from AI visibility weakness to a draft article, landing page, or FAQ. This skill connects directly to Amplitude AI Visibility data (topics, prompts, visibility scores, citations, competitor data, full LLM responses and sources) and produces a publish-ready content brief plus full article draft. If the user mentions CMS (WordPress, Webflow, Contentful, Sanity, HubSpot, Ghost, Shopify), also trigger this skill to push the draft directly. Trigger even if they just say something vague like "what content should we create?" in an AI Visibility context.

amplitude/builder-skills

Use this skill whenever a user wants to test content variants before publishing to find which one will get cited most by AI models — whether they say "which version of this content will perform better", "test this article before we publish", "simulate how AI will respond to this content", "which angle should we use", "generate content variants and pick the winner", "run a simulation before publishing", or any variation where the goal is data-driven content selection rather than gut-feel publishing. This skill takes an identified content opportunity, generates 2–3 distinct variants with different angles or structures, scores them against actual AI model responses from AI Visibility, references the Simulate Changes feature for pre-publish validation, and produces a clear recommendation on which variant to publish — then pushes the winner to CMS. Trigger on any mention of "simulate", "test variants", "which performs better", "A/B content", or "before we publish".

amplitude/builder-skills

Use this skill whenever a user wants to understand which external sources are being cited by AI models on topics relevant to their brand, and wants to create content that will outrank those sources — whether they say "what sources are AI models citing", "why is [third-party site] being cited instead of us", "we want to be the definitive source on X", "build something that gets cited more than G2 or TechRadar", "create an authoritative asset", or any variation where the goal is producing a new reference asset (definition page, benchmark, methodology, glossary, comparison hub) designed to beat existing top-cited sources. This skill analyzes AI Visibility source data, reverse-engineers what makes top-cited pages authoritative, and produces a superior source asset — then pushes it to CMS as a draft. Trigger on any mention of "sources", "third-party citations", "authoritative content", "definitional pages", or "outrank".

amplitude/builder-skills

Instrument a Node/TypeScript MCP server with Amplitude's @amplitude/mcp-analytics SDK so tool calls, sessions, and rationale are tracked as Amplitude events. Use this skill whenever the user wants to add Amplitude analytics to their MCP server, mentions "MCP Analytics", "@amplitude/mcp-analytics", "instrument my MCP server", "track MCP tool calls", "add rationale to my MCP tools", or wants agent traffic (Claude, Cursor, ChatGPT) attributed back to Amplitude. Also use for adding UTM tagging to MCP-returned links, or for troubleshooting identity/user_id mismatches between MCP events and web/mobile Amplitude data.

amplitude/builder-skills

Instruments a pull request with Amplitude analytics that conform to the project's existing taxonomy. Reads the tracking plan via the Amplitude MCP server (events, properties, naming conventions), analyzes the PR diff to find the few user actions genuinely worth tracking, detects the codebase's SDK and tracking patterns, and adds instrumentation that matches both. Optionally (opt-in) stages new events and properties on an Amplitude tracking-plan branch for data-governance review. Use when asked to "instrument this PR", "add analytics to this change", "add tracking", "add Amplitude events", "instrument this feature", or "what should I track here".

amplitude/builder-skills

Diagnoses product health by cross-referencing Amplitude analytics (dashboards, charts, funnels, feedback, AI agent analytics), optionally Datadog (errors, latency, stack traces), and optionally Slack (qualitative feedback, bug reports, feature requests). Identifies what's broken, what's working, and what to do about it — with root causes, not just symptoms. Use when asked to "diagnose my product", "what's going on", "product health check", "what's broken", "where are users struggling", "give me a product diagnosis", or "what should I focus on".

amplitude/builder-skills

Turn one or more meeting transcripts, notes, or Slack threads into concise takeaways and clear action items with DRIs. Works with a single meeting or a batch from the whole week.

amplitude/builder-skills

Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.

Verwandte Skills

steipete/sag

ElevenLabs text-to-speech with mac-style say UX.

community

steipete/oracle

Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.

community

steipete/peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

community

mattpocock/design-an-interface

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

community

mattpocock/prototype

Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.

community

mattpocock/grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

community