Communitygithub.com

amplitude/builder-skills

为你的产品设计产品主导的增长策略——分类你的PLG动向、定义激活与变现架构、选择分销渠道、规划PLG到销售的桥梁,并构建防御性。融入AI时代的分销、定价和用户期望变化。适用于构建或重塑增长策略时使用。

builder-skills 是什么?

这个技能可以帮助开发者和产品团队系统性地构建产品主导增长(PLG)策略,从用户发现产品的初始阶段到激活、留存、付费和扩展,全面覆盖增长架构设计。它强调基于当前市场实际运作的机制进行策略设计,而非依赖过时的“2018年剧本”。技能支持多个平台,包括Claude Code、Cursor和Codex,通过七步框架(分类PLG动向、设计激活架构、变现架构、分销架构、PLG到销售桥梁和防御性设计)引导用户输出可执行的行动计划。其核心价值在于,它不仅仅提供理论指导,而是将AI时代的分销侵蚀、高激活门槛、真实成本变化等现实挑战融入每一步决策,帮助团队避免常见陷阱,并优先考虑创新而非优化,从而在快速变化的市场中建立持久优势。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/growth-skills/skills/build-plg-strategy

在你喜欢的 AI 中提问

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

文档

构建产品主导增长(PLG)策略

为你的产品设计增长架构——从用户如何发现你,到他们如何激活、留存、付费和扩展。基于当前市场实际运作的机制,而非2018年的剧本。

产品主导增长意味着你的产品是获取、激活、留存和扩展的主要引擎。但PLG并非单一概念——它是一个由分销、激活、变现和防御性交织而成的架构。本技能帮助你从头设计这一架构,或对现有架构进行压力测试。


领域背景

仍然有效的PLG基础原则

以下原则未曾改变,是所有PLG动向的基石:

  • 产品是最好的销售员。 用户希望先尝后买。自助式发现比推销更值得信赖。如果你的产品无法展示自身价值,任何营销都无法拯救。
  • 产品合格信号胜过营销合格线索。 使用产品合格线索的公司转化率达25-30%,而营销合格线索仅为5-10%。PLG公司的客户获取成本约为销售主导方式的十分之一。
  • 价值实现时间是核心。 只有约33%的注册用户能触发“啊哈”时刻。顶级PLG公司通过将价值实现时间压缩到分钟级而非小时级,将这一比例提升至65%以上。
  • 激活驱动下游一切。 已激活用户的长期留存率高出2-5倍,且70-80%的完全激活用户会转化为付费用户。大多数自认为有留存或变现问题的公司,实际是激活问题。

已发生变化的部分

多项力量重塑了PLG的实际运作方式:

  • 激活门槛更高。 用户现在以“60秒内交付价值”的产品为基准衡量入门体验。多步骤设置向导已显过时。最佳产品将设置和价值交付压缩为单一交互。
  • 传统分销渠道正在萎缩。 随着用户转向AI助理而非网站获取答案,SEO流量在下降。社交平台限制外链。原本持续数月的营销活动生命周期如今数天就会耗尽。新渠道——AI助理推荐、产品原生病毒传播、社区——正在取代旧渠道。
  • 真实成本改变免费增值经济学。 AI功能具有真实的每用户销售成本。免费用户活跃烧钱时,过去那种边际成本近乎为零的慷慨免费层级模式就行不通了。定价策略必须在慷慨与可持续性之间取得平衡。
  • 产品-市场契合是持续过程,而非终点。 竞争格局每周变化。曾经需要花几个季度才能完成的特性采用曲线,如今压缩到几周。测量节奏必须跟上市场速度。
  • 创新胜过优化。 当竞争对手能在几天内推出类似功能时,增量A/B测试的小胜无法累积成持久优势。获胜团队交付的是全新体验,而非优化现有漏斗。

何时适合PLG?

如果以下情况成立,PLG不适用作为主要策略:

  • 你的产品无法提供自助式的“啊哈”时刻(需要大量定制设置、数据迁移或集成后用户才能看到价值)
  • 你的买家和用户过于脱节,产品使用信号无法触及购买决策者
  • 你的产品解决的是客户尚未意识到的问题
  • 你的市场完全由具有正式采购流程的企业买家组成

即便如此,防御性地借用PLG元素(交互式演示、现有账户内额外用户的自助激活、限时试用)仍能加快你的销售流程。


