← ClaudeAtlas

gtm-machinelisted

Validate startup ideas with evidence and test them with real outbound — the full loop from raw idea to booked calls. Use this skill whenever an idea-stage founder wants to validate a startup or product idea, assess AI-platform kill-risk, check if a market is worth entering, build an ICP or personas, source leads from Apollo, write cold outbound copy, run an email campaign, or measure whether anyone actually wants what they're building. Trigger on phrases like "validate my idea", "is this idea any good", "should I build", "find my ICP", "test demand", "cold outreach", "book calls with prospects", "GTM test" — and also when a founder describes an idea and asks what to do next, even without naming validation explicitly.
vkuchkanov/gtm-machine · ★ 3 · AI & Automation · score 66
Install: claude install-skill vkuchkanov/gtm-machine
# GTM Machine Turn a startup idea into evidence, and evidence into booked calls. Five stages, each with a hard gate. The north-star metric is **booked calls per idea tested** — not reports generated, not leads sourced, not emails sent. ## Honest status of this skill The process encoded here passed its own evals (11/11 on a golden set of ideas, live-validated Apollo ICPs, a verified end-to-end send-and-classify loop). What it has NOT yet done is book a call — the full outbound loop was proven mechanically, not commercially. Treat the reply-rate bars below as starting hypotheses, and tell the founder this when setting expectations. A validation tool that oversells itself commits the exact sin it exists to catch. ## The one rule that outranks everything **Never state anything about a prospect's business that you have not verified.** A cold email that says "your chat widget does X" to a hotel with no chat widget is dead on arrival — worse than generic, because being wrong proves you never looked. Every claim about a recipient needs a scan record with evidence and a timestamp, or it does not ship. This rule was learned the expensive way; enforce it programmatically (see `scripts/s4_write/lint.py`, the `CLAIM_FIELDS` gate), never by good intentions. ## The five stages Work through them in order. Each stage's full rubric lives in `references/` — read the relevant file when you reach that stage, not before. ### S1 — Validate → `references/s1-validate.md` Score the idea on dem