startup-validation-test-designer

startup-validation-test-designer is a skill for Claude Code from forjd/startup-ideation-skills. It costs 36 tokens per session (1,626 once invoked), scanned A, original, MIT.

A guide for testing whether a startup idea solves a real problem before building the first version. It designs interviews, outreach, landing-page tests, manual services, and other small experiments.

In plain words
What is it for?
Use it to identify the riskiest assumption, choose a quick demand test, write neutral interview questions, and decide what behaviour counts as evidence.
Why use it?
It helps replace encouraging opinions with evidence from potential users and buyers. It also sets success, failure, and stopping rules before the test begins.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the startup-ideation-skills plugin — 6 skills shipped together

Good fit Use it to identify the riskiest assumption, choose a quick demand test, write neutral interview questions, and decide what behaviour counts as evidence.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/forjd/startup-ideation-skills/startup-validation-test-designer
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add forjd/startup-ideation-skills --skill startup-validation-test-designer
Clone the repo
git clone --depth 1 https://github.com/forjd/startup-ideation-skills

Made for: Claude Code.

Or install startup-ideation-skills, the plugin that ships this one along with the rest of its 6 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for startup-validation-test-designer

README.md
[![agentmods](https://agentmods.dev/badge/skills/forjd/startup-ideation-skills/startup-validation-test-designer/github.svg)](https://agentmods.dev/skills/forjd/startup-ideation-skills/startup-validation-test-designer)
Your own site
<a href="https://agentmods.dev/skills/forjd/startup-ideation-skills/startup-validation-test-designer"><img src="https://agentmods.dev/badge/skills/forjd/startup-ideation-skills/startup-validation-test-designer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for startup-validation-test-designer

Your own site · 80×15
<a href="https://agentmods.dev/skills/forjd/startup-ideation-skills/startup-validation-test-designer"><img src="https://agentmods.dev/badge/skills/forjd/startup-ideation-skills/startup-validation-test-designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,626 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.01626
Opus 5 $0.00018 $0.00813
Sonnet 5 $0.00007 $0.00325
Haiku 4.5 $0.00004 $0.00163

Measured 10d ago against content hash d4632d6e9736, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

startup-validation-test-designer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/startup-validation-test-designer/SKILL.md · 239 lines

How it starts

The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Startup Validation Test Designer

When to use

Use after a startup problem has been captured and grilled, especially when the next question is “how do I test this before building?”

This skill designs the smallest credible validation test. It should produce evidence from real people, not compliments about an idea.

Core rule

Test the riskiest assumption first. Prefer interviews, targeted outreach, paid audits, manual services, landing pages, fake doors, demo videos, and concierge delivery before building full software.

Inputs to request if missing

Problem:
Target user:
Likely buyer:
Current workaround:
Riskiest assumption:
What the user can build or deliver manually:
Existing network or channels:
Founder advantage:
Recent enabling change:
Distribution route:

Workflow

  1. Identify the riskiest assumption.
  2. Choose the fastest credible test type.
  3. Define the exact behaviour that would count as evidence.
  4. Write non-leading interview questions if interviews are part of the test.
  5. Define the target list and outreach angle.
  6. Tie the test to why the problem is urgent or newly solvable now.
  7. Set success, failure, and kill criteria before the test runs.
  8. Keep the test timeboxed. Default to 48 hours to 2 weeks.
  9. End with a clear evidence gate for whether v1 scoping is justified after the test.

Test types

Choose one or combine a small number:

  • Customer interview: learn workflow, cost, workaround, urgency, budget, and objections.
  • Direct outreach: test whether a narrow ICP responds to the pain statement.
  • Landing page: test whether people understand and take a specific action.
  • Fake door: measure clicks or requests for a specific capability.
  • Demo video: test whether the promised workflow is compelling.
  • Paid audit: sell a manual diagnostic or review before SaaS exists.
  • Manual service: deliver the outcome by hand for a few users.
  • Concierge/Wizard-of-Oz prototype: give a product-like experience with manual fulfilment.
  • Prototype: build only when behaviour cannot be tested another way.

Read the full file on GitHub · 239 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 239 lines · 36 tokens per session scan A d4632d6e9736

Subscribe to this mod's changes

startup-validation-test-designer is a skill published in the GitHub repository forjd/startup-ideation-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 1,626 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories