Communitygithub.com

amplitude/builder-skills

通过分析使用模式、参与趋势、风险信号和扩展机会，总结B2B账户健康状况。适用于客户成功回顾、续约准备、季度业务回顾或账户优先级排序。

builder-skills 是什么？

这是一个专为B2B客户成功团队设计的AI技能，用于深入分析账户的产品使用情况。它能够自动执行健康分类（健康、存在风险、危急），并提供包含风险因素、积极信号、用户洞察和功能采用情况的详细报告。该技能支持Amplitude平台，通过Amplitude:search和Amplitude:query_dataset等工具并行查询账户数据，从而缩短分析时间。它特别强调将用户反馈与实际行为数据相关联，并提供可直接执行的客户成功建议。最终输出以结构化Markdown报告呈现，便于团队间共享和决策。

兼容平台~Claude Code~Codex CLI~Cursor
Part ofDesign & UI
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/analytics-skills/skills/analyze-account-health
查看原文→浏览所有技能

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

文档

分析账户健康

深入分析B2B账户的产品使用情况，为季度业务回顾（QBR）做准备、评估续约风险、识别扩展机会或优先安排客户成功（CS）外联。

指示

步骤 0：识别账户并发现上下文

获取账户标识符：

  • 公司名称、组织ID、账户ID或组属性值
  • 如果未提供，询问用户

搜索现有工作： 使用 Amplitude:search 查找此账户的现有仪表盘、图表或笔记本。如果找到，询问用户是否想要重新分析或查看现有内容。

步骤 1：快速健康分类

使用 Amplitude:query_dataset 并行运行以下查询：

使用趋势：

  • 事件：_active，指标：uniques，分组依据：账户属性
  • 时间：最近60天，每日间隔
  • 显示： 活跃度在增加还是减少？

参与质量：

  • 计算账户的日活跃用户（DAU）和月活跃用户（MAU）
  • 获取DAU/MAU比率（用户黏性）
  • 显示： 活跃用户的参与程度如何？

用户势头：

  • 周活跃用户数逐周变化
  • 显示： 团队在增长还是萎缩？

分类健康：

  • 健康： MAU增长，DAU/MAU > 40%，周同比为正
  • 存在风险： MAU持平/下降，DAU/MAU为20-40%，周同比为负
  • 危急： 急剧下降，DAU/MAU < 20%，持续周同比为负

步骤 2：用户级分析

使用 Amplitude:query_dataset 并按用户级分组：

核心用户：

  • 按事件量排序的前3-5个用户（可利用的拥护者）

流失用户：

  • 在上一时期活跃但当前时期不活跃的用户（留存风险）

许可利用率：

  • 最近30天内的活跃用户数占总席位数

步骤 3：功能使用分析

使用 Amplitude:query_dataset 并按事件/功能分组：

功能广度：

  • 正在使用的核心功能有哪些？（询问用户5-10个关键功能）
  • 每个功能的采用率

功能趋势：

  • 每个功能在过去90天内的使用情况
  • 识别增长和下降的功能

根据健康情况聚焦：

  • 如果存在风险/危急： 查找被放弃的功能（60-90天前使用过，但最近30天未使用）
  • 如果健康： 查找扩展机会（尚未尝试的高级功能）

步骤 4：账户反馈分析

获取反馈来源： 使用 Amplitude:get_feedback_sources 查看可用内容。

获取反馈洞察： 使用 Amplitude:get_feedback_insights 并按以下条件筛选：

  • 账户中每个用户的ampId
  • dateStart/dateEnd：最近90天
  • types：bug、painPoint、complaint、request、lovedFeature

获取具体提及： 对于前3-5个洞察，使用 Amplitude:get_feedback_mentions 获取相关引用。

与行为关联：

  • 对功能X的投诉？查询他们对功能X的使用情况
  • 对功能Y的请求？检查他们是否遇到了功能Y能解决的限制
  • 对功能Z的赞扬？验证他们是否是功能Z的重度用户

步骤 5：呈现账户健康报告

按以下结构输出：

账户健康报告：[账户名称]

执行摘要

[2-3句话：健康评分、关键趋势、主要建议]

健康评分：[🟢 健康 | 🟡 存在风险 | 🔴 危急]

[一句话理由及关键指标]

关键指标

指标当前值趋势状态
MAUX↑↓→ Y%🟢🟡🔴
DAU/MAUX%↑↓→ Y%🟢🟡🔴
许可利用率X%↑↓→🟢🟡🔴
采用的功能数X/Y↑↓→🟢🟡🔴

🚨 风险因素（如有）

  1. [问题] - [影响]
    • 使用数据：[指标/趋势]
    • 客户反馈：[主题，提及X次] - [代表性引用]

✅ 积极信号

  1. [有效的方法] - [来自使用和反馈的证据]

👥 用户洞察

拥护者（可利用）

  • [用户ID/名称]：[活跃度摘要] - 操作：[具体的客户成功建议]

存在风险（需联系）

  • [用户ID/名称]：[最后活跃日期/下降模式] - 操作：[联系建议]

不活跃（>30天）

  • [数量] 个用户（占许可的 [X]%）

💡 主要痛点与请求

痛点

  1. [主题]（提及X次）
    • [简要描述]
    • 证据：[行为数据] + "[引用]" - [来源, 日期]
    • 操作：[要做什么]

功能请求

  1. [主题]（提及X次）
    • [他们想要什么]
    • 证据："[引用]" - [来源, 日期]
    • 路线图状态：[已在计划中/未计划/正在考虑]

他们喜欢什么 ❤️

  1. [功能]："[引用]"

📊 功能采用率

高频使用： [功能] - [X个用户] (↑Y%) 下降中： [功能] - [X个用户] (↓Y%) - 需要调查 未开发（增销）： [高级功能] - 可解决[痛点]

🎯 建议

🔥 本周

  1. [具体操作，包含用户名/联系人名]

📅 本月

  1. [战略行动，附上下文]

💰 扩展机会

  1. [增销信号，附证据]

📎 详情

  • 分析日期： [日期]
  • 时间范围： [最近X天]
  • 置信度： [高/中/低，基于数据量]

最佳实践

  • 始终提及用户名称 - 客户成功需要知道联系谁，而非汇总数据
  • 将反馈与行为关联 - 用使用数据验证投诉
  • 给出具体建议 - 说"打电话给Sarah讨论功能X"而非"提高参与度"
  • 展示趋势而非快照 - 方向比时间点更重要
  • 标记数据缺口 - 注意低数据量、缺失属性或不完整数据
  • 按影响排序优先级 - 聚焦影响多用户或拥护者的问题

常见模式

流失风险：

  • 拥护者流失 + 整体使用量下降
  • 对同一问题的多个投诉 + 摩擦的行为证据
  • 许可利用率下降 + 负面反馈

扩展信号：

  • 接近计划限制（用户、API、存储）
  • 对高级功能的请求 + 高参与度
  • 新用户加入 + 积极反馈

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

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.

相关技能

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