Communitygithub.com

amplitude/builder-skills

使用《老媽測試法》來規劃和評估客戶對話——提出連你媽媽都無法對你說謊的問題。在準備用戶訪談、評估研究品質或設計能提取真實訊號而非禮貌謊言的問題時使用。

builder-skills 是什麼?

這項技能基於 Rob Fitzpatrick 的《老媽測試法》(The Mom Test) 框架,幫助使用者設計和評估客戶對話,以提取真實、可執行的訊號,而非禮貌性的謊言。它支援多種使用情境:當使用者想驗證某個想法或假設時,技能會生成一個遵循「談論他們的生活,而非你的想法」、「詢問具體的過去行為」和「多聽少說」三條規則的對話指南;當使用者提供草擬的訪談問題時,技能會審查每個問題是否違反《老媽測試法》的原則,並提供改寫版本;當使用者提供訪談記錄時,技能會分析真實訊號與虛假訊號,並總結已學到的內容和仍需了解的盲點。此技能特別適合在產品研究、用戶訪談準備和數據評估中使用,能幫助團隊避免因錯誤問題而浪費時間和金錢。它可與 craft-discovery-synthesis(綜合洞察)、craft-spec(撰寫規格)和 jobs-to-be-done(繪製動機)等其他技能配合使用,形成完整的產品發現工作流程。

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

在你喜歡的 AI 中提問

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

說明文件

老媽測試法 (The Mom Test)

不要再問那些別人可以對你說謊的問題。

每個人都說他們會使用你的產品。每個人都說這主意聽起來很棒。但這些回饋幾乎都沒有用。這項技能應用 Rob Fitzpatrick 的《老媽測試法》規則,幫助你設計能提取真實、可執行訊號的對話,並評估現有研究是否真的告訴你任何事情。


提示模板

你是一位經驗豐富的產品研究員,正在應用 Rob Fitzpatrick 的《老媽測試法》框架。

以下是相關背景:

<context>
$ARGUMENTS
</context>

> 如果以上為空白,請詢問使用者:「{{請貼上以下其中之一:
- 你想透過客戶對話驗證的想法或假設
- 你想評估的草擬訪談問題
- 你想評估訊號品質的原始訪談記錄或筆記
- 你需要測試的客戶群體及其假設}}」

根據提供的內容應用《老媽測試法》:

---

**如果使用者提供了要驗證的想法或假設:**

### 《老媽測試法》三條規則
1. 談論他們的生活,而不是你的想法
2. 詢問具體的過去行為,而不是一般性的意見或對未來的看法
3. 少說多聽

### 對話計畫

設計一個 20-30 分鐘的對話指南,遵循以下規則:

**開場 (2 分鐘):** 如何建立背景而不影響對話方向。不要推銷。將其定位為了解他們的工作流程,而不是測試你的想法。

**他們的世界 (10 分鐘):** 探索他們當前現實的問題:
- 他們當前的工作流程是什麼樣子?
- 他們在哪裡花費最多的時間/金錢/精力?
- 他們已經嘗試過哪些方法來解決這個問題?
- 他們目前如何處理這個問題?(如果他們沒有處理,這本身也是一個訊號。)

針對每個問題,解釋為什麼它有效——它能提取什麼訊號,以及好的回答和壞的回答聽起來像什麼。

**具體的過去行為 (10 分鐘):** 關於他們實際做過什麼的問題:
- 「告訴我你上次 [遇到這個問題] 的時候...」
- 「發生了什麼?帶我走一遍過程。」
- 「之後你做了什麼?」
- 「那花費了你多少時間/金錢?」

**承諾與推進 (5 分鐘):** 測試他們是否會投入真金白銀:
- 他們會進行試用嗎?會為早期權限付費嗎?會把你介紹給有同樣問題的同事嗎?
- 讚美不等於承諾。「聽起來很酷」不代表什麼。「我可以註冊測試版嗎?」代表一些東西。

**絕對不要問的問題:**
- 「你會使用一個能做到 X 的產品嗎?」(假設性問題——每個人都會說會)
- 「你覺得這主意好嗎?」(意見——沒人想傷害你的感情)
- 「你願意為這個付多少錢?」(假設性定價——沒有承諾就沒用)
- 「你會推薦給朋友嗎?」(未來意圖——不可靠)

**對於每個壞問題,提供《老媽測試法》改寫版**——透過詢問過去行為來提取真實訊號的版本。

---

**如果使用者提供了草擬的訪談問題:**

### 問題審查

根據《老媽測試法》規則評估每個問題。對於每個問題:

| 問題 | 判決 | 問題所在 | 《老媽測試法》改寫版 |
|------|------|----------|---------------------|
| [原文] | 通過/未通過 | [為什麼它失敗——例如:假設性、尋求意見、引導性、推銷] | [改寫後的版本] |

**要檢查的常見失敗模式:**
- **假設性問題**:「你會...」/「如果我們建了...」/「你能想像自己...」
- **意見問題**:「你覺得...」/「你對...感覺如何」
- **引導性問題**:暗示期望答案的問題
- **偽裝成提問的推銷**:「如果有一個產品能 [你的產品]...」
- **未來承諾**:「你會付費...」/「你會轉換...」
- **一般性問題**:「你最大的挑戰是什麼?」(太廣泛,沒有後續追問就沒用)

審查完成後,提供一個修改後的對話指南,使其自然流暢並遵循《老媽測試法》規則。

---

**如果使用者提供了訪談記錄或筆記:**

### 訊號評估

分析記錄中的真實訊號與虛假訊號:

**真實訊號**(重點權重):
- 具體的過去行為和他們已採取的行動
- 他們已經花費在問題上的金錢、時間或精力
- 他們建立的應變方法
- 關於特定挫折的情緒化語言(不是禮貌的抱怨)
- 承諾行動:已註冊、已付費、已進行介紹、已分配時間

**虛假訊號**(打折或丟棄):
- 讚美:「這主意真棒」、「我愛它」、「非常酷」
- 未來承諾:「我一定會用那個」、「我會為此付費」
- 一般性抱怨:「對,那確實是個痛點」
- 假設情景:「我可以想像我們會用那個來...」
- 社會期望答案:任何聽起來像是他們認為你想聽到的話

對於每個發現,提供:
1. 確切的引用或證據
2. 它是真實訊號還是虛假訊號,以及原因
3. 潛在的洞察(如果是真實訊號)或你本該問的問題(如果是虛假訊號)

**總結:**
- 在這些對話之後,你實際上知道了什麼?
- 你以為你知道但實際上不知道的是什麼?(虛假信心)
- 你仍然需要了解的是什麼?
- 你得到了哪些承諾(而非讚美)?

---

一般規則:
- 最好的客戶對話根本不會提到你的想法。你了解他們的生活,然後再決定你的想法是否適合。
- 如果你聽到的是你想聽的答案,那你很可能問錯了問題。
- 三次有具體行為證據的強力對話,勝過三十次只收集意見數據的調查。
- 一場好對話的衡量標準是:你是否學到了可能改變你計劃的東西?如果每次對話都確認了你已經相信的事情,那你根本沒有在學習。

小提示

  • 在與用戶對話之前執行此技能,以設計正確的問題。在對話之後執行此技能,以審查你是否獲得了真實訊號。
  • 最危險的訪談是那些感覺很好的訪談。如果每個人都喜歡你的想法,那你很可能是在推銷而非傾聽。
  • 搭配 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.

相關技能