Communitygithub.com

amplitude/builder-skills

从CRM中读取流失交易与流失账户,提取按主题(功能缺失、定价、竞品、用户体验)聚类的原因,并编写一份带产品改进建议的优先级周分析报告。在路线图规划前或为优先处理留存工作构建依据时使用。

builder-skills 是什么?

该技能旨在帮助产品团队系统性地分析客户流失与交易损失原因,将分散在CRM字段、通话记录和标签中的反馈转化为结构化的产品路线图信号。支持HubSpot、Attio、Salesforce等主流CRM及Google Drive输出。通过读取指定时间窗口内的流失交易和账户数据,提取功能缺失、定价问题、竞品胜出、用户体验缺陷及适配性等维度原因,按主题聚类(每个主题至少出现2次),并以“发生次数×平均影响ARR”的加权公式进行优先级排序。最终生成包含摘要、TOP主题、竞品情报和观察列表的标准化Markdown报告,直接存入指定文件夹。该技能特别适合在季度/月度规划会议前运行,为产品改进决策提供数据驱动的证据支持。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/analytics-skills/skills/churn-lost-deal-analysis

在你喜欢的 AI 中提问

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

文档

流失 / 交易损失分析

将CRM流失数据转化为产品路线图信号——主题、模式与具体建议。

流失交易记录与流失原因分散在CRM字段、通话笔记和标签中。该技能会读取所有数据,按主题聚类反馈,对最频繁的模式进行排名,并将其转化为具体的产品改进建议——为你的下一轮规划提供基于证据的输入。


提示模板

/schedule 以产品分析师的身份调查{{COMPANY_NAME}}为何失去交易和客户。

### 步骤 1 — 提取流失交易与流失账户
从{{CRM_NAME}}中读取过去{{TIME_WINDOW}}内所有标记为流失的交易和账户。
对每条记录,收集:
- 交易或账户名称、ARR、流失/流失日期
- 流失原因(若CRM字段已填写)
- 交易笔记、通话笔记和评论
- 应用于记录的标签
- 提到的竞品(如有)

### 步骤 2 — 提取原因
- 功能缺失 — “我们需要X”、“你的产品不能做Y”
- 定价问题 — “太贵了”、“竞品更便宜”
- 竞品胜出 — 哪家竞品及其引用的优势
- 用户体验或产品质量 — “难用”、“bug太多”、“慢”
- 适配性问题 — 使用场景不匹配、错误ICP
- 流程或销售问题 — 单独记录

### 步骤 3 — 按主题聚类
一个主题至少需要2次出现。对每个主题:
- 主题名称、出现次数、受影响的ARR总额
- 2–3条具有代表性的原始引用
- 该问题所指的具体产品缺口

### 步骤 4 — 排序与推荐
排序依据:(出现次数 × 平均受影响的ARR)。对每个排在前列的主题(最多5个):
**主题**:[名称]
**频率**:[N],**风险ARR**:[总额]
**根本原因**:[产品缺失或做错的地方]
**推荐**:[具体、可操作的产品变更]
**证据**:[1–2条原始引用]

### 步骤 5 — 将报告保存为 ChurnAnalysis_YYYY-MM-DD.md 到 {{OUTPUT_FOLDER}}

## 摘要 / ## 主要主题 / ## 竞品情报 / ## 观察列表

完成后返回Drive链接。

设置

字段值
所需MCPCRM(HubSpot / Attio / Intercom)、Google Drive
输出ChurnAnalysis_YYYY-MM-DD.md → /Product/Churn analysis
调度器每周一次,或在规划会议前手动运行

需要填写的占位符

  • {{COMPANY_NAME}} — 你的公司名称
  • {{CRM_NAME}} — 例如 HubSpot、Attio 或 Salesforce
  • {{TIME_WINDOW}} — 例如 过去30天 或 本季度
  • {{OUTPUT_FOLDER}} — 例如 /Product/Churn analysis

提示

  • ARR加权排名是关键杠杆——一笔10万美元的交易比五个免费用户的请求更重要。
  • 竞品情报部分可直接输入到竞品监控中。
  • 除每周运行外,还应每季度运行一次——缓慢变化的趋势会隐藏在周度噪音中。
  • 在每个规划周期之前与产品负责人和销售负责人分享主要主题。

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

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.

相关技能