agentleFS
letscooktech-studioletscooktech-studio/ai-engineering-arsenal/skills/startup-validator/SKILL.md

startup-validator

Skill7 starsChanged 6 days agoMITView on GitHub

Validate a startup, product, or feature thesis with falsifiable customer, market, and economics evidence. Use for new venture ideas, pivots, ICP selection, pricing hypotheses, and go/no-go decisions.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Write a one-sentence falsifiable thesis: customer, painful job, measurable outcome, and willingness-to-pay condition.

    line 18
  2. Distinctive:

    Do not treat TAM slides or survey intent as demand proof.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 3 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Startup Validator

Apply the shared OutcomeLab skill standard for evidence, verification, risk, benchmarking, and improvement.

Replace narrative confidence with a sequence of cheap, falsifiable tests.

Intake

Capture the proposed customer, painful job, current workaround, trigger event, solution, distribution route, constraints, and available evidence. Label statements as facts, assumptions, or guesses.

Workflow

  1. Write a one-sentence falsifiable thesis: customer, painful job, measurable outcome, and willingness-to-pay condition.
  2. Segment the market by urgency and access, then choose a beachhead ICP with a reachable interview list.
  3. Map alternatives including manual work, doing nothing, and incumbent products.
  4. Design evidence in ascending cost: desk research, problem interviews, concierge test, landing-page/offer test, and paid pilot.
  5. Define a pass/fail threshold before each test. Update confidence only from observed behavior, not compliments.

Output contract

Provide a thesis card, assumption ledger, competitor/alternative map, ranked experiments, interview guide, pricing test, and a go/pivot/stop recommendation. For every recommendation include the next observable signal and owner.

Quality gates

  • Do not treat TAM slides or survey intent as demand proof.
  • Require a clear status for desirability, viability, feasibility, and distribution.
  • State sample bias, evidence age, and confidence intervals where relevant.
  • Make the smallest next experiment capable of changing the decision.

Improvement loop

Log prediction versus result after every test; retire disproven assumptions and rerank the next uncertainty by decision impact.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.