Communitygithub.com

7가지 경쟁력 분석 (7 Powers)

Hamilton Helmer의 7 Powers 프레임워크를 사용하여 비즈니스, 제품 또는 기능의 경쟁 우위와 전략적 지속 가능성을 분석합니다. 사용자가 경쟁 해자(moat), 전략적 포지셔닝, 힘(Power) 분석, 방어 가능성, 경쟁 우위 또는 '7 Powers'에 대해 질문할 때 사용하세요.

7가지 경쟁력 분석 (7 Powers)란 무엇인가요?

이 스킬은 Hamilton Helmer의 '7 Powers' 프레임워크를 기반으로 비즈니스, 제품 또는 기능의 지속 가능한 경쟁 우위를 평가하는 AI 어시스턴트용 분석 도구입니다. 사용자가 '경쟁 해자', '전략적 포지셔닝', '방어 가능성' 등과 같은 용어를 언급할 때 자동으로 활성화되며, 분석 대상(회사, 제품 라인, 특정 기능)을 명확히 하고 7가지 힘(규모 경제, 네트워크 경제, 반대 포지셔닝, 전환 비용, 브랜딩, 독점 자원, 프로세스 파워) 각각에 대해 현재 보유 여부, 강도, 지속 가능성을 체계적으로 평가합니다. 또한 힘 간의 시너지 효과를 식별하고, 강화, 개발, 방어를 위한 전략적 권장 사항을 제시합니다. 이 프레임워크는 신규 기능/제품 결정, 경쟁 위협 평가, 초기 단계 스타트업 분석 등 다양한 상황에 맞게 조정할 수 있으며, 결과는 표 형식의 상세 분석과 실행 가능한 전략적 조언으로 구성됩니다.

지원 대상~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 Powers 프레임워크를 적용하여 비즈니스, 제품 또는 기능이 지속적인 차별적 수익을 가능하게 하는 내구성 있는 경쟁 우위('Powers')를 보유하고 있는지 평가합니다.

각 힘(Power)에 대한 상세한 정의, 속성 및 예시는 framework.md를 참조하세요.

워크플로우

  1. 대상 명확히 하기: 분석 대상을 파악합니다 — 회사, 제품 라인 또는 특정 기능. 모호한 경우 사용자에게 질문합니다.

  2. 7가지 힘 모두 스캔하기: 각 힘에 대해 대상을 평가합니다:

    • 규모 경제 (Scale Economies)
    • 네트워크 경제 (Network Economies)
    • 반대 포지셔닝 (Counter-Positioning)
    • 전환 비용 (Switching Costs)
    • 브랜딩 (Branding)
    • 독점 자원 (Cornered Resource)
    • 프로세스 파워 (Process Power)
  3. 각 힘 평가하기: 세 가지 차원을 사용합니다:

    • 보유 여부?: 대상이 현재 이 힘을 보유하고 있습니까?
    • 강도: 장벽이 얼마나 강력합니까? (없음 / 약함 / 보통 / 강함)
    • 지속 가능성: 얼마나 오래 지속될 것입니까? (취약 / 보통 / 내구성 있음)
  4. 힘 조합 식별하기: 서로를 강화하는 힘 조합을 식별합니다 (예: 규모 경제 + 네트워크 효과는 성장 루프를 만듭니다).

  5. 전략적 행동 제안하기: 비즈니스가 힘을 강화, 개발 또는 방어하기 위해 무엇을 해야 합니까?

출력 템플릿

분석에는 다음 구조를 사용합니다:

# 7가지 힘 분석: [대상]

## 요약
[전반적인 전략적 위치와 식별된 주요 힘에 대한 1-2문장]

## 힘 평가

| 힘 (Power) | 보유 여부? | 강도 | 지속 가능성 | 비고 |
|-------|----------|----------|------------|-------|
| 규모 경제 | 예/아니오 | 없음-강함 | 취약-내구성 있음 | [간략한 근거] |
| 네트워크 경제 | 예/아니오 | 없음-강함 | 취약-내구성 있음 | [간략한 근거] |
| 반대 포지셔닝 | 예/아니오 | 없음-강함 | 취약-내구성 있음 | [간략한 근거] |
| 전환 비용 | 예/아니오 | 없음-강함 | 취약-내구성 있음 | [간략한 근거] |
| 브랜딩 | 예/아니오 | 없음-강함 | 취약-내구성 있음 | [간략한 근거] |
| 독점 자원 | 예/아니오 | 없음-강함 | 취약-내구성 있음 | [간략한 근거] |
| 프로세스 파워 | 예/아니오 | 없음-강함 | 취약-내구성 있음 | [간략한 근거] |

## 주요 힘 심층 분석
[보통 또는 강함으로 평가된 각 힘에 대해 2-3문단 제공:
- 평가를 뒷받침하는 증거
- 이 힘이 경쟁사에 대한 장벽을 만드는 방법
- 이 힘에 대한 위험 또는 취약점]

## 힘 시너지 효과
[대상이 보유한 힘 간의 강화 조합 식별]

## 전략적 권장 사항
1. **강화**: [기존 힘을 심화하는 방법]
2. **개발**: [새로운 힘을 구축할 수 있는 방법과 그 방법]
3. **방어**: [현재 힘을 위협하는 요소와 보호 방법]

분석 조정하기

신규 기능 또는 제품 결정의 경우: 힘 강화(기존 힘을 강화하는가?), 힘 확장(새로운 힘을 창출하는가?), 힘 방어(위협으로부터 보호하는가?)에 초점을 맞춥니다.

경쟁 위협 평가의 경우: 경쟁사가 보유한 힘, 신흥 경쟁사가 개발 중인 힘, 기존 힘이 무력화될 수 있는 방법에 초점을 맞춥니다.

초기 단계 스타트업의 경우: 비즈니스 모델을 고려하여 어떤 힘이 형성될 수 있는지, 개발 일정은 어떻게 되는지 등 힘 잠재력에 초점을 맞춥니다. 힘 발전 관점(Power Progression lens)을 사용합니다: 잠재력 → 실현 → 지속적 수익.

예시

사용자: "Figma의 경쟁적 위치를 분석해줘"

주요 결과는 다음과 같습니다:

  • 네트워크 경제 (강함/내구성 있음): 다중 사용자 협업은 직접적인 네트워크 효과를 창출합니다. 플러그인 생태계는 간접적인 효과를 만듭니다.
  • 전환 비용 (보통/내구성 있음): 팀 디자인 시스템, 컴포넌트 라이브러리 및 워크플로우 통합은 절차적 고착(lock-in)을 만듭니다.
  • 반대 포지셔닝 (보통/취약): 브라우저 네이티브 접근 방식은 처음에 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.

관련 스킬