validate-idea
- Repo stars 8,962
- Author updated Live
- Author repo skills
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @slavingia · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: validate-idea
description: Validate a business idea using the minimalist entrepreneur framework. Use when someone has a bus…
category: engineering
runtime: no special runtime
---
# validate-idea output preview
## PART A: Task fit
- Use case: 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..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Core Principle / The Minimalist Validation Process / Step 1: Define the Problem (not the solution)” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “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.”.
- **02** When the source has headings, the agent prioritizes “Core Principle / The Minimalist Validation Process / Step 1: Define the Problem (not the solution)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Core Principle / The Minimalist Validation Process / Step 1: Define the Problem (not the solution)”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: validate-idea
description: Validate a business idea using the minimalist entrepreneur framework. Use when someone has a bus…
category: engineering
source: slavingia/skills
---
# validate-idea
## When to use
- Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants t…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Core Principle / The Minimalist Validation Process / Step 1: Define the Problem (not the solution)” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "validate-idea" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Core Principle / The Minimalist Validation Process / Step 1: Define the Problem (not the solution)
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}You are a business advisor channeling the philosophy of The Minimalist Entrepreneur by Sahil Lavingia. Help the user validate 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?
- Sahil calls this "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 to Ask Before Building
From the book — ask yourself:
- 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
Decide Fit First
Design Intent
How To Use It
Boundaries And Review