Skip to main content
ClaudeWave
Skill188 estrellas del repoactualizado today

competitive-analysis

Strategic analysis frameworks including Porter's Five Forces (industry attractiveness), SWOT (internal positioning), and competitive landscape mapping with battlecard generation. Produces competitor profiles, feature gap analysis, and positioning recommendations. Use when analyzing market position, evaluating threats, or building sales battlecards.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/yonatangross/orchestkit /tmp/competitive-analysis && cp -r /tmp/competitive-analysis/plugins/ork/skills/competitive-analysis ~/.claude/skills/competitive-analysis
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

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](rules/market-competitive.md) — Porter's, SWOT, landscape map, competitor profile templates
- [Competitive Analysis Guide](references/competitive-analysis-guide.md) — 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
accessibilitySkill

Accessibility patterns for WCAG 2.2 compliance, keyboard focus management, React Aria component patterns, cognitive inclusion, native HTML-first philosophy, and user preference honoring. Use when implementing screen reader support, keyboard navigation, ARIA patterns, focus traps, accessible component libraries, reduced motion, or cognitive accessibility.

agent-orchestrationSkill

Agent orchestration patterns for agentic loops, multi-agent coordination, alternative frameworks, and multi-scenario workflows. Use when building autonomous agent loops, coordinating multiple agents, evaluating CrewAI/AutoGen/Swarm, or orchestrating complex multi-step scenarios.

ai-ui-generationSkill

AI-assisted UI generation patterns for json-render, v0.app, Google Stitch, Bolt Cloud, and Cursor workflows. Covers prompt engineering for component and full-stack app 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.

analyticsSkill

Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs, or understanding usage patterns.

animation-motion-designSkill

Animation and motion design patterns using Motion library (formerly Framer Motion) and View Transitions API. Use when implementing component animations, page transitions, micro-interactions, gesture-driven UIs, or ensuring motion accessibility with prefers-reduced-motion.

api-designSkill

API design patterns for REST/GraphQL framework design, versioning strategies, and RFC 9457 error handling. Use when designing API endpoints, choosing versioning schemes, implementing Problem Details errors, or building OpenAPI specifications.

architecture-decision-recordSkill

Use this skill when documenting significant architectural decisions. Provides ADR templates following the Nygard format with sections for context, decision, consequences, and alternatives. Use when writing ADRs, recording decisions, or evaluating options.

architecture-patternsSkill

Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right architecture tier for project scope.