何时使用

  • 设计新产品增长策略
  • 重构现有产品的增长架构
  • 评估PLG是否为合适的策略(进攻性或防御性)
  • 规划分销渠道及市场推广
  • 为自助式产品设计定价与包装
  • 构建从PLG到企业销售的桥梁

提示

你是一位增长策略师,研究过增长最快的产品主导公司的实际增长机制——而非理论,而是具体操作。你明白PLG是环环相扣的决策架构,而非单一战术。你对什么有效、什么无效以及什么已经改变直言不讳。

给定以下关于我的产品和增长目标的背景信息:$ARGUMENTS

按以下步骤推进:

步骤1:分类你的PLG动向

你的PLG是进攻性还是防御性?

  • 进攻性PLG: 你的产品天生就是为了驱动自身增长而设计的。产品体验就是增长引擎。自助式采用是主要收入路径。
  • 防御性PLG: 你的产品可以适应一定程度上的自助式增长,但大部分收入来自其他策略。你使用PLG元素来防御来自底层的PLG竞争对手的入侵。

对这一点要诚实。两种策略所需的投入水平和架构决策不同。

你的产品玩哪种游戏?

  • 注意力: 成功 = 花费的时间。用户为了内容、娱乐或持续互动而来。
  • 交易: 成功 = 交易量。用户为了购买、销售或交换价值而来。
  • 生产力: 成功 = 高效完成工作。用户为了更快或更好地完成某项工作而来。

游戏类型决定了你的北极星指标、激活定义和自然变现模式。不要试图同时玩三种。

步骤2:设计激活架构

激活是PLG中投入产出比最高的领域。做好这一点,下游一切都会改善。

定义“啊哈”时刻。 用户首次体验到产品核心价值的具体动作是什么?这不是登录、不是完成个人资料、不是完成教程。而是用户心中产生“这真有用”的瞬间。要精确。

设定价值实现时间的基准。 新用户目前需要多长时间才能到达“啊哈”时刻?当前强PLG产品的标准是首个价值实现时间低于60秒。如果以天计,找出延迟所在——是数据设置、配置、学习曲线,还是等待他人?

设计首次使用体验。 最佳激活将设置和价值交付压缩为单一交互:

  • 产品最少需要知道什么才能交付价值?(角色、目标、一条背景信息)
  • 产品能否在用户动手做任何工作之前交付结果?
  • 首次体验是像使用产品,还是像填写表单?

分层衡量激活。 分别跟踪三个不同阶段:

  1. 设置: 环境就绪(账户创建、数据连接等)
  2. “啊哈”: 用户首次体验核心价值
  3. 习惯: 用户定期回来并重复“啊哈”时刻,达到自然频率

大多数团队混淆了这些阶段。完成了设置但从未达到“啊哈”时刻的用户并非已激活。

考虑团队,而非个人。 如果你的产品是协作型的,请单独定义团队激活与个人激活。跟踪团队何时成功协作并共同获取价值,而不仅仅是个人用户何时注册。

步骤3:设计变现架构

选择随价值交付扩展的定价模型:

  • 按席位: 简单、可预测,但与AI产品价值交付方式越来越不匹配。每个席位代表一个有独特价值的独立用户时适用。
  • 按使用量: 成本与价值对齐,但影响销售薪酬、预测和客户预算。每个消费单位都能产生可见输出时适用。
  • 按点数: 给予用户所有功能权限,限制用量。升级触发点是数量而非能力——更自然的升级路径。增长快速的AI产品中最常见的模式。
  • 混合型: 基础订阅加按使用量计费组件。提供可预测性并兼容价值对齐。
  • 按结果: 按交付的结果收费(合格线索、已解决问题的工单、已完成的交易)。定价的前沿领域,但需要对产品交付可衡量结果的能力有信心。

设计免费到付费的边界。 免费体验必须足够吸引人以交付“啊哈”时刻,但又有限度以创造自然升级触发点。关键原则:限制数量或频率,而非能力。从未体验过完整产品品质的用户永远无法理解他们付费购买的是什么。

测试定价清晰度。 如果你不能用一句话解释你的定价,那就太复杂了。用户应清楚理解他们能得到什么以及什么会触发升级。

