hypothesis-design

hypothesis-design is a skill for Claude Code, Codex from Adelie-Squad/solosquad. It costs 32 tokens per session (648 once invoked), scanned A, original, MIT.

A product-planning method for writing testable hypotheses and examining their assumptions. It uses formats such as “If–Then–Because” and classifies risks by value, usability, viability, and feasibility.

In plain words
What is it for?
It helps define target users, expected behavior, timing, reasons, risks, experiments, and a recommendation for which product idea to test.
Why use it?
It helps teams turn vague ideas into measurable predictions and test the riskiest assumptions first. It also requires comparing at least two possible approaches.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for gstack. Also seen: built for gstack.

Good fit It helps define target users, expected behavior, timing, reasons, risks, experiments, and a recommendation for which product idea to test.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/adelie-squad/solosquad/hypothesis-design
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 Adelie-Squad/solosquad --skill hypothesis-design
Clone the repo
git clone --depth 1 https://github.com/Adelie-Squad/solosquad

Made for: Claude Code, Codex.

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 hypothesis-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/adelie-squad/solosquad/hypothesis-design/github.svg)](https://agentmods.dev/skills/adelie-squad/solosquad/hypothesis-design)
Your own site
<a href="https://agentmods.dev/skills/adelie-squad/solosquad/hypothesis-design"><img src="https://agentmods.dev/badge/skills/adelie-squad/solosquad/hypothesis-design/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 hypothesis-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/adelie-squad/solosquad/hypothesis-design"><img src="https://agentmods.dev/badge/skills/adelie-squad/solosquad/hypothesis-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 648 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00032 $0.00648
Opus 5 $0.00016 $0.00324
Sonnet 5 $0.00006 $0.00130
Haiku 4.5 $0.00003 $0.00065

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

Security

Grade A, and why

hypothesis-design 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 8d 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/hypothesis-design/SKILL.md · 86 lines

What it actually says

Hypothesis Design Skill

XYZ Hypothesis

[X%] of [Y segment] will [Z behavior] within [T period], because [R rationale]

상세 schema 는 skills/problem-definition/assets/05-xyz-hypothesis.md 참조 (cross-reference).

If-Then-Because

If [intervention] is delivered to [segment]
Then [measurable result] within [period]
Because [causal mechanism]

XYZ 보다 가벼운 형식. early-stage exploration 시 사용.

V/U/V/F Assumption Classifier

각 가설의 핵심 가정을 4 카테고리로 분류 후 위험도 평가:

카테고리 질문 위험 시 검증 방법
Value 사용자가 이 변화로 가치를 얻는가? concierge MVP, fake door
Usability 사용자가 발견/사용 가능한가? usability test, prototype
Viability 비즈니스 / 운영 가능한가? financial model, capacity check
Feasibility 기술적으로 가능한가? technical spike, prototype

가장 risky assumption 부터 experiment 우선순위 결정.

≥ 2 approaches 룰

hypotheses:
  - id: h1
    xyz: "..."
    pros: [...]
    cons: [...]
    v_u_v_f_risk: { v: high, u: low, v2: low, f: low }
  - id: h2
    xyz: "..."
    pros: [...]
    cons: [...]
    v_u_v_f_risk: { v: low, u: high, v2: low, f: medium }
recommended: h1
recommendation_rationale: "h1 의 V 위험이 더 testable. h1 fail 시 h2 로 pivot."

HARD GATE: hypothesis → experiment-design 진입 조건

  • ≥2 hypotheses 비교
  • 각 hypothesis 의 V/U/V/F risk 평가
  • recommended + falsification 명시
  • confidence ≥ 60

Reference

  • RO-PNA XYZ format
  • David Bland "Testing Business Ideas" — V/U/V/F (V=Value, U=Usability, V=Viability, F=Feasibility)
  • gstack approaches ≥2 rule
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. 8d ago First seen · 86 lines · 32 tokens per session scan A c066c8d8aa3a

Subscribe to this mod's changes

hypothesis-design is a skill published in the GitHub repository Adelie-Squad/solosquad (19 stars, last pushed 18d ago), licensed MIT. It adds 32 tokens to every session and 648 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-30.

Related

Other skills, from other repositories

saas-api-security

SaaS uygulaması için API güvenlik katmanı kur. Rate limiting, plan bazlı erişim kontrolü, input validation, hata yönetimi, CORS ve health check. Bu skill'i kullanıcı API güvenliği, rate limiting, yetkilendirme, input doğrulama, hata yönetimi veya API koruması ile ilgili bir şey istediğinde kullan. "API'yi koru", "rate…

komunite/tezgah · 108 tokens

saas-launcher

Sıfırdan production-ready bir SaaS uygulaması kur. Ödeme, kimlik doğrulama, veritabanı, e-posta, landing page, SEO ve API güvenliği dahil tüm katmanları kapsar. Kullanıcı SaaS kurmak, web uygulaması başlatmak, AI aracı oluşturmak veya online ürün çıkarmak istediğinde bu skill'i kullan — "startup kur", "proje başlat"…

komunite/tezgah · 136 tokens

saas-payments

SaaS uygulaması için ödeme ve abonelik sistemi kur. Stripe veya Lemon Squeezy ile checkout, webhook, abonelik yönetimi, fiyatlandırma planları ve müşteri portalı yapılandır. Bu skill'i kullanıcı ödeme, abonelik, fiyatlandırma, Stripe, gelir, plan, subscription veya checkout ile ilgili bir şey istediğinde kullan. "Para…

komunite/tezgah · 103 tokens

saas-analytics

SaaS uygulaması için PostHog analytics ve ürün analizi kur. Event tracking, kullanıcı tanımlama, feature flag, session replay, funnel analizi ve gizlilik uyumlu yapılandırma. Bu skill'i kullanıcı analytics, PostHog, event tracking, kullanıcı davranışı, feature flag, A/B test, dönüşüm analizi veya metrik takibi ile…

komunite/tezgah · 119 tokens

saas-testing

SaaS uygulaması için test stratejisi kur. Vitest ile birim test, Playwright ile E2E test, API route testi, webhook mock, Stripe test modu ve CI entegrasyonu. Bu skill'i kullanıcı test, test yazma, E2E, birim test, Playwright, Vitest, coverage veya kalite güvencesi ile ilgili bir şey istediğinde kullan. "Test yaz"…

komunite/tezgah · 115 tokens

saas-deployment

SaaS uygulamasını production'a taşı. Vercel, Railway veya Fly.io ile deployment, domain yapılandırması, SSL, ortam değişkenleri, CI/CD, izleme ve operasyonel hazırlık. Bu skill'i kullanıcı deploy, yayınlama, production, hosting, domain, SSL, CI/CD, monitoring veya "siteyi canlıya al" ile ilgili bir şey istediğinde…

komunite/tezgah · 119 tokens