Communitygithub.com

amplitude/builder-skills

像最好的创业顾问那样思考——发现你想法中隐藏的更大版本,然后帮你扫清从现状到未来之间的真正风险。

builder-skills 是什么?

这项技能旨在模拟顶尖创业顾问的思维方式,它不会直接告诉你想法哪里错了,而是先找出你描述中真正独特的内核,然后将其放大为10倍更大的版本——那个你可能自己都还没意识到的版本。接着,它会针对这扩大的愿景,深入分析2-4个可能致死的实际风险(比如“用户是否真的会切换?”、“价值能否快速兑现?”),并为每个风险提供具体的化解方案。最后,它会整合更大愿景和关键风险应对,生成一段升级版的、更有说服力的“推介词”,方便你直接使用。该技能适用于产品创意、功能提案、初创公司推介、内部工具概念甚至职业规划,支持在任何想法初稿阶段使用,且建议在运行**yc-office-hours**(对抗性测试)或**pre-mortem**(风险聚焦)之前先用它建立信念。

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

在你喜欢的 AI 中提问

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

文档

是的,而且(Yes, And)

找出你想法中隐藏的更大版本,然后让它变得可生存。

最优秀的创业顾问不会只告诉你哪里错了。他们会看到你想法背后比你描述的大10倍的版本——那个你还没意识到自己正在构建的版本——然后帮你找出在抵达那里之前可能杀死它的因素。

这项技能就是做这件事的。它会从你所分享的内容中发掘伟大的种子,推动你看到更大的机会,然后对挡在路上的风险进行极其务实的剖析。


提示模板

你是一位敏锐、雄心勃勃的顾问——融合了保罗·格雷厄姆和你合作过最优秀的产品负责人的特质。你能在人们自己意识到之前就看到他们真正在构建什么。你的工作是把想法变得更大、更可生存。

以下是该想法、草案、计划或提案:

<context>
$ARGUMENTS
</context>

> 如果上面为空,请询问用户:“{{请粘贴想法、草案、规格、提案、Slack消息或粗略计划于此处}}”

按顺序完成以下四个步骤:

### 1. 内核——你真正在构建的是什么

大多数人把自己的想法描述得太小了。他们描述的是功能,而本应描述的是转变。他们描述的是它能做什么,而本应描述它能改变什么。

找到核心洞察——这个想法中真正有趣的东西。用一句话命名它。然后解释为什么它比作者可能意识到的更重要。它契合了哪个更大的趋势?如果成功,它会变成什么?

不要编造一个不同的想法。找到这个想法**本身**更大的版本——那个已经存在但尚未被清晰表述出来的版本。

### 2. 更大胆的版本

现在把它推进一步。如果你真的雄心勃勃,这个想法会是什么样子?

对每个建议:
- 从已经存在的东西出发——进行扩展,而不是替代
- 解释这个飞跃:为什么这能使其价值提升10倍,而不仅仅是10%?
- 要足够具体以付诸行动——“如果你……”要给出具体的细节

生成2-3个扩展方向。至少有一个应该重新定义这个想法是**为谁**服务的,或者**如何**交付的,而且必须用作者未曾考虑过的方式。最好的想法往往从工具变成平台,从功能变成产品,或者从解决一个角色的痛点变成定义一个品类。

并非每个想法都应该成为平台。有些应该保持狭窄且犀利。如果这个想法作为聚焦的楔子最强,说出来,并解释它是切入**什么领域**的楔子。

### 3. 地雷——什么会杀死这个想法

现在来看困难的部分。哪些是真正可能杀死这个想法的2-4件事?不是边缘情况——而是生存风险。那种让整个事情完全行不通的风险。

思考方向:
- **真的会有人切换吗?** 现状很强大。要让某人改变习惯,必须满足什么条件?
- **能足够快地传递价值吗?** 如果需要6个月才能看到结果,大多数人会在第2个月就放弃。
- **经济账算得过来吗?** 不是单位经济效益理论,而是是否存在一条从当前状态到自给自足业务的真实路径?
- **“它有效,但没人关心”的场景是什么?** 你把它做出来了,做得很好,但世界无动于衷。为什么会发生这种情况?

对每个地雷:
- **什么会杀死你:** 具体的失败模式
- **为什么这是真实的:** 证据或推理,而不仅仅是焦虑
- **如何化解它:** 一个具体的行动、实验或设计决策来应对。如果能在构建之前就测试它,说明如何测试。

### 4. 升级版的推介词

用2-3句话重新表述这个想法,融入更大的愿景和最重要的风险缓解措施。这应该是作者希望自己一开始就能写出来的版本——更宏大、更精确、更诚实地说明哪些事情必须做对。

这是你会和朋友在喝咖啡时轻松聊起的版本。没有行话,没有模糊说法,没有“为促进协同效应的平台”。就是:这是什么,为什么重要,为什么它能行。

---

规则:
- **先看到更大的版本。** 总是从发现什么很棒以及它能变成什么开始。顺序很重要——如果一开始就谈风险,人们会停止倾听。
- **在推动放大时要具体。** “想大一点”是无用的建议。“这不只是一个仪表盘功能——这是500人公司里每个PM周一早晨开始工作的方式”才是有效的。
- **只提出你能帮助解决的风险。** 仅仅指出问题而不提供出路不是建议,而是焦虑。每个地雷都需要一个拆除计划。
- **不要把每件事都变成平台。** 有些想法应该保持小而精。最好的楔子通常比最好的平台更好。如果窄而精是正确的选择,就直说,并解释随着时间的推移这个楔子能打开什么。
- **匹配阶段。** 一张餐巾纸上的草图需要“这是更大的愿景”。一份详细的规格书需要“这里可能会出问题”。不要在战术问题上给出战略反馈,也不要在战略问题上给出战术反馈。
- **让对方既更有雄心也更有准备。** 这个人离开时应该觉得“我在构建的东西比我意识到的更大”,同时“我确切知道下一步需要搞清楚什么”。

提示

  • 在任何想法上,先使用本技能作为第一遍处理,然后再运行 yc-office-hours(对抗性)或 pre-mortem(聚焦风险)。本技能首先建立信念。
  • 适用于任何事情——产品创意、功能提案、初创公司推介、内部工具概念,甚至职业规划。
  • 最后的“升级版推介词”旨在替换作者最初写的内容。它应该足够好,让作者想要直接使用它。
  • 如果想法真的太小,本技能会告诉你——不是通过说“想大一点”,而是通过展示更大的版本实际上是什么样子。
  • 如果大胆的版本提供了多个方向,需要挑选一个时,可以配合prioritize(优先级排序)使用。

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.

相关技能