Communitygithub.com

amplitude/builder-skills

根据需求或目标构建全面的Amplitude仪表盘,将图表按逻辑分区组织并采用合适的布局。适用于从头创建完整仪表盘或将现有图表整合为统一视图。

builder-skills 是什么?

该技能(Amplitude Dashboard Builder)旨在帮助AI代理或开发人员从零开始或整合现有图表,快速创建结构化的Amplitude分析仪表盘。它提供了一套完整的五步工作流:从需求发现、仪表盘目标定义,到图表收集/创建、布局规划(摘要行→趋势→细分→明细),最后通过API创建仪表盘并添加上下文说明。技能特别强调高效操作——建议使用`save_chart_edits`批量保存图表、优先复用已有图表减少工具调用次数,并给出了针对不同内容类型的布局表格(如摘要指标3-4列/375px,趋势图6-12列/500px)。支持平台为Amplitude,用户可通过搜索事件/属性、执行查询(query_dataset)和创建/更新仪表盘API来构建最终仪表盘。常见问题涵盖查询错误(建议简化分组/日期范围)和无数据返回(检查事件名称精确匹配及日期范围覆盖)。该技能适用于团队新仪表盘、分散图表整理、高管报表或周期性复盘仪表盘的搭建。

兼容平台~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 列)
  • 分区使用富文本标题
  • 在 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 列表,使用 eventsSegmentation 配合 groupBy 代替 dataTableV2

无数据返回:

  • 检查事件名称是否完全匹配(区分大小写)
  • 确认日期范围覆盖了事件被追踪的期间
  • 确认用户细分条件不限制过严

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.

相关技能