agentsclimarketplace
Sign in

Market validation

Skill Dragoon0x/product-skills/skills/strategy/market-validation

Test assumptions before committing resources. Generates lean validation plans, fake door tests, and interview scripts. Use before building anything expensive or when there's no evidence anyone wants what's being built.From its SKILL.md

Install
npx -y skills add Dragoon0x/product-skills --skill market-validation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, 423 tokens by cl100k_base, as published. Nobody here has run it

Market Validation

Test assumptions before committing resources.

How to use

  • /market-validation Apply validation-first constraints to this conversation.
  • /market-validation <idea> Generate a validation plan for the described idea.

Constraints

Assumption Mapping

  • MUST list the top 3 assumptions that would kill the product if wrong
  • MUST rank assumptions by risk: which one, if false, makes everything else irrelevant
  • MUST design a test for the highest-risk assumption first
  • NEVER build until the highest-risk assumption has some evidence behind it

Validation Methods (ordered by speed and cost)

  1. Talk to 5 people who have the problem. Just listen.
  2. Search for existing solutions and read their reviews. What's missing?
  3. Build a landing page that describes the product. Measure interest.
  4. Create a fake door: a button that says "coming soon" to measure demand
  5. Build the smallest possible thing that tests the core assumption

Interview Framework

  • Ask about past behavior, not future intent ("Tell me about the last time..." not "Would you use...")
  • NEVER ask "Would you pay for this?" Ask "How do you solve this today and what does it cost you?"
  • MUST listen for emotion. Mild interest is not validation. Frustration is.
  • SHOULD identify the moment they switched from an old solution to their current one. What triggered it?

Signal vs. Noise

  • "That's cool" is not validation. "When can I use this?" is closer.
  • Email signups are weak signals. Credit card on waitlist is strong.
  • 100 lukewarm responses < 10 people who desperately need this
  • MUST define what "validated" looks like before running the test

Anti-Patterns

  • Survey-based validation (people lie in surveys, even to themselves)
  • Asking friends and family (they'll say what you want to hear)
  • Treating a pitch deck as validation
  • Building first, validating later
  • Validating the easy assumption instead of the risky one

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.