Agent skill

competitive-analysis

Porter's Five Forces, SWOT analysis, and competitive landscape mapping. Use when analyzing market position, evaluating competitive threats, building battlecards, or assessing industry dynamics.

Stars 143
Forks 15

Install this agent skill to your Project

npx add-skill https://github.com/yonatangross/orchestkit/tree/main/plugins/ork/skills/competitive-analysis

Metadata

Additional technical details for this skill

category
document-asset-creation

SKILL.md

Competitive Analysis

Frameworks for analyzing competitive position and industry dynamics.

When to Use Porter's vs. SWOT

Framework Use When
Porter's Five Forces Evaluating industry attractiveness; new market entry; strategic positioning
SWOT Internal capability assessment; go/no-go decisions; strategy planning
Competitive Landscape Map Visualizing whitespace; investor decks; positioning against specific competitors
Competitor Profiles Battlecards for sales; feature gap analysis; threat assessment

Use Porter's to understand the structural forces shaping the industry. Use SWOT to assess your specific position within it. Combine both for a complete picture.

Porter's Five Forces Template

markdown
## Porter's Five Forces: [Industry/Market]

### 1. Competitive Rivalry — Intensity: HIGH / MEDIUM / LOW
| Factor | Assessment |
|--------|------------|
| Number of competitors | |
| Industry growth rate | |
| Product differentiation | |
| Exit barriers | |

### 2. Threat of New Entrants — Threat Level: HIGH / MEDIUM / LOW
| Barrier | Strength |
|---------|----------|
| Economies of scale | |
| Brand loyalty | |
| Capital requirements | |
| Network effects | |
| Switching costs | |

### 3. Bargaining Power of Suppliers — Power: HIGH / MEDIUM / LOW
[Key suppliers, switching cost, concentration]

### 4. Bargaining Power of Buyers — Power: HIGH / MEDIUM / LOW
[Price sensitivity, alternatives available, buyer concentration]

### 5. Threat of Substitutes — Threat: HIGH / MEDIUM / LOW
[Alternative ways customers solve the same problem]

### Overall Industry Attractiveness: X/10
[Summary: which forces are most significant and why]

SWOT Analysis

+-------------------------+-------------------------+
|       STRENGTHS         |       WEAKNESSES        |
|       (Internal +)      |       (Internal -)      |
| * What we do well       | * Where we lack         |
| * Unique resources      | * Resource gaps         |
| * Competitive advantages| * Capability limits     |
+-------------------------+-------------------------+
|      OPPORTUNITIES      |         THREATS         |
|       (External +)      |       (External -)      |
| * Market trends         | * Competitive pressure  |
| * Unmet needs           | * Regulatory changes    |
| * Technology shifts     | * Economic factors      |
+-------------------------+-------------------------+

TOWS Matrix (SWOT to Strategy)

Strengths Weaknesses
Opportunities SO: Use strengths to capture opportunities WO: Fix weaknesses to unlock opportunities
Threats ST: Use strengths to mitigate threats WT: Minimize weaknesses, avoid threats

Competitor Profile Template

markdown
## Competitor: [Name]

### Overview
- Founded: [Year] | Funding: $[Amount] | Employees: [N]
- Target customer: [Segment]
- Pricing: [Model and range]

### Strengths / Weaknesses
+ [Strength 1]
+ [Strength 2]
- [Weakness 1]
- [Weakness 2]

### Threat Assessment: HIGH / MEDIUM / LOW
- [Why this threat level]
- [Our differentiation vs. this competitor]

Competitive Landscape Map

Plot competitors on two axes that matter most to buyers (e.g., price vs. features, ease of use vs. power):

                    HIGH PRICE
                        |
     Premium Leaders    |    Luxury Niche
   +-------------+      |      +-------------+
   |  [Comp A]   |      |      |  [Comp B]   |
   +-------------+      |      +-------------+
                        |
LOW ────────────────────+──────────────────── HIGH
FEATURES                |                   FEATURES
                        |
   +-------------+      |      +-------------+
   |  [Comp C]   |      |      |    [US]     |
   +-------------+      |      +-------------+
     Budget Options     |    Value Leaders
                        |
                    LOW PRICE

Identify whitespace — quadrants with no incumbents that align with unmet buyer needs.

GitHub Signals for Competitive Tracking

bash
# Star count and momentum
gh api repos/owner/repo --jq '{stars: .stargazers_count, forks: .forks_count}'

# Shipping velocity (recent releases)
gh release list --repo owner/repo --limit 5

# Community size
gh api repos/owner/repo/contributors --jq 'length'
Signal Check Frequency
Star growth Weekly
Release notes Per release
Pricing changes Monthly
Feature launches Per announcement
Full analysis Quarterly

References

  • Competitive Analysis Rules — Porter's, SWOT, landscape map, competitor profile templates
  • Competitive Analysis Guide — Research methodology, data sources, update cadence

Related Skills

  • ork:market-sizing — Quantify opportunity size alongside competitive landscape
  • ork:business-case — Build financial justification informed by competitive position
  • ork:product-frameworks — Full product strategy toolkit (value prop, prioritization, OKRs)

Version: 1.0.0

Expand your agent's capabilities with these related and highly-rated skills.

yonatangross/orchestkit

expect

Diff-aware AI browser testing — analyzes git changes, generates targeted test plans, and executes them via agent-browser. Reads git diff to determine what changed, maps changes to affected pages via route map, generates a test plan scoped to the diff, and runs it with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, running regression checks on changed components, or validating that recent code changes don't break the user-facing experience.

143 15
Explore
yonatangross/orchestkit

github-operations

GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.

143 15
Explore
yonatangross/orchestkit

chain-patterns

Chain patterns for CC 2.1.71 pipelines — MCP detection, handoff files, checkpoint-resume, worktree agents, CronCreate monitoring. Use when building multi-phase pipeline skills. Loaded via skills: field by pipeline skills (fix-issue, implement, brainstorm, verify). Not user-invocable.

143 15
Explore
yonatangross/orchestkit

storybook-mcp-integration

Storybook MCP server integration for component-aware AI development. Covers 6 tools across 3 toolsets (dev, docs, testing): component discovery via list-all-documentation/get-documentation, story previews via preview-stories, and automated testing via run-story-tests. Use when generating components that should reuse existing Storybook components, running component tests via MCP, or previewing stories in chat.

143 15
Explore
yonatangross/orchestkit

component-search

Search 21st.dev component registry for production-ready React components. Finds components by natural language description, filters by framework and style system, returns ranked results with install instructions. Use when looking for UI components, finding alternatives to existing components, or sourcing design system building blocks.

143 15
Explore
yonatangross/orchestkit

ai-ui-generation

AI-assisted UI generation patterns for json-render, v0, Bolt, and Cursor workflows. Covers prompt engineering for component generation, review checklists for AI-generated code, design token injection, refactoring for design system conformance, and CI gates for quality assurance. Use when generating UI components with AI tools, rendering multi-surface MCP visual output, reviewing AI-generated code, or integrating AI output into design systems.

143 15
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results