startup-competitors

Name: startup-competitors
Author: ferdinandobons

337installs85forks

How to install startup-competitors?

ferdinandobons/startup-skill/startup-competitors

$npx -y skills add ferdinandobons/startup-skill --skill startup-competitors

Installs into the current project.

Summary

Deep competitive intelligence for any market. Analyzes competitors' products, pricing, customer sentiment, GTM strategy, and growth signals using real web data. Produces battle cards, pricing landscape, and feature matrix. Use when the user wants to understand their competitive l

Files · 1

View on GitHub

SKILL.md

1	# Startup Competitors
2
3	Deep competitive intelligence that goes beyond surface-level profiles. Produces actionable battle cards, pricing landscape analysis, and strategic vulnerability mapping using real web data.
4
5	## How It Works
6
7	```
8	INTAKE → RESEARCH (3 sequential waves) → SYNTHESIS → BATTLE CARDS
9	```
10
11	The process is focused: understand the product, research competitors deeply across 3 dimensions, synthesize findings, and produce actionable output. Typical runtime: 15-25 minutes in Claude Code (parallel agents), 30-45 minutes in Claude.ai (sequential).
12
13	### Language
14
15	Default output language is English. If the user writes in another language or explicitly requests one, use that language for all outputs instead.
16
17	---
18
19	## Phase 0: Resume Check
20
21	Before anything else, check if a `PROGRESS.md` created by this skill exists in the working directory or a project subdirectory (the skill name field says `startup-competitors`). If it does, read it and resume from the last incomplete phase. Tell the user: "I found progress from a previous session. You completed [phases]. Picking up from [next phase]."
22
23	If no progress file exists — or the one found belongs to a different skill — start from Phase 1.
24
25	---
26
27	## Phase 1: Intake
28
29	Short and focused — 1-2 rounds of questions, not an extended interview. The goal is just enough context to run targeted research.
30
31	### Check for Prior startup-design Work
32
33	Before asking questions, check if a `startup-design` session has already been completed for this project. Look for these files in the working directory or subdirectories:
34
35	- `01-discovery/competitor-landscape.md` — competitor profiles and analysis
36	- `01-discovery/market-analysis.md` — market size, trends, regulatory
37	- `01-discovery/target-audience.md` — customer personas, pain points
38	- `00-intake/brief.md` — product description and context
39
40	If these files exist, read them and use the data as a head start:
41	- Extract the product description, target market, and known competitors from the brief
42	- Use the competitor list from `competitor-landscape.md` as the starting point for deeper analysis (startup-design profiles 5-8 competitors at surface level — this skill goes much deeper on each)
43	- Pull market size and trends from `market-analysis.md` to contextualize the competitive landscape
44	- Use customer pain points from `target-audience.md` to focus the sentiment mining on what matters most
45
46	Tell the user: "I found data from a previous startup-design session. I'll use it as a starting point and go deeper on the competitive analysis."
47
48	Skip the intake interview entirely if the startup-design files provide enough context. Go straight to research.
49
50	### What to Ask (if no prior data exists)
51
52	Round 1 — The basics:
53	- What's your product/idea? (one sentence is fine)
54	- What problem does it solve and for whom?
55	- What market/category are you in?
56	- Do you know any competitors already? (names, URLs)
57
58	Round 2 — Sharpening (only if needed):
59	- What geography/market are you targeting?
60	- What's your pricing model or range?
61	- What do you consider your key differentiator?
62
63	Don't over-interview. If the user gives a clear description upfront, skip straight to research. The competitive analysis itself will surface what matters.
64
65	### Output
66
67	Save to `{project-name}/intake.md` — a brief summary of the product, market, and known competitors. If built on startup-design data, note the source files used. The project name should be derived from the product/market (kebab-case, e.g., `ai-email-assistant`).
68
69	Create `{project-name}/PROGRESS.md` with: project name, skill name (`startup-competitors`), start date, language, research mode (Live / Knowledge-Based), and a phase checklist. Update it after each phase completes. If PROGRESS.md already exists from a previous session, resume from the last incomplete phase.
70
71	---
72
73	## Phase 1.5: Research Depth Assessment
74
75	After intake, assess market complexity and present the Research Depth recommendation to the user.
76
77	> Reference: Read `references/research-scaling.md` for the complexity scoring matrix, tier definitions, wave configurations, and the user communication template.
78
79	### Process
80
81	1. Score three fa

