validate-idea

Name: validate-idea
Author: keeea

15stars1forks

How to install validate-idea?

keeea/minimalist-entrepreneur-skills/validate-idea

$npx -y skills add keeea/minimalist-entrepreneur-skills --skill validate-idea

Installs into the current project.

Summary

Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything. Based on The Minimalist Entrepreneur by Sahil Lavingia.

Files · 1

View on GitHub

SKILL.md

1	# Validate Idea
2
3	Help validate a business idea before writing any code or spending money.
4
5	## Core Principle
6
7	Validation happens through selling, not building. Most founders spend months building something nobody wants. Validate by selling a manual version first.
8
9	## The Minimalist Validation Process
10
11	### Step 1: Define the Problem (not the solution)
12
13	- Who specifically has this problem? (Be precise — "freelance graphic designers who struggle with invoicing", not "businesses")
14	- How are they solving it today? (Current workaround = real competition)
15	- How painful is it? (Mild annoyance vs. hair-on-fire)
16	- Would they pay to make it go away?
17
18	### Step 2: Can You Solve It Manually First?
19
20	- Create a manual valuable process ("processizing")
21	- Do it yourself first. Write down every step.
22	- If you can solve it manually for a few people, you can eventually automate it.
23	- Example: Gumroad started as Sahil manually collecting PayPal info and paying creators one by one.
24
25	### Step 3: Will People Pay?
26
27	- Can you charge for this manual service right now?
28	- Have you talked to at least 10 potential customers?
29	- Have at least 3 said they'd pay (or actually paid)?
30	- What price point feels natural?
31
32	### Step 4: Four Questions Before Building
33
34	1. Can I ship it in a weekend? First iteration should be prototyped in 2-3 days.
35	2. Is it making my customers' life better? That's a minimum viable product.
36	3. Is a customer willing to pay? Profitable from day one.
37	4. Can I get feedback quickly? Faster feedback = faster iteration.
38
39	## Red Flags (Do Not Build)
40
41	- Nobody currently trying to solve this problem
42	- Can't name 10 specific people who have it
43	- Only validation is "my friends think it's cool"
44	- Need to educate people that they have this problem
45	- Building for a community you don't belong to
46
47	## Green Flags (Worth Pursuing)
48
49	- People already paying for inferior solutions
50	- You've manually solved this for a few people and they loved it
51	- Community actively complaining about this problem
52	- Can describe customer and pain point in one sentence
53	- Scratching your own itch
54
55	## Output
56
57	Clear verdict:
58	- Validated: Strong signals, proceed to MVP
59	- Needs more validation: Specific next steps to gather evidence
60	- Pivot: Idea needs fundamental changes — suggest directions

People who liked this also viewed

6 picks

Type

validate-idea

15stars1forks

View on GitHub

How to install validate-idea?

keeea/minimalist-entrepreneur-skills/validate-idea

$npx -y skills add keeea/minimalist-entrepreneur-skills --skill validate-idea

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Validate Idea
2
3	Help validate a business idea before writing any code or spending money.
4
5	## Core Principle
6
7	Validation happens through selling, not building. Most founders spend months building something nobody wants. Validate by selling a manual version first.
8
9	## The Minimalist Validation Process
10
11	### Step 1: Define the Problem (not the solution)
12
13	- Who specifically has this problem? (Be precise — "freelance graphic designers who struggle with invoicing", not "businesses")
14	- How are they solving it today? (Current workaround = real competition)
15	- How painful is it? (Mild annoyance vs. hair-on-fire)
16	- Would they pay to make it go away?
17
18	### Step 2: Can You Solve It Manually First?
19
20	- Create a manual valuable process ("processizing")
21	- Do it yourself first. Write down every step.
22	- If you can solve it manually for a few people, you can eventually automate it.
23	- Example: Gumroad started as Sahil manually collecting PayPal info and paying creators one by one.
24
25	### Step 3: Will People Pay?
26
27	- Can you charge for this manual service right now?
28	- Have you talked to at least 10 potential customers?
29	- Have at least 3 said they'd pay (or actually paid)?
30	- What price point feels natural?
31
32	### Step 4: Four Questions Before Building
33
34	1. Can I ship it in a weekend? First iteration should be prototyped in 2-3 days.
35	2. Is it making my customers' life better? That's a minimum viable product.
36	3. Is a customer willing to pay? Profitable from day one.
37	4. Can I get feedback quickly? Faster feedback = faster iteration.
38
39	## Red Flags (Do Not Build)
40
41	- Nobody currently trying to solve this problem
42	- Can't name 10 specific people who have it
43	- Only validation is "my friends think it's cool"
44	- Need to educate people that they have this problem
45	- Building for a community you don't belong to
46
47	## Green Flags (Worth Pursuing)
48
49	- People already paying for inferior solutions
50	- You've manually solved this for a few people and they loved it
51	- Community actively complaining about this problem
52	- Can describe customer and pain point in one sentence
53	- Scratching your own itch
54
55	## Output
56
57	Clear verdict:
58	- Validated: Strong signals, proceed to MVP
59	- Needs more validation: Specific next steps to gather evidence
60	- Pivot: Idea needs fundamental changes — suggest directions

People who liked this also viewed

6 picks

Type