Communitygithub.com

amplitude/builder-skills

Amplitude の MCP Analytics SDK で計装された MCP サーバーの利用状況を分析し、ツールごとの使用量とエラー、呼び出し元の意図を明らかにして、優先順位付けされた修正案をレポートします。

builder-skills とは？

このスキルは、Amplitude MCP Analytics SDK で計装された MCP サーバーの利用データを分析し、開発者がサーバーの改善点を特定し、優先順位を付けるための包括的なレポートを生成します。分析は、ツールごとの呼び出し量とエラー率の把握、各ツール内の呼び出し理由（Rationale）に基づくユーザー意図のクラスタリング、そしてエラー証拠に基づいた具体的な修正提案の3段階で構成されます。特に、ツール名と呼び出し理由（Rationale）の組み合わせが重要で、エラー率が高いツールを特定した上で、そのツール内で何をしようとして失敗しているのかを明らかにすることで、修正すべき箇所とその理由を明確にします。このスキルは、Claude Code、Cursor、Codex などの AI エージェントが利用可能な Amplitude MCP コネクタ経由でデータを取得し、MCP サーバーの利用レポート、ツールエラー分析、インテント分析を要求するユーザーの依頼に応答します。分析結果は、ツールレベルの内訳を最優先としたレポート構造で提供され、各主張には正確な数値が添えられ、具体的なアクションとして修正案が提示されます。

対応~Claude Code~Codex CLI~Cursor
Part ofDesign & UI
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/analytics-skills/skills/analyze-mcp-server
オリジナルを見る→すべてのスキルを見る

お気に入りのAIに質問する

このエージェントスキルを事前に読み込んだ状態で新しいチャットを開きます。

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

ドキュメント

MCP サーバー分析 — インテント & エラー分析

Amplitude の MCP Analytics SDK で計装された MCP サーバーに関する3つの質問に答えるレポートを生成します:

  1. どのツールが使用され、どのツールが失敗しているか？ （ツールごとのボリューム + エラー率）
  2. 呼び出し元は各ツールで何をしようとしており、それぞれの意図はどこで失敗しているか？ （ツール内の理由とエラーメッセージ）
  3. チームは何を最初に修正すべきか？ （「なんとなく」ではなく、エラー証拠に基づいた修正）

この分析を価値あるものにする核となる考え方: ツールが修正箇所を特定し、理由がその背後にある意図を説明する。 全体的なエラー率は「呼び出しの4.5%が失敗する」と言います。ツール別に分解すると「query_chart は22%の確率で失敗する」と分かります — これで何を開くべきかが分かります。そのツール内の理由を追加すると「失敗は、バッチサイズ制限に達しているダッシュボード更新エージェントによるもの」と分かります — これで理由が分かり、修正は自ずと決まります。理由はほとんどがツールスコープです（各ツールには独自の呼び出し理由があります）。そのため、ツールが主要な軸であり、理由はその内側の2番目の切り口です — 理由をグローバルにクラスタリングすると、ツールの境界を再導出するだけで、比較不可能な意図が混在することになります。

前提条件

  • Amplitude MCP コネクタがアクティブであること。アクティブでない場合は、ユーザーにツール/コネクタ設定で Amplitude コネクタを追加するよう依頼して停止してください — 代替のデータソースはありません。

  • SDK のイベントを含むプロジェクト。SDK は SDK 所有のデフォルトイベント を発行し、すべて [MCP] プレフィックスが付いています。そして、重要なことに、それらが運ぶすべてのデフォルトプロパティも [MCP] プレフィックスが付いており、カスタムプロパティを持つ場合もあります。

    イベント:

    • [MCP] Tool Call Response — 主力イベント: ツールコールバックに到達したツール呼び出しごとに1つのイベント（成功またはエラー）。
    • [MCP] Tool Call Rejected — ツールが実行される 前 に失敗した tools/call（不明/無効なツール、入力スキーマ検証）。幻覚や誤入力されたツール名はここに入り、[MCP] Attempted Tool Name に保持されます（予約済みの [MCP] Tool Name には入りません）。
    • [MCP] Session Initialized、[MCP] Session Ended、[MCP] Tools Listed。

    [MCP] Tool Call Response の主要プロパティ: [MCP] Tool Name、[MCP] Client Name、 [MCP] Client Version、[MCP] Session ID、[MCP] Auth Type、[MCP] Rationale、 [MCP] Is Error、[MCP] Error Message、[MCP] Error Type（returned_error vs thrown_exception — 失敗を報告したツールとクラッシュしたツールを区別）、 [MCP] Response Duration、[MCP] Response Size、[MCP] Request Size。

  • イベント/プロパティ名は SDK バージョン間で変わる可能性があります。決して推測しないでください — フェーズ0でタクソノミツールを使用して確認してください。上記の正規名は SDK の constants.ts（EVENT_PROPERTY_KEYS）からのものです。プロジェクトのデータが異なる場合は、プロジェクトを信頼して適応してください。

フェーズ0 — データの特定と検証

  1. Amplitude コンテキストツール（projectId なし）を呼び出してプロジェクトを一覧表示します。複数の妥当なプロジェクトが存在し、ユーザーが指定していない場合は尋ねてください。
  2. 選択したプロジェクトに [MCP] イベントが存在することを確認します（イベントを検索または一覧表示します。get_events は完全名でのみフィルタリングするため、[MCP] プレフィックスの発見には検索を使用してください）。
  3. [MCP] Tool Call Response（および [MCP] Tool Call Rejected）のイベントプロパティを取得して、正確なプロパティ名を確認します — これらは [MCP] プレフィックスが付き、タイトルケースであることを忘れないでください（例: [MCP] Rationale、tool rationale ではありません）。見つけたものを以下のクエリで使用する名前にバインドします。
  4. 1つのボリューム/新しさクエリを実行します: 過去60日間の [MCP] Tool Call Response、[MCP] Session Initialized の合計を週間隔で。これにより、使用可能な日付範囲と十分なデータがあるかどうかがわかります。ツール呼び出しの合計が約5k未満の場合は、ツールごとの内訳が薄くなりパーセンテージが不安定になることをユーザーに警告します — それでも続行しますが、レポートにその旨を記載します。

記録: プロジェクト ID、日付範囲、総呼び出しボリューム。以降のすべてのクエリは同じ範囲を使用して、数値の比較可能性を維持します。

フェーズ1 — ツールごとの内訳（基軸）

これが主要なマップです。他のすべてはこれを掘り下げます。

  • ツールごとのボリューム: [MCP] Tool Call Response の合計を [MCP] Tool Name でグループ化、groupByLimit ~100。
  • ツールごとのエラー: 同様に、フィルター `[MCP] Is Error is

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

Synthesizes customer feedback into actionable themes including feature requests, bugs, pain points, and praise. Use when planning product roadmap, understanding user sentiment, investigating specific issues, or preparing voice-of-customer reports.

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.

関連スキル

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