Communitygithub.com

7つの力(7 Powers)競争優位分析

Hamilton Helmerの7つの力(7 Powers)フレームワークを用いて、ビジネス、製品、機能の競争優位性と戦略的持続性を分析します。ユーザーが競争上の堀、戦略的ポジショニング、パワー分析、防御可能性、競争優位性、または「7 Powers」について質問した際に使用します。

7つの力(7 Powers)競争優位分析 とは?

このスキルは、Hamilton Helmerの「7つの力(7 Powers)」フレームワークを適用して、ビジネス、製品、機能が持続的な差別的リターンを可能にする強固な競争優位性(「パワー」)を持っているかどうかを評価するためのものです。スキルは、7つの各パワー(規模の経済、ネットワーク経済、カウンターポジショニング、スイッチングコスト、ブランディング、独占的リソース、プロセスパワー)に対して、存在の有無、強度、持続性の3次元で評価するワークフローを提供します。さらに、パワー間の相乗効果の特定や、パワーを強化・開発・防御するための戦略的アクションの推奨を行います。新機能や製品決定、競合脅威評価、初期段階の企業分析など、様々なシナリオに適応可能であり、分析結果は構造化されたテンプレートを使ってレポートとして出力します。このスキルは主としてClaude CodeのようなAIエージェント上で動作し、framework.mdを参照して詳細な定義や例を確認しながら分析を進めます。

対応~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/product-skills/skills/7-powers

お気に入りのAIに質問する

このエージェントスキルを事前に読み込んだ状態で新しいチャットを開きます。

ドキュメント

7つの力(7 Powers)競争優位分析 は何をしますか?

Hamilton Helmerの7つの力(7 Powers)フレームワークを適用して、ビジネス、製品、または機能が持続的な差別的リターンを可能にする強固な競争優位性(「パワー」)を持っているかどうかを評価します。

各パワーの詳細な定義、属性、例については、framework.md を参照してください。

ワークフロー

  1. 分析対象を明確にする: 何を分析するのか(企業、製品ライン、特定の機能)を特定します。曖昧な場合はユーザーに確認します。

  2. 7つのパワーすべてをスキャンする: 分析対象を各パワーに対して評価します。

    • 規模の経済(Scale Economies)
    • ネットワーク経済(Network Economies)
    • カウンターポジショニング(Counter-Positioning)
    • スイッチングコスト(Switching Costs)
    • ブランディング(Branding)
    • 独占的リソース(Cornered Resource)
    • プロセスパワー(Process Power)
  3. 各パワーを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.

関連スキル