Communitygithub.com

amplitude/builder-skills

在 Amplitude 找出最活躍的使用者,檢查你的 Google 日曆空檔,然後為每位使用者建立個人化的 Gmail 草稿邀請他們參與研究訪談。所有信件只儲存為草稿,絕不自動寄出。適合規劃使用者研究衝刺時使用。

builder-skills 是什麼?

這項技能自動化使用者研究招募流程:從 Amplitude 擷取活躍使用者資料、比對 Google 日曆空檔,並為每位使用者產生個人化 Gmail 草稿。它完全以草稿模式運作,確保您有機會審查並調整內容後再寄出。支援 Amplitude、Google Calendar 與 Gmail 的 MCP 整合,可依需求於每次研究衝刺前或持續招募時執行。核心運作邏輯包含三個步驟:分析 Amplitude 中的使用者活躍度、識別可用的日曆時段、以及根據資料(如常用功能與使用趨勢)建立個人化邀請。該技能內建防錯機制,例如略過缺少電子郵件的使用者、不隨意捏造資料,並強制所有郵件儲存為草稿以免誤寄。它也能與其他技能(如 `craft-discovery-synthesis`)搭配,進一步處理訪談結果。

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

在你喜歡的 AI 中提問

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

說明文件

訪談排程

找對使用者、檢查日曆、撰寫個人化邀請 — 不費吹灰之力。

你想和真實使用者聊聊,但找到他們、比對你的日曆、還要一封一封寫信,往往耗費數小時。這項技能會從 Amplitude 提取最活躍的使用者、找出你的空檔,並為每人建立個人化的 Gmail 草稿 — 在你審閱之前,絕不寄出任何信件。


Prompt 模板

/schedule 請幫我安排使用者研究訪談。依下列步驟進行:

### 步驟 1 — 在 Amplitude 中找出頂尖使用者
前往 Amplitude 並找出過去 {{TIME_PERIOD}} 中 {{N}} 名最活躍的使用者。
對於每位使用者,記錄:
- 工作階段次數
- 最常使用的功能
- 近期活動是否有任何激增或驟降
- 他們已經使用產品多久

### 步驟 2 — 檢查我的 Google 日曆空檔
查看接下來 {{CALENDAR_WINDOW}} 的 Google 日曆。在 {{PREFERRED_HOURS}} 期間尋找空閒的 45 分鐘時段,避開既有活動,並在會議之間保留至少 15 分鐘的緩衝。找出 {{SLOT_COUNT}} 個合適的候選時段。

### 步驟 3 — 在 Gmail 中撰寫個人化草稿 — 不要寄出
為每位使用者建立一封個人化的 Gmail 草稿。每封草稿應包含:

主旨:「快速聊聊?我們很想知道您對 {{PRODUCT_NAME}} 的意見」

開場:根據他們的 Amplitude 資料寫 1–2 句個人化觀察 — 例如「我們注意到您在過去幾週頻繁使用 {{FEATURE_NAME}}。」保持真誠且具體,不要諂媚。

內文:簡短說明目的 — 一場簡短的研究訪談,了解您這類使用者對 {{PRODUCT_NAME}} 的意見與可改進之處。

排程:
- 如果有 Calendly:優先使用 — 「歡迎直接預約時間:{{CALENDLY_LINK}}」
- 如果沒有 Calendly:提供 {{SLOT_COUNT}} 個可用的時段(星期、日期、時間 + 時區)並附上會議連結:{{MEETING_LINK}}

署名為:{{SENDER_NAME}}

### 規則
- 不要寄出任何郵件。全部儲存為草稿。
- 不要捏造使用者資料 — 僅使用 Amplitude 回傳的資料。
- 如果使用者在 Amplitude 中沒有電子郵件,請另行列出並跳過該草稿。

設定

欄位值
所需 MCPAmplitude、Google Calendar、Gmail
輸出Gmail 草稿(絕不自動寄出)
排程在每次研究衝刺前依需求執行,或持續招募時每日執行

需要填入的佔位符

  • {{N}} — 目標使用者人數,例如 10
  • {{TIME_PERIOD}} — 回溯時間範圍,例如 過去 30 天 或 上一季
  • {{CALENDAR_WINDOW}} — 檢查多久之後的時程,例如 未來 2 週
  • {{PREFERRED_HOURS}} — 您可用的時段,例如 週一至週五 10:00–16:00
  • {{SLOT_COUNT}} — 要提供的時段數量,例如 3
  • {{PRODUCT_NAME}} — 您的產品名稱
  • {{FEATURE_NAME}} — 用於個人化的功能名稱(選填;如不需要可移除)
  • {{CALENDLY_LINK}} — 您的排程連結,如果不使用 Calendly 請移除這一行
  • {{MEETING_LINK}} — Google Meet 或 Zoom 連結
  • {{SENDER_NAME}} — 您或團隊的名稱

提示

  • 送出前務必審查草稿 — 個人化效果取決於 Amplitude 的資料品質。
  • 若為特定功能招募使用者,請在 Amplitude 中按該功能的事件進行篩選,以找到重度使用者。
  • 可搭配 craft-discovery-synthesis 處理後續的訪談成果。
  • 對於 B2B 產品,建議在執行技能前先透過 Amplitude 分群依公司 ARR 或方案等級進行篩選。

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.

相關技能