Communitygithub.com

amplitude/builder-skills

使用 Hamilton Helmer 的 7 種力量框架分析企業、產品或功能的競爭優勢與策略持久性。當使用者詢問關於競爭護城河、策略定位、力量分析、防禦性、競爭優勢或「7 種力量」時使用。

builder-skills 是什麼?

此技能運用 Hamilton Helmer 的 7 種力量框架,協助分析企業、產品或功能是否具備持久性競爭優勢(即「力量」),從而實現持續的超額回報。它支援多種分析情境,包括新產品/功能決策(著重於力量強化、擴展與防禦)、競爭威脅評估(分析競爭對手的力量與潛在威脅),以及早期階段公司評估(聚焦於力量潛力與發展時間表)。使用者只需明確分析主體,技能便會逐一掃描規模經濟、網路效應、反定位、轉換成本、品牌、關鍵資源與流程力量這七大力量,並從「是否存在」、「強度」與「持久性」三個維度進行評估。最終產出一份結構化報告,包含執行摘要、力量評估表格、關鍵力量深入探討、力量綜效分析與策略建議,協助決策者制定強化、發展或防禦競爭優勢的具體行動方案。

相容平台~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 種力量:逐一評估分析主體與每種力量的對應關係:

    • 規模經濟
    • 網路效應
    • 反定位
    • 轉換成本
    • 品牌
    • 關鍵資源
    • 流程力量
  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.

相關技能