本文へ移動
cccskills
無料GitHub で公開

business-idea-validator

Pressure-test a business or side-hustle idea before you sink money and months into it — find the real demand, the risky assumptions, and the cheapest way to test them. Use when asked to validate my business idea, is this a good business idea, test my side hustle, or should I start this. Produces a read on the core assumptions the idea depends on, who the customer really is and whether the pain is real, the cheapest experiments to test demand before building, a rough viability check (market, competition, economics), and a go/refine/rethink call — honest, not a cheerleader.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Business-Idea Validator

Most business ideas fail not from bad execution but from building something nobody wanted — a problem you can catch before spending the money. This pressure-tests your idea: it surfaces the assumptions it secretly depends on, checks whether the customer and pain are real, and designs the cheapest experiments to find out — so you validate demand before you build, and get an honest call, not applause.

What This Skill Produces

  • The core assumptions — what has to be true for this to work (the customer exists, the pain is real, they'll pay, you can reach them, the economics work)
  • A customer & pain check — who the real buyer is and whether the problem is painful enough to pay to solve
  • Cheap validation experiments — the fastest, lowest-cost ways to test demand before building (conversations, a landing page, pre-sales, a manual/concierge version)
  • A viability read — rough market size, competition, and whether the unit economics could work
  • A go / refine / rethink call — honest, based on the evidence and the riskiest assumptions
  • The riskiest assumption to test first — where to point your first experiment

Required Inputs

Ask for these if not provided:

  • The idea — what it is, who it's for, and the problem it solves
  • The customer — who you think will pay, and why
  • Your evidence — any real signal so far (interest, sales, competitors)
  • Your stake — time/money you'd commit, and your risk tolerance
  • Your goal — a side hustle, a real business, or just testing the water

Framework: Test The Assumptions, Cheaply, First

  1. Surface the hidden assumptions. Every idea rests on beliefs — that a specific customer has a painful problem, will pay, and can be reached affordably. Name them.
  2. Interrogate the customer and pain. Is the buyer specific and real, and is the pain strong enough that they'll pay? "Nice to have" ideas die here.
  3. Design cheap experiments. Before building anything, test demand the fast way: talk to real potential buyers, put up a landing page, attempt pre-sales, or run a manual "concierge" version.
  4. Sanity-check viability. Rough market size, existing competition (its presence can validate demand), and whether the numbers could plausibly work.
  5. Test the riskiest assumption first. Point the first, cheapest experiment at the thing most likely to kill the idea — don't validate the easy parts.
  6. Give an honest call. Go, refine (pivot the weak assumption), or rethink — based on evidence, not enthusiasm. Be a critic, not a cheerleader.

Output Format

Idea validation: [idea] · for [customer] · stake [x]

Core assumptions: [customer exists · pain is real · they'll pay · reachable · economics work]. Customer & pain: [who really pays] · pain level: [must-have / nice-to-have]. Cheapest tests (before building): [customer conversations · landing page · pre-sale · concierge version]. Viability: market [rough] · competition [signal] · economics [plausible?]. Riskiest assumption to test first: [x]. Call: [go / refine / rethink] — because [evidence].

Quality Checks

  • Surfaces the idea's hidden assumptions
  • Interrogates whether the customer and pain are real/payable
  • Prescribes cheap experiments before building
  • Includes a rough viability read (market, competition, economics)
  • Identifies the riskiest assumption to test first
  • Gives an honest go/refine/rethink call, not cheerleading

Anti-Patterns

  • Cheerleading the idea instead of stress-testing it.
  • Jumping to build before testing demand.
  • Vague "big market" with no real customer/pain.
  • Testing the easy assumptions and ignoring the killer one.
  • Confusing personal excitement with market demand.

Example Trigger Phrases

  • "Is this a good business idea? Help me validate it."
  • "I want to start a side hustle doing X — is there demand?"
  • "How do I test my business idea cheaply before committing?"
  • "Pressure-test my startup idea honestly."
  • "Should I actually start this, or am I kidding myself?"

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

このスキルの問題を報告する