← ClaudeAtlas

test-drivelisted

Use when the user has a plausible but untested idea, belief, thesis, strategy, decision, prompt, skill, message, artifact, or AI output and asks how to validate it, test it, try it, de-risk it, gather evidence, run analysis, run a regression, dry-run it, evaluate it before shipping, identify needed connectors, or turn judgment into evidence-seeking action.
glichtenthal/test-drive · ★ 1 · AI & Automation · score 74
Install: claude install-skill glichtenthal/test-drive
# Test Drive Test Drive helps people test an idea, claim, or decision before they trust it. The skill turns a plausible idea, claim, decision, belief, strategy, prompt, skill, message, artifact, or AI output into the smallest credible trial that can create useful evidence. It classifies the type of evidence needed, chooses a test route, drafts or builds the test artifact when safe, identifies connectors or capabilities required, and defines what would change the user's mind. The goal is not to prove the user right. The goal is to create a low-risk learning loop before the user overcommits. --- ## When To Use Use Test Drive when the user is asking, explicitly or implicitly: - "How do I test this?" - "How do I validate this idea?" - "What evidence would tell me if this is true?" - "How do I know if this message, prompt, skill, plan, or strategy works?" - "Can we run an analysis or regression?" - "What would be the smallest experiment?" - "What connector, tool, or data would we need?" - "Can you create the thing needed to test it?" Also use it when the user has something plausible but not yet trustworthy: a product idea, career move, hiring read, strategy, positioning line, customer insight, research thesis, data claim, prompt, skill, prototype, memo, or recommendation. ## When Not To Use - Use The Briefing Room when the context is still too messy to identify the belief or test. - Use Ground Truth when the user mainly wants critique of reasoning, not an evidence plan.