Communitygithub.com

amplitude/builder-skills

在 Amplitude 中找到最活跃的用户,查看您的 Google 日历中的空闲时段,并创建个性化的 Gmail 草稿邀请他们参加研究访谈。永远不会发送——始终保存为草稿供您审核。用于规划用户研究冲刺时使用。

builder-skills 是什么?

该技能旨在自动化用户研究访谈的招募流程,帮助产品团队高效地找到目标用户、安排时间并起草邀约邮件。它首先从 Amplitude 中提取指定时间段内最活跃的 N 个用户及其使用数据(如会话次数、常用功能、行为变化),然后查询您的 Google 日历以找出符合偏好时段的空闲 45 分钟时段,最后为每位用户生成一个个性化的 Gmail 邮件草稿。邮件内容基于用户在 Amplitude 的真实行为数据,例如“我们注意到您最近几周频繁使用某个功能”,并包含 Calendly 链接或预定时间段供对方选择。所有邮件都保存为草稿,绝不会自动发送,确保您可以在发送前手动审核和调整。该技能适用于 Cursor、Claude Code、Codex 和 Windsurf 等主流开发工具,支持与 Amplitude、Google Calendar 和 Gmail 的 MCP 集成。

兼容平台~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 中提取最活跃的用户,在您的日历中找到空闲时段,并为每位用户起草一封个性化邮件——准备好供您审核,然后才会发出。


提示模板

/schedule 您正在帮我安排用户研究访谈。请按以下步骤操作:

### 第一步 —— 在 Amplitude 中找到顶级用户
进入 Amplitude,找出过去 {{TIME_PERIOD}} 期间排名前 {{N}} 的最活跃用户。
对于每位用户,记录:
- 会话次数
- 最常用的功能
- 近期活动是否有激增或下降
- 他们作为客户的时间长度

### 第二步 —— 检查我的 Google 日历空闲时段
查看我接下来 {{CALENDAR_WINDOW}} 的 Google 日历。在 {{PREFERRED_HOURS}} 期间找到空闲的 45 分钟时段,
避开已有事件,并在会议之间保留至少 15 分钟的缓冲时间。确定 {{SLOT_COUNT}} 个合适的候选时段。

### 第三步 —— 在 Gmail 中起草个人邮件——不要发送
为每位用户创建个性化的 Gmail 草稿。每封草稿应包含:

主题:“聊几分钟?我们很想听听您对 {{PRODUCT_NAME}} 的反馈”

开头:基于其在 Amplitude 中的数据写一句个性化的观察——例如“我们注意到您在过去几周内频繁使用 {{FEATURE_NAME}}。”保持真诚且具体,不要恭维。

正文:简要说明目的——进行简短的研究访谈,以了解 {{PRODUCT_NAME}} 对用户来说哪些地方做得好,哪些地方可以改进。

排程:
- 如果 Calendly 可用:优先提供——“欢迎选择方便的时间:{{CALENDLY_LINK}}”
- 如果没有 Calendly:提供 {{SLOT_COUNT}} 个可用的时间段(日、日期、时间 + 时区)并包含会议链接:{{MEETING_LINK}}

落款:{{SENDER_NAME}}

### 规则
- 不要发送任何邮件。将所有内容保存为草稿。
- 不要编造用户数据——仅使用 Amplitude 返回的数据。
- 如果用户在 Amplitude 中没有电子邮件,请单独记录并跳过草稿。

设置

字段值
所需 MCPAmplitude、Google 日历、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.

相关技能