What does this skill do, and when should you use it?
This skill turns Claude into a business advisor channeling The Minimalist Entrepreneur by Sahil Lavingia. It targets founders ready to build their first product or struggling with scope creep, using a three-stage path (manual delivery, then processizing, then productization) plus four pre-build questions to compress scope ruthlessly. It pushes you to do one thing, skip polish, charge from day one, and ships with a launch essentials checklist. The output focuses on: the single thing your MVP does, the simplest implementation, what you can ship this weekend, pricing, and feedback channels.
It reads the user's product idea or scope dilemma and generates guidance from its embedded methodology: filtering scope through four questions (shippable in a weekend? makes customers' life a little better? will someone pay? can you get feedback fast?); breaking delivery into manual / processized / productized stages; recommending existing tools (Carrd, Gumroad, Stripe, Airtable, Notion, Zapier) instead of writing code; and walking through a launch checklist (naming, domain, simple website, social accounts, payments, support email). It is a pure instructional prompt — it executes no commands and calls no tools — and produces a structured MVP definition covering the one thing, simplest implementation, weekend ship target, initial price, and feedback plan.
- A first-time founder with a product idea whose feature list keeps growing and needs a framework to cut it down to a weekend-shippable MVP
- An indie hacker wanting to test willingness to pay and needing guidance on a minimal Carrd + Stripe page that can charge $1 within a day or two
- A service-based founder doing everything by hand for each customer who wants to know when and how to document the process so someone else could take over
- A technical founder inclined to jump straight to code who needs a nudge to validate with spreadsheets and forms first
- Someone about to launch who wants a concrete checklist: naming, domain, simple website, payment setup, customer email
How do you install this skill?
- This is a static source review; the skill was not executed and confidence is low.
- The skill file declares no license; verify the repository's overall license terms before use.
- Content is English-only with no Chinese support; recommended tools (Stripe, Carrd, Gumroad) may have registration or payment reachability issues for mainland-China users.
- This is methodology guidance rather than a validated production tool; actual results depend on model execution quality.
The skill is part of a 10-skill collection in the slavingia/skills repo. In Claude Code run: /plugin marketplace add slavingia/skills then /plugin install minimalist-entrepreneur — Claude Code fetches the repo and registers all 10 skills automatically. Alternative from a local clone: git clone https://github.com/slavingia/skills.git ~/.claude/plugins/skills, then /plugin marketplace add ~/.claude/plugins/skills and install. License: unknown.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/slavingia/skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/mvp" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- I want to build an invoicing tool for freelancers but my feature list is 20 items long — cut it to an MVP I can ship this weekend.
In Claude Code, invoke /mvp, or simply describe your situation, e.g. "I want to build an invoicing tool for freelancers but my feature list is 20 items long — cut it to an MVP I can ship this weekend." The skill auto-matches requests about building a first product or struggling with scope, per its frontmatter description. Output is advisory text; no extra permissions needed.
What are this skill's strengths and limitations?
- A complete, coherent methodology (three stages, four questions, launch checklist) rather than generic advice
- Includes real Gumroad anecdotes (manual PayPal payouts, never shipping a v2) that add credibility
- Pure Markdown prompt with zero dependencies and zero permissions — portable to any Agent Skills-compatible client
- Strongly anti-overengineering (don't build for scale, spreadsheet over code) — especially valuable for technical founders
- Advisory only — it will not actually build your website, write code, or configure payments
- Opinionated toward The Minimalist Entrepreneur school (e.g., always charge from day one), which doesn't fit every product type
- Repository license is unknown, creating uncertainty around commercial reuse
- No tests or evaluations back the skill's quality; effectiveness depends on the underlying model
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| MVP Minimalist Advisor this page | 52 · Use with care | ★ 11k | 6mo ago | — |
| Validate Idea | 52 · Use with care | ★ 11k | 6mo ago | — |
| First Customers | 55 · Use with care | ★ 11k | 6mo ago | — |
| vibe-check Product Planning Coach | 62 · Recommended | ★ 619 | 3mo ago | MIT |
| Processize — Manual-First Delivery | 53 · Use with care | ★ 11k | 6mo ago | — |
How did FollowSkills review this skill?
Pure prompt-based advisory skill: no scripts, no permission requests, no data exfiltration or external side effects; least privilege is inherently satisfied and content is attributed to a public book. Deducted for: no explicit confirmation/rollback disclosure (even if unnecessary), unknown license metadata, and no explicit data-flow declaration.
As a prompt-only guidance skill, instructions are self-consistent with no runtime dependencies; happy-path behavior is predictable. Deducted for: no tests or edge-case handling, undefined behavior on abnormal inputs (e.g., existing products, non-software businesses), and unverified failure feedback; static review caps this at 10.
Trigger scenarios are clear (ready to build first product, struggling with scope) and the YAML description supports accurate semantic invocation; output structure is specified. Deducted for: no declared non-fit boundaries (hardware, internal tools), no Chinese-language support, and recommended tools (Stripe, Carrd, Gumroad) may be hard to reach for mainland-China users without disclosure.
Well-structured with progressive disclosure across stages, a checklist, and output spec; README covers installation and the skill suite. Deducted for: no per-skill license, versioning, changelog, or maintenance responsibility; unknown license metadata; few examples and no known-limitations disclosure.
Statically, the three-stage framework, four build questions, and output checklist should yield directly usable MVP planning advice; marginal value lies in the structured methodology. Deducted for: no execution evidence, output quality depends entirely on model behavior, and completeness is unverified; static cap is 7, scored 6.
Key factual claims (Gumroad's manual PayPal payouts, Stripe pricing) are traceable to public sources and the book attribution is genuine. Deducted for: no tests, no third-party execution evidence, no multi-source corroboration, and no clear separation of fact vs. inference; static cap well below 5, scored 3.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →