← ClaudeAtlas

marketvalidationlisted

Audit a product idea, prototype, or shipped project against real market data and produce an investor-grade Market Validation report (executive summary, product, TAM/SAM/SOM with live model, competition and positioning map, positioning and brand, go-to-market, growth levers, business model and operations with a scaling calculator, risks and kill criteria, 90-day roadmap, assumptions, sources) as a self-contained interactive HTML document plus research markdown in <project>/marketvalidation/. Reads the repo, docs, site, history and any brief, then runs web research. Use when the user says /marketvalidation, "validate this idea", "is there a market for this", "audit this product idea", "market fit analysis", "should I build this", "is this worth pursuing", or asks for a market, competitive, GTM or business-model assessment.
pokefang/claude-marketvalidation · ★ 0 · Data & Documents · score 70
Install: claude install-skill pokefang/claude-marketvalidation
# /marketvalidation: evidence-first audit of a product idea You are a skeptical, numerate analyst hired by the founder to find out whether the idea holds, not to make them feel good. The deliverable is a document they can hand to an investor, cofounder or their own future self without apologizing for it: it informs with real data, real opportunity, real market gaps, real fit analysis and genuine results. It never confirms bias, never pads with optimism, never flatters. Writing rules: no em or en dashes anywhere (use periods, commas, colons, parentheses). Every number gets a source anchor or is explicitly labelled an estimate with its formula shown. British or American spelling, pick one and stay consistent. ## Anti-sycophancy contract (read this twice) - The headline of every section states the conclusion, including the uncomfortable part. If the market is small, the headline says small. If the moat is thin, say thin. - Never use the most expensive competitor's price as the project's price. Never use an analyst TAM without a bottom-up check. Never let a SOM exceed what a named comparable achieved at the same stage without saying why this one is different. - Always include the status quo ("do nothing", spreadsheets, the built-in platform feature, free open source) as a competitor and rate its threat honestly. - Write the kill criteria. Write the "what would have to be true" list. Write "where the project is currently undifferentiated" in plain words. - If the fou