People who liked this also viewed

6 picks

Type

startup-competitors

337installs85forks

View on GitHub

How to install startup-competitors?

ferdinandobons/startup-skill/startup-competitors

$npx -y skills add ferdinandobons/startup-skill --skill startup-competitors

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Startup Competitors
2
3	Deep competitive intelligence that goes beyond surface-level profiles. Produces actionable battle cards, pricing landscape analysis, and strategic vulnerability mapping using real web data.
4
5	## How It Works
6
7	```
8	INTAKE → RESEARCH (3 sequential waves) → SYNTHESIS → BATTLE CARDS
9	```
10
11	The process is focused: understand the product, research competitors deeply across 3 dimensions, synthesize findings, and produce actionable output. Typical runtime: 15-25 minutes in Claude Code (parallel agents), 30-45 minutes in Claude.ai (sequential).
12
13	### Language
14
15	Default output language is English. If the user writes in another language or explicitly requests one, use that language for all outputs instead.
16
17	---
18
19	## Phase 0: Resume Check
20
21	Before anything else, check if a `PROGRESS.md` created by this skill exists in the working directory or a project subdirectory (the skill name field says `startup-competitors`). If it does, read it and resume from the last incomplete phase. Tell the user: "I found progress from a previous session. You completed [phases]. Picking up from [next phase]."
22
23	If no progress file exists — or the one found belongs to a different skill — start from Phase 1.
24
25	---
26
27	## Phase 1: Intake
28
29	Short and focused — 1-2 rounds of questions, not an extended interview. The goal is just enough context to run targeted research.
30
31	### Check for Prior startup-design Work
32
33	Before asking questions, check if a `startup-design` session has already been completed for this project. Look for these files in the working directory or subdirectories:
34
35	- `01-discovery/competitor-landscape.md` — competitor profiles and analysis
36	- `01-discovery/market-analysis.md` — market size, trends, regulatory
37	- `01-discovery/target-audience.md` — customer personas, pain points
38	- `00-intake/brief.md` — product description and context
39
40	If these files exist, read them and use the data as a head start:
41	- Extract the product description, target market, and known competitors from the brief
42	- Use the competitor list from `competitor-landscape.md` as the starting point for deeper analysis (startup-design profiles 5-8 competitors at surface level — this skill goes much deeper on each)
43	- Pull market size and trends from `market-analysis.md` to contextualize the competitive landscape
44	- Use customer pain points from `target-audience.md` to focus the sentiment mining on what matters most
45
46	Tell the user: "I found data from a previous startup-design session. I'll use it as a starting point and go deeper on the competitive analysis."
47
48	Skip the intake interview entirely if the startup-design files provide enough context. Go straight to research.
49
50	### What to Ask (if no prior data exists)
51
52	Round 1 — The basics:
53	- What's your product/idea? (one sentence is fine)
54	- What problem does it solve and for whom?
55	- What market/category are you in?
56	- Do you know any competitors already? (names, URLs)
57
58	Round 2 — Sharpening (only if needed):
59	- What geography/market are you targeting?
60	- What's your pricing model or range?
61	- What do you consider your key differentiator?
62
63	Don't over-interview. If the user gives a clear description upfront, skip straight to research. The competitive analysis itself will surface what matters.
64
65	### Output
66
67	Save to `{project-name}/intake.md` — a brief summary of the product, market, and known competitors. If built on startup-design data, note the source files used. The project name should be derived from the product/market (kebab-case, e.g., `ai-email-assistant`).
68
69	Create `{project-name}/PROGRESS.md` with: project name, skill name (`startup-competitors`), start date, language, research mode (Live / Knowledge-Based), and a phase checklist. Update it after each phase completes. If PROGRESS.md already exists from a previous session, resume from the last incomplete phase.
70
71	---
72
73	## Phase 1.5: Research Depth Assessment
74
75	After intake, assess market complexity and present the Research Depth recommendation to the user.
76
77	> Reference: Read `references/research-scaling.md` for the complexity scoring matrix, tier definitions, wave configurations, and the user communication template.
78
79	### Process
80
81	1. Score three fa

People who liked this also viewed

6 picks

Type