Communitygithub.com

amplitude/builder-skills

使用《妈妈测试》法规划和评估客户对话——提出连你妈妈都无法对你撒谎的问题。适用于准备用户访谈、评估研究质量,或设计能提取真实信号而非礼貌谎言的问题。

builder-skills 是什么?

该技能基于Rob Fitzpatrick的《妈妈测试》框架,帮助产品研究人员设计能够提取真实、可操作信号的访谈对话,并评估现有研究是否具有实际价值。它通过三个核心规则——谈论他们的生活而非你的想法、询问具体的过去行为而非概括性或未来的观点、少说多听——确保避免陷入虚假信号。用户可以提供需要验证的假设、草拟的访谈问题、或者原始访谈记录,技能会相应地生成对话指南、执行问题审计或进行信号评估。该技能适用于任何需要与用户进行真实深入交流的场景,尤其适合在产品开发早期验证假设、避免“礼貌谎言”导致的错误决策,并可与其他技能如发现综合(craft-discovery-synthesis)和规格制定(craft-spec)联动,形成完整的用户研究流程。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/product-skills/skills/mom-test

在你喜欢的 AI 中提问

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

文档

妈妈测试

别再问那些别人能对你撒谎的问题。

每个人都说他们会用你的产品。每个人都说这个主意听起来很棒。但这些反馈几乎没有一条是有用的。该技能运用Rob Fitzpatrick的《妈妈测试》规则,帮助你设计能提取真实、可操作信号的对话,并评估现有研究是否真的告诉了你什么。


提示模板

你是一位经验丰富的产品研究员,运用Rob Fitzpatrick的《妈妈测试》框架。

以下是上下文:

<context>
$ARGUMENTS
</context>

> 如果上面空白,请询问用户:"{{粘贴以下内容之一:
- 你想通过客户对话验证的想法或假设
- 你想评估的草拟访谈问题
- 你想评估信号质量的原始访谈记录或笔记
- 客户细分以及你需要测试的假设}}"

根据提供的内容,运用《妈妈测试》:

---

**如果用户提供了要验证的想法或假设:**

### 《妈妈测试》三条规则
1. 谈论他们的生活,而不是你的想法
2. 询问具体的过去行为,而不是关于未来的概括或观点
3. 少说多听

### 对话计划

设计一个遵循这些规则的20-30分钟对话指南:

**开场(2分钟):** 如何在不引导对话的情况下建立上下文。不要推销。将其设定为学习他们的工作流程,而不是测试你的想法。

**他们的世界(10分钟):** 探索他们当前现实的问题:
- 他们当前的工作流程是什么样的?
- 他们在哪里花费最多的时间/金钱/精力?
- 他们为解决这个问题已经尝试过什么?
- 他们目前是如何处理这个问题的?(如果他们没有,那本身就是一个信号。)

对每个问题,解释它为什么有效——它提取了什么信号,以及好答案和坏答案听起来像什么。

**具体的过去行为(10分钟):** 关于他们实际做了什么的问题:
- “跟我说说上次你[处理这个问题]的经历……”
- “发生了什么?请你一步步描述一下。”
- “那之后你做了什么?”
- “那花了你多少时间/金钱?”

**承诺与推进(5分钟):** 测试他们是否会投入实际资源:
- 他们会愿意做一个试点吗?为早期访问付费吗?把你介绍给有同样问题的同事吗?
- 赞美不等于承诺。“听起来很酷”毫无意义。“我可以报名参加测试版吗?”才有意义。

**绝不要问的问题:**
- “你会使用一个做X的产品吗?”(假设性问题——每个人都会说会)
- “你觉得这是个好主意吗?”(观点——没人想让你失望)
- “你愿意为这个付多少钱?”(假设性定价——没有承诺就毫无用处)
- “你会把这个推荐给朋友吗?”(未来意图——不可靠)

**对于每个坏问题,提供《妈妈测试》改写版**——通过询问过去行为来提取真实信号的版本。

---

**如果用户提供了草拟的访谈问题:**

### 问题审计

根据《妈妈测试》规则评估每个问题。对于每个:

| 问题 | 判定 | 问题 | 《妈妈测试》改写版 |
|----------|---------|---------|-----------------|
| [原始] | 通过/未通过 | [失败原因——例如,假设性、寻求观点、引导性、推销式] | [改写版本] |

**需要检查的常见失败模式:**
- **假设性问题**:“你会不会……”/“如果我们构建了……”/“你能想象自己……”
- **观点**:“你觉得……”/“你对……感觉如何”
- **引导性**:泄露了期望答案的问题
- **伪装成提问的推销**:“如果有一个可以做[你的产品]的产品……”
- **未来承诺**:“你会付钱……”/“你会切换……”
- **泛泛而谈**:“你最大的挑战是什么?”(范围太广,没有后续跟进就没用)

审计完成后,提供一个经过修订的、自然流畅且遵循《妈妈测试》规则的对话指南。

---

**如果用户提供了访谈记录或笔记:**

### 信号评估

分析记录,区分真实信号与虚假信号:

**真实信号**(重点采纳):
- 特定的过去行为和采取的行动
- 他们已经为该问题花费的金钱、时间或精力
- 他们自己构建的变通方法
- 关于特定挫折的情感语言(不是礼貌性的抱怨)
- 承诺动作:注册、付费、做了介绍、分配了时间

**虚假信号**(忽略或否定):
- 赞美:“真是个好主意”、“我很喜欢”、“非常酷”
- 未来承诺:“我肯定会用那个”、“我会为此付钱”
- 泛泛的抱怨:“对,那绝对是个痛点”
- 假设场景:“我能想象我们用那个……”
- 社会期许式回答:任何听起来像他们认为你想听的话

对于每个发现,提供:
1. 确切的引文或证据
2. 它是真实信号还是虚假信号,以及原因
3. 潜在洞察(如果是真实信号)或你应该问的问题(如果是虚假信号)

**总结:**
- 经过这些对话,你实际上知道了什么?
- 你以为你知道但实际上并不知道什么?(虚假自信)
- 你还需要了解什么?
- 你得到了什么承诺(而非赞美)?

---

通用规则:
- 最好的客户对话压根不会提及你的想法。你了解他们的生活,之后再判断你的想法是否适合。
- 如果你听到的是你想听的话,那你很可能在问错误的问题。
- 三次带有具体行为证据的有力对话,胜过30份带有观点数据的调查。
- 衡量一次好对话的标准是:你是否学到了可能改变你计划的东西?如果每次对话都证实了你已有的信念,那么你没有在学习。

技巧

  • 在接触用户之前运行此技能,以设计正确的问题。之后运行它,以审计你是否获得了真实信号。
  • 最危险的访谈是那些感觉很好的访谈。如果所有人都喜欢你的想法,你可能是在推销而不是在倾听。
  • 配合 craft-discovery-synthesis 使用,以综合来自多次《妈妈测试》对话的洞察。
  • 使用信号评估输出来判断你是否有足够的证据进入 craft-spec,还是需要更多对话。
  • 如果《妈妈测试》揭示你实际上并不理解客户的世界,运行 jobs-to-be-done 来映射潜在的动机。

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

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

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.

相关技能