Communitygithub.com

amplitude/builder-skills

特定のAmplitudeチャートを深く分析し、トレンド、異常値、原因を説明します。指標が異常に見える場合、急上昇や急落を調査する場合、数値の背景にある「理由」を理解する場合に使用します。

builder-skills とは？

このスキルは、Amplitudeチャートの詳細分析を自動化し、データ駆動型のインサイトを提供します。ユーザーがチャートのURLやIDを入力すると、ステップバイステップでデータを取得・検証し、パターン（スパイク、ドロップ、トレンド、季節性、異常）を特定します。その後、関連するプロパティを用いたセグメント分析を実行し、変化の主要因を絞り込みます。さらに、実験、デプロイ、顧客フィードバックなどのコンテキスト信号を収集し、異常値の原因を特定します。最終的に、「何が」「いつ」「なぜ」起きたか、主要な仮説、証拠、影響、推奨される次のステップを含む構造化された分析レポートを生成します。Claude CodeやCursorなどのAIエージェントプラットフォームで動作し、Amplitude APIと連携して効率的なデータ探索を実現します。

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

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

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

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

ドキュメント

チャート深堀分析

使用タイミング

  • 指標が予想外に急上昇または急落した場合
  • トレンドの原因を理解する必要がある場合
  • エビデンスに基づいた詳細分析を関係者向けに準備する場合
  • ユーザーセグメントやイベントセグメント間の差異を調査する場合

手順

ステップ0: チャートの特定

  • チャートのURLまたはチャートIDを受け取る
  • ユーザーがURLを提供した場合、Amplitude:getting_data_from_url を使用してチャートIDを抽出する
  • チャート識別子が提供されなかった場合、チャートのURLまたはIDを明示的に要求し、処理を中断する

ステップ1: チャートデータの取得と検証（必須）

  • チャートデータの読み取りを使用してチャート定義とデータを取得する
  • チャートデータが取得できない、または空の場合は処理を進めない
    • 不足している内容（時間範囲、イベント、フィルター、権限）を説明する
    • ユーザーにチャートを修正するか、有効なチャートを提供するよう依頼する

以下を取得して明記する:

  • 測定対象の指標
  • 時間範囲と粒度
  • チャートタイプ（例：時系列、ファネル、リテンション）
  • 既存のフィルター、セグメント、またはブレークダウン

ステップ2: パターンと変化期間の特定

Analyzing chart を使用して状況を特徴づける:

  • スパイク / ドロップ: 特定の日付で急な変化
  • トレンド: 時間の経過に伴う徐々の増加または減少
  • 季節性: 毎週または毎月繰り返されるパターン
  • 異常: 最近のベースラインまたは過去の動作からの逸脱

以下を明示的に特定する:

  • 変化の期間（開始/終了）
  • 変化の方向と規模
  • 比較に使用したベースライン期間（デフォルト: 直前の同等期間）

ステップ3: 原因の調査（制限付き）

幅広くスライスする代わりに、ガイド付きセグメンテーションを使用する:

  1. 適切なイベントプロパティの検出を使用して、変化を説明するための最も関連性の高いプロパティを特定する
  2. 最大9つの高シグナルプロパティ（例：プラットフォーム、国、プラン、バージョン）を選択する
  3. これらのプロパティを考慮してAnalyzing chartを再実行し、以下を判断する:
    • どのセグメントが変化に最も寄与しているか
    • パターンが局所的か広範囲か
    • Amplitude:query_charts を使用する際は、一度に取得するチャートは最大3つまでとする

ユーザーが明示的に深度調査を要求しない限り、合計9つを超えるプロパティをテストしないこと。

ステップ4: コンテキストとの相関（異常値には必須）

スパイク、ドロップ、または予期しない変動の場合、同じ時間枠でコンテキストシグナルを収集する:

  • 実験の取得を使用してアクティブな実験やフラグを特定する
  • デプロイの取得を使用してリリースやロールアウトを特定する
  • コンテンツの検索を使用して注釈や関連ドキュメントを表面的に取得する
  • Amplitude:get_feedback_insights を使用して、変化を説明する可能性のある顧客フィードバックのトレンドを検索する
  • Amplitude:get_feedback_mentions を使用して、説明対象に関連する可能性のあるフィードバックトレンドがある場合、特定の顧客言及を取得する

コンテキストの変化がチャートパターンと時間的に一致するかどうかを判断する。

ステップ5: 調査結果の統合

構造化された意思決定可能な分析を提示する:

  1. 何が起きたか 観測されたパターンと規模の明確な説明

  2. いつ 正確な時間枠と比較ベースライン

  3. 主な仮説 チャートデータとコンテキストシグナルに基づく最も可能性の高い説明

  4. 裏付けとなるエビデンス

    • 主要指標
    • セグメント貢献度
    • 関連する実験、デプロイ、または注釈

  5. 代替説明 1～3の妥当な代替案と、それらが可能性が低い理由

  6. 影響 可能な限り影響を定量化する（ユーザー、イベント、コンバージョン、収益プロキシ）

  7. 推奨される次のステップ 1つの明確なフォローアップアクション（例：詳細セグメント、実験レビュー、インストルメンテーションチェック）

常に以下を含める:

  • チャート名
  • チャートID
  • チャートへのリンク
  • カバレッジ（例：テストしたプロパティ、分析したセグメント）

ベストプラクティス

  • 常に明確なベースライン期間と比較する
  • 観測と仮説を区別する
  • 網羅的なスライスよりも高シグナルのセグメンテーションを優先する
  • データ品質の問題（低ボリューム、不完全な期間、大量の「(なし)」値など）に注意する
  • ユーザーが明示的に依頼しない限り、チャートを作成または編集しない

Individual skills in this repo

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

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

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.

関連スキル

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