curie

Translate business ideas into testable hypotheses and rigorous experiments.

4|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/satsilem/claude-skills-pantheon --skill curie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: curie
Source: https://github.com/satsilem/claude-skills-pantheon/tree/main/skills/curie
Command: npx skills add https://github.com/satsilem/claude-skills-pantheon --skill curie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn assumptions into testable hypotheses and rigorous experiments to minimize risk and maximize learning before committing significant resources.

Core Features & Use Cases

  • Design and validate experiments for product decisions, feature changes, and strategic bets.
  • Plan A/B tests, proof-of-concept scopes, and market or pricing validation with clear success criteria.
  • Provide an end-to-end workflow from hypothesis to pre-committed decision, including threat assessment and guardrails.

Quick Start

Design a complete Curie-style experiment plan to test the proposed feature.

Frequently Asked Questions about curie

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn business assumptions into testable hypotheses for product validation?

To turn assumptions into testable hypotheses, define the change, expected effect, and mechanism. This approach structures business ideas into formal hypotheses with clear falsifiability and cost-value analysis for product validation.

What is the best way to design an A/B test with pre-committed decisions and guardrails?

Designing an A/B test requires establishing pre-committed decisions and threat assessments before rollout. This creates an end-to-end experiment workflow that validates feature changes while protecting against threats to validity.

How do I plan a market validation experiment with clear success criteria?

Plan market validation by defining a formal hypothesis, establishing falsifiability, and outlining pre-committed decisions. This workflow translates business bets into rigorous experiments with explicit success criteria and cost-value analysis.

Can I use a structured hypothesis workflow for feature flag rollouts and proof-of-concept scopes?

Yes, a structured hypothesis workflow supports feature flag rollouts and proof-of-concept scopes. It applies formal requirements like change, effect, and mechanism to ensure resource commitments are backed by rigorous experimental evidence.

When do I need to include a threats to validity assessment in my experiment design?

You need a threats to validity assessment when committing significant resources to untested ideas. Evaluating threats to validity is a core component of rigorous experiment design, ensuring your A/B tests and market validations yield reliable evidence.