Communitygithub.com

amplitude/builder-skills

要件や目標から包括的なAmplitudeダッシュボードを構築し、チャートを論理的なセクションに整理して適切なレイアウトで配置します。新しいダッシュボードを一から作成する場合や、既存のチャートをまとめて統一感のあるビューにする場合に使用します。

builder-skills とは？

このスキルは、AIエージェント（Claude Code、Cursor、Codexなど）がAmplitude上で包括的なダッシュボードを自動構築するための手順とベストプラクティスを提供します。新規ダッシュボード作成、既存チャートの整理、エグゼクティブレポート作成、定期的なレビューダッシュボード設定など、さまざまなユースケースに対応します。スキルは5つのステップ（ディスカバリー、目的定義、チャート収集/作成、レイアウト計画、ダッシュボード作成）に分かれており、各ステップで具体的なAPI呼び出し（Amplitude:search、Amplitude:get_charts、Amplitude:query_dataset、Amplitude:save_chart_edits、Amplitude:create_dashboard）を指示します。チャートのプロトタイプ作成、バッチ保存、レイアウトガイドライン（サマリ行、トレンドセクション、内訳セクション、詳細セクション）、リッチテストによるコンテキスト追加など、実践的なアドバイスを提供します。また、クエリエラーやデータ不足などの一般的な問題とその対処法も含まれています。このスキルにより、エージェントはユーザーの要件から一貫性のある美しいダッシュボードを効率的に生成できます。

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

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

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

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

ドキュメント

ダッシュボード作成

新しいチームまたはイニシアチブのダッシュボードを作成し、散在するチャートを整理し、エグゼクティブレポートを構築し、またはレビューカデンスダッシュボードを設定します。

手順

ステップ 0: ディスカバリー（機能に不慣れな場合）

構築する前に、何を追跡しているのかを理解します：

  • トピックに関連する既存のダッシュボード/チャートを検索する
  • 関連するイベントを検索する：Amplitude:search（entityTypes: ["EVENT", "CUSTOM_EVENT"]）
  • get_event_properties を使用して、セグメント化に利用可能なプロパティを理解する
  • 主な目標、主要セグメント、または時間軸についてユーザーに明確化を求める

ステップ 1: ダッシュボードの目的を定義する

以下を明確にします：

  • 誰が視聴者か？
  • どのような意思決定に役立つか？
  • どの程度の頻度でレビューされるか？
  • ナラティブ構造はどのようなものか？

ステップ 2: チャートを収集または作成する

既存のチャートが十分にある場合（5つ以上関連するものがある場合）：

  • Amplitude:search を使用して関連する既存のチャートを見つける
  • Amplitude:get_charts を使用してそれらの定義を取得する
  • 新しいチャートが必要なギャップを特定する

チャートがほとんどない場合（5つ未満しか関連するものがない場合）：

  • 「グリーンフィールドビルド」モードに切り替える
  • Amplitude:query_dataset を使用して必要なチャートを作成する
  • ダッシュボードを構築する前に、すべてのチャートを Amplitude:save_chart_edits で保存する
  • 最初に entityTypes: ["EVENT", "CUSTOM_EVENT"] を使用して関連イベントを検索することを検討する

新しいチャートの作成：

  • query_dataset でプロトタイプを作成してデータを検証する
  • バッチで保存するには save_chart_edits を使用する（より効率的）
  • ダッシュボードを作成する前にすべてのチャートIDを収集する

ステップ 3: レイアウトを計画する

論理的なセクションに整理します：

  1. サマリ行：一目でわかる主要指標（ヘッドラインビュー）
  2. トレンドセクション：変化の推移
  3. 内訳セクション：セグメントとディメンション
  4. 詳細セクション：補足分析

ステップ 4: ダッシュボードを作成する

Amplitude:create_dashboard を使用して：

  • 明確で説明的な名前
  • 適切な高さ（375、500、625、または750px）の行
  • 適切なサイズ（3～12カラム）のチャート
  • セクションのリッチテキストヘッダー
  • chartMetas でのチャート表示設定：
    • metric_only：ヘッドラインKPI（単一数値）
    • series：トレンドライン（デフォルトビュー）
    • converted：ファネル（コンバージョンビュー）
    • table：データテーブル

ステップ 5: コンテキストを追加する

リッチテキストブロックを含めます：

  • ダッシュボードの目的と視聴者
  • 主要指標の解釈方法
  • 関連リソースへのリンク
  • 最終更新日またはレビュースケジュール

レイアウトガイドライン

コンテンツタイプ推奨幅推奨高さ
ヘッドライン指標3～4カラム375px
トレンドチャート6～12カラム500px
比較チャート6カラム500px
詳細テーブル12カラム625px
セクションヘッダー12カラム375px

ベストプラクティス

  • 最も重要な指標をファーストビューに配置する
  • 行内で一貫したチャートサイズを使用する
  • 関連する指標をグループ化する
  • 複雑な指標には説明テキストを追加する
  • 複数の有効なアプローチがある場合は、ユーザーに焦点領域を尋ねる
  • ツールコールを最小限にするためにチャートをバッチで作成する

よくある問題

クエリエラー（500/400）：

  • 簡略化する：複雑なgroupByを削除し、日付範囲を短縮し、ネストされたプロパティを避ける
  • 最初に検索を使用してイベント/プロパティが存在することを確認する
  • Top Nリストの場合は dataTableV2 の代わりに groupBy 付きの eventsSegmentation を使用する

データが返されない場合：

  • イベント名が完全一致していることを確認する（大文字小文字を区別）
  • 日付範囲がイベントが追跡された期間をカバーしていることを確認する
  • ユーザーセグメントが制限しすぎていないことを確認する

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

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

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