Communitygithub.com

amplitude/builder-skills

使用 Hamilton Helmer 的 7 种力量框架分析业务、产品或功能,评估其竞争优势和战略持久性。当用户询问竞争护城河、战略定位、力量分析、防御性、竞争优势或“7 Powers”时使用。

builder-skills 是什么?

该技能旨在帮助 AI 代理(如 Claude Code、Cursor)对给定的业务、产品或功能进行全面的竞争战略分析。它基于 Hamilton Helmer 的“7 种力量”框架,通过系统性地评估规模经济、网络效应、逆定位、转换成本、品牌、独有资源和流程力量这七个维度,来判断目标的竞争优势和战略持久性。用户只需提出一个分析对象(例如一个公司、产品线或功能),技能就会引导代理完成从澄清对象、逐项评估到输出结构化分析报告的完整工作流。它特别适用于产品经理、战略分析师和创业者进行竞争态势评估。该技能支持在多种 AI 代理平台下工作,通过清晰的 Markdown 模板输出,包括执行摘要、力量评估表、深度分析、协同效应识别及战略建议,确保分析结果既系统又具有可操作性。

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

在你喜欢的 AI 中提问

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

文档

7种力量竞争分析

应用 Hamilton Helmer 的 7 种力量框架评估一个业务、产品或功能是否具有持久的竞争优势(“力量”),从而能够实现持续的差异化回报。

有关每种力量的详细定义、属性和示例,请参阅 framework.md。

工作流程

  1. 澄清主体:确定分析的对象——是公司、产品线还是特定功能。如果不明确,请向用户询问。

  2. 扫描全部7种力量:针对每种力量评估主体:

    • 规模经济 (Scale Economies)
    • 网络效应 (Network Economies)
    • 逆定位 (Counter-Positioning)
    • 转换成本 (Switching Costs)
    • 品牌 (Branding)
    • 独有资源 (Cornered Resource)
    • 流程力量 (Process Power)
  3. 从三个维度评估每种力量:

    • **当前是否存在?**主体目前是否拥有这种力量?
    • 强度:壁垒有多强?(无 / 弱 / 中等 / 强)
    • 持久性:能持续多久?(脆弱 / 中等 / 持久)
  4. 识别力量组合:确认能够相互加强的力量组合(例如,规模经济 + 网络效应可形成增长循环)。

  5. 推荐战略行动:业务应该做什么来加强、发展或防御其力量?

输出模板

使用以下结构进行分析:

# 7种力量分析:[主体]

## 执行摘要
[1-2句话总结整体战略定位和识别出的关键力量]

## 力量评估

| 力量 | 当前存在? | 强度 | 持久性 | 备注 |
|-------|----------|------------|------------|-------|
| 规模经济 | 是/否 | 无-强 | 脆弱-持久 | [简要理由] |
| 网络效应 | 是/否 | 无-强 | 脆弱-持久 | [简要理由] |
| 逆定位 | 是/否 | 无-强 | 脆弱-持久 | [简要理由] |
| 转换成本 | 是/否 | 无-强 | 脆弱-持久 | [简要理由] |
| 品牌 | 是/否 | 无-强 | 脆弱-持久 | [简要理由] |
| 独有资源 | 是/否 | 无-强 | 脆弱-持久 | [简要理由] |
| 流程力量 | 是/否 | 无-强 | 脆弱-持久 | [简要理由] |

## 深度分析:关键力量
[对于被评为中等或强的每种力量,提供2-3段,涵盖:
- 支持该评估的证据
- 这种力量如何为竞争对手制造壁垒
- 该力量面临的风险或弱点]

## 力量协同
[识别主体所拥有的力量之间相互增强的组合]

## 战略建议
1. **加强**:[如何深化现有的力量]
2. **发展**:[可以构建哪些新力量,以及如何构建]
3. **防御**:[哪些因素威胁当前力量,以及如何保护它们]

调整分析

对于新功能或产品决策:重点放在力量增强(这能否增强现有力量?)、力量扩展(是否创造新力量?)和力量防御(能否防御威胁?)。

对于竞争威胁评估:重点放在竞争对手拥有哪些力量、哪些新兴竞争对手正在发展力量,以及现有力量如何可能被削弱。

对于早期阶段公司:重点放在力量潜力——基于业务模式可以形成哪些力量,以及发展的时间表。使用力量发展视角:潜力 → 实现 → 持续回报。

示例

用户:“分析 Figma 的竞争地位”

关键发现包括:

  • 网络效应(强/持久):多人协作创造直接网络效应;插件生态系统创造间接效应
  • 转换成本(中等/持久):团队设计系统、组件库和工作流集成创造程序性锁定
  • 逆定位(中等/脆弱):基于浏览器的原生方式最初对 Adobe 的桌面模式构成了逆定位,但这种优势在收购后减弱了
  • 协同效应:网络效应 + 转换成本相互加强——团队采用越多,两者都越深

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.

相关技能