validate-idea
Skill1 starsChanged 7 months agoMITView on GitHub
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. Also use when the user mentions "idea validation," "business idea," "market fit," "customer interviews," "problem worth solving," or "should I build this." For finding a community first, see find-community. For building the MVP, see mvp.
23 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- insight68/Skillsedited, first seen Nov 8, 2026
- lalulali/vespyrtheir own version, first seen Nov 6, 2026
- sanskarprajapati/validator-skilltheir own version, first seen Nov 1, 2026
- alexjmiller5/agent-config-publictheir own version, first seen Oct 15, 2026
- menkesu/awesome-pm-skillstheir own version, first seen Oct 13, 2026
- sendaifun/solana-newtheir own version, first seen Oct 9, 2026
Used with
Projects with it also use launch.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkilllaunch
Launch and automate VS Code Insiders with the Copilot Chat extension using @playwright/cli via Chrome DevTools Protocol. Use when you need to interact with the VS Code UI, automate the chat panel, test the extension UI, or take screenshots. Triggers include 'automate VS Code', 'interact with chat', 'test the UI', 'take a screenshot', 'launch with debugging'.
Also in 3 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 6
- slavingia/skills★ 11k92% same
- keeea/minimalist-entrepreneur-skills★ 1958% same
- ariadoss/superskills★ 1292% same
- CarbeneAI/Forge★ 992% same
- insight68/Skills★ 592% same
- consubstantial-polistes407/skills★ 092% same
Wrote their own version · 17
- emotixco/claude-skills-founder★ 796same name
- me2resh/apexyard★ 542same name
- menkesu/awesome-pm-skills★ 441same name
- sendaifun/solana-new★ 178same name
- konglong87/superPM★ 84same name
- lalulali/vespyr★ 11same name
- Latifox/find-me-saas★ 10same name
- sanskarprajapati/validator-skill★ 7same name
- impactbrussels/FounderOS★ 2same name
- cacardinal/laila★ 1same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- company-valuesSkill
- find-communitySkill
- first-customersSkill
- grow-sustainablySkill
- marketing-planSkill
- minimalist-reviewSkill
- mvpSkill
- pricingSkill
- processizeSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Before building anything, can you solve this problem for people by hand?
- Distinctive: line 35
Do it yourself first. Hire yourself.
- Distinctive: line 36
If you can solve it manually for a few people, you can eventually automate it
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Guide the user through validating their business idea before they write a single line of code or spend a dollar.
Core Principle
Validation happens through selling, not building. Most founders spend months building a product nobody wants. Instead, validate by selling a manual version of your solution first.
The Minimalist Validation Process
Step 1: Define the Problem (not the solution)
Ask the user:
- Who specifically has this problem? (Be precise — not "businesses" but "freelance graphic designers who struggle with invoicing")
- How are they solving it today? (The current workaround is your real competition)
- How painful is this problem? (Mild annoyance vs. hair-on-fire)
- Would they pay to make this problem go away?
Step 2: Can You Solve It Manually First?
Before building anything, can you solve this problem for people by hand?
- This is called "processizing" — creating a manual valuable process
- Do it yourself first. Hire yourself. Write down every step on a piece of paper
- If you can solve it manually for a few people, you can eventually automate it
- Example: Gumroad started as Sahil manually collecting PayPal info and paying creators one by one
Step 3: Will People Pay?
The ultimate validation is a transaction. Ask:
- Can you charge for this manual service right now?
- Have you talked to at least 10 potential customers?
- Have at least 3 of them said they'd pay (or actually paid)?
- What price point feels natural?
Step 4: Four Questions Before Building
- Can I ship it in the span of a weekend? First iteration should be prototyped in 2-3 days.
- Is it making my customers' life a little better? That's a minimum viable product.
- Is a customer willing to pay me for it? Profitable from day one.
- Can I get feedback quickly? The faster the feedback loop, the faster you build something worth paying for.
Red Flags (Do Not Build If...)
- Nobody is currently trying to solve this problem (no existing workarounds)
- You can't name 10 specific people who have this problem
- The only validation is "my friends think it's a cool idea"
- You need to educate people that they have this problem
- You're building for a community you don't belong to
Green Flags (Worth Pursuing If...)
- People are already paying for inferior solutions
- You've manually solved this for a few people and they loved it
- The community is actively complaining about this problem
- You can describe the customer and their pain point in one sentence
- You're scratching your own itch
Output
Give the user a clear verdict:
- Validated: Strong signals, proceed to MVP
- Needs more validation: Specific next steps to gather evidence
- Pivot: The idea needs fundamental changes — suggest directions
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