警惕定价过低。 为了快速增长而设定低价格的诱惑会产生结构性赤字,一旦用户锚定在某个数字上就很难逆转。为交付的价值定价,而非仅为采用速度定价。

步骤4:设计分销架构

传统渠道正在萎缩。根据用户现在实际发现产品的地方来设计分销。

审计你当前的渠道组合。 对于每个渠道,评估:

  • 当前流量和趋势方向(增长、稳定、下降)
  • 每个获取用户的成本和质量(这些用户是否激活和留存?)
  • 防御性(这个渠道能否被破坏或复制?)

评估新兴渠道:

  • AI助理推荐: 当用户向AI助理询问你所在类别的解决方案时,你的产品如何出现?你是否针对AI系统评估和推荐产品的方式进行了优化(清晰的结构化内容、权威信号、多格式呈现)?
  • 产品原生病毒传播: 使用你的产品是否会自然产生工具体、输出物或共享体验,从而向新用户展示它?这是目前最可靠的分销渠道。
  • 社区主导增长: 活跃社区(论坛、Slack/Discord群组、模板库)推动采用的速度比博客内容快2-3倍。用户生成内容和同行验证胜过品牌营销。
  • 多表面分销: 你的产品功能能否在用户已花费时间的表面上(Slack、Teams、AI助理)访问,而非要求他们访问你的应用?

做出平台选择。 根据用户实际所在的位置(而非三年前的位置),挑选2-3个你将重点投资的渠道。

步骤5:设计PLG到销售桥梁

纯自助式PLG只能做到一定程度。大多数成功的PLG公司会在获得产品使用信号后加入销售层。

定义产品合格账户(PQA)和产品合格线索(PQL)。

  • PQA: 基于产品使用情况的账户级资格认定——数量、速度、广度、团队规模、集成深度。告知你何时账户准备好进行销售接触。
  • PQL: 账户内的购买决策者。并非所有用户都是买家。拥有PQA但没有PQL其实是最佳机会——账户已获得价值,但你尚未与决策者建立联系。

构建行为评分。 将产品使用信号与公司统计特征数据结合,生成准备销售接触的账户排名。不要将没有上下文活跃用户列表交给销售——那会浪费代表时间并削弱对PLG策略的信任。

设计交接点。 自助式账户何时转变为销售对话?触发点应基于行为信号(团队扩展、达到使用限制、采用企业功能),而非基于时间的规则。

步骤6:设计防御性

在竞争对手能快速复制功能的市场中,你的护城河不在于代码。从一开始就设计防御性。

评估五种护城河策略:

  1. 数据和上下文锁定: 用户因存储在你系统中的数据而获得更好体验。使用越多,越难离开。
  2. 深度工作流集成: 将产品嵌入用户现有工具和工作流。转换成本不是学习新产品——而是拆除集成。
  3. 社区和内容生态系统: 用户生成的模板、共享知识、同行网络。竞争对手无法通过打造更好的产品来复制这一点。
  4. 网络效应: 每个额外用户都使产品对现有用户更有价值。在协作型和市场型产品中表现突出。
  5. 行为智能: 对用户行为、预测留存和触发扩展的深度理解。这随时间积累,无法被复制。

对于每种策略,评估:是否适用于你的产品?今天有多强?需要做些什么来加强?

步骤7:构建行动计划

将一切整合为优先级的计划。

交付物:

  1. PLG分类 —— 进攻性 vs. 防御性,哪种游戏,PLG是否适合作为主要策略
  2. 激活架构 —— “啊哈”时刻定义、价值实现时间目标、首次使用体验设计、测量分层
  3. 变现架构 —— 定价模型建议、免费到付费边界、包装结构
  4. 分销架构 —— 渠道评估、新兴渠道机会、平台选择建议
  5. PLG到销售桥梁 —— PQA/PQL定义、行为评分方法、交接设计
  6. 防御性计划 —— 投资哪些护城河及如何投资
  7. 前三大行动 —— 未来30天内最高杠杆率的事,按影响排序。每个以动词开头。具体到可以明天开始执行。
  8. 停止做的事 —— 团队应放弃的PLG反模式。要直接。

不要模棱两可。一个模糊的策略比一个错误但可以测试和迭代的策略更糟糕。


提示

  • 带上你当前的指标(注册数、激活率、价值实现时间、留存率、付费转化率、渠道细分)。数据越多

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.

相关技能