ork-assess
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a request asks to assess, rate,…
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
$ npx -y skills add yonatangross/orchestkit --skill competitive-analysis --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/competitive-analysisContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: competitive-analysis compatibility: "Claude Code 2.1.251+" description: "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." version: 1.0.0 author: OrchestKit user-invocable: false disable-model-invocation: false complexity: medium persuasion-type: guidance tags: [porter, swot, competitive, battlecard, moat, five-forces, landscape] context: fork agent: product-strategist metadata: category: document-asset-creation allowed-tools: [Read, Glob, Grep, WebFetch, WebSearch]
Frameworks for analyzing competitive position and industry dynamics.
| 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: [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]
+-------------------------+-------------------------+ | 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 | +-------------------------+-------------------------+
| | 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: [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]
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 PRICEIdentify whitespace — quadrants with no incumbents that align with unmet buyer needs.
# 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 |
---
Version: 1.0.0
The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install `ork` for stable (v9.x), or `ork-alpha` for the v10 line, which ships daily.
Repo: yonatangross/orchestkit
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a request asks to assess, rate,…
Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request asks to brainstorm, think…
Map an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a request asks how a system works, where…
Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a feature that already has an agreed…
Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a request asks to review a PR, review…
Verify that existing work is ready to merge, release, or hand off using an explicit evidence contract. Use when a request asks to verify, validate, prove,…