本文へ移動
cccskills
無料GitHub で公開

competitor-analysis

Analyze competitors using Porter's four-component model - drivers, assumptions, strategy, capabilities.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.2 KB
  • agents/openai.yaml186 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Competitor Analysis (Porter)

Analyze competitors using Porter's four-component model.

When to Use

When you need to understand a competitor's strategy, capabilities, and likely moves.

The Framework

Porter's four components:

ComponentQuestions
ObjectivesWhat are they trying to achieve? (growth, profit, share, positioning)
Current StrategyHow are they competing? (segments, pricing, channels, roadmap)
AssumptionsWhat do they believe about the market, themselves, and rivals?
CapabilitiesWhat can they actually do? (resources, competencies, gaps)

The Process

1. Objectives (Future Goals)

  • Economic goals (growth, profitability, market share)
  • Strategic goals (positioning, tech leadership, ecosystem)
  • Timeframes and indicators
  • Priority ranking

2. Current Strategy

  • Target segments and value proposition
  • Pricing and monetization
  • Go-to-market (channels, partnerships)
  • Product roadmap themes
  • Geographic posture

3. Assumptions

  • About the industry (demand, regulation, tech trajectory)
  • About themselves (core competencies, cost position)
  • About you and other rivals
  • Implicit beliefs inferred from behavior

4. Capabilities

  • Tangible: cost structure, capacity, balance sheet
  • Intangible: brand, IP, data, culture, talent
  • Activities across value chain
  • Notable gaps and constraints

5. Synthesize: Likely Moves

Based on the four components:

  • What will they respond to quickly vs. ignore?
  • Probable near-term moves (ranked by likelihood)
  • Expected response speed by move type

6. Implications for Us

  • Risks to monitor
  • Opportunities to exploit
  • Recommended counter-moves
  • "If they do X, we do Y" mapping

Output

  • Executive snapshot
  • Four components analysis
  • Likely moves and response profile
  • Implications and recommendations
  • Evidence sources
  • Unknowns and validation plan

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Surface and categorize assumptions underlying product strategy. Use early in development to document what you're betting on.

日本語の概要は準備中です。原文の説明を表示しています。

itseffi/agentic-os1142026年10月7日 更新

Prioritize assumptions by risk and importance. Use after assumption mapping to decide what to test first.

日本語の概要は準備中です。原文の説明を表示しています。

itseffi/agentic-os1142026年10月7日 更新

Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.

日本語の概要は準備中です。原文の説明を表示しています。

itseffi/agentic-os1142026年10月7日 更新

Design backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.

日本語の概要は準備中です。原文の説明を表示しています。

itseffi/agentic-os1142026年10月7日 更新

Turn ideas into designs through collaborative dialogue. Use before any creative work - features, components, or modifications.

日本語の概要は準備中です。原文の説明を表示しています。

itseffi/agentic-os1142026年10月7日 更新

Check Google Calendar for today's schedule. Use during daily planning or when user asks about their calendar.

日本語の概要は準備中です。原文の説明を表示しています。

itseffi/agentic-os1142026年10月7日 更新

itseffi のスキルをすべて見る

このスキルの問題を報告する