Communitygithub.com

amplitude/builder-skills

根據需求或目標建立完整的 Amplitude 儀表板,將圖表整理成邏輯分區並採用合適的版面配置。適合從頭建立全新儀表板,或將現有圖表整合為統一的檢視畫面時使用。

builder-skills 是什麼?

這項技能可自動化建立 Amplitude 儀表板的流程,從需求釐清、圖表建立、版面規劃到最終儀表板生成。支援新專案儀表板、零散圖表整合、主管報告與定期回顧儀表板等多種場景。技能核心包含五個步驟:探索階段(搜尋既有圖表與事件)、定義儀表板目的、收集或建立圖表(區分既有圖表多寡決定走「整併」或「從零建立」路線)、規劃版面(摘要列、趨勢區、細分區、詳細區)、以及最終建立與添加說明文字。版面指南提供各類內容的建議寬高(如摘要指標 3-4 欄寬 375px 高、趨勢圖 6-12 欄寬 500px 高),並建議將重要指標置於上方、在行內保持圖表尺寸一致、批次儲存圖表以減少工具呼叫。常見問題包含查詢錯誤與無資料回傳的排除技巧,例如簡化查詢條件、驗證事件名稱精準匹配、調整日期範圍等。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/analytics-skills/skills/create-dashboard

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

建立儀表板

建立新的團隊或專案儀表板、整理零散的圖表、建置主管報告,或設定定期回顧儀表板。

操作說明

步驟 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 欄)
  • 區段的 Rich Text 標題
  • 在 chartMetas 中設定圖表顯示方式:
    • metric_only:重點 KPI(單一數值)
    • series:趨勢線(預設檢視)
    • converted:漏斗圖(轉換檢視)
    • table:資料表格

步驟 5:加入說明文字

包含 Rich Text 區塊來說明:

  • 儀表板的目的與受眾
  • 如何解讀關鍵指標
  • 相關資源的連結
  • 最後更新時間或檢視排程

版面指南

內容類型建議寬度建議高度
重點指標3-4 欄375px
趨勢圖6-12 欄500px
比較圖6 欄500px
詳細表格12 欄625px
區段標題12 欄375px

最佳做法

  • 將最重要的指標置於上方(頁面摺疊以上)
  • 在同一行內保持圖表尺寸一致
  • 將相關指標分組在一起
  • 為複雜的指標加上說明文字
  • 若有多種合理做法,詢問使用者關注的領域
  • 批次建立圖表以減少工具呼叫次數

常見問題

查詢錯誤(500/400):

  • 簡化:移除複雜的 groupBy、縮短日期範圍、避免巢狀屬性
  • 先使用搜尋功能驗證事件/屬性是否存在
  • 使用搭配 groupBy 的 eventsSegmentation,而非使用 dataTableV2 來取得前 N 名清單

無資料回傳:

  • 檢查事件名稱是否完全相符(區分大小寫)
  • 確認日期範圍涵蓋事件被追蹤的時間
  • 確認使用者分群條件不會過於嚴格

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.

相關技能