helix

Designs experiments with hypotheses, controls, power analysis, and pre-specified analysis plans.

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/kridaydave/My_Skills --skill helix-kridaydave
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: helix
Source: https://github.com/kridaydave/My_Skills/tree/main/helix
Command: npx skills add https://github.com/kridaydave/My_Skills --skill helix-kridaydave

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing a study before data collection is where most research goes wrong: unfalsifiable hypotheses, uncontrolled confounds, underpowered samples, and analyses decided after seeing the data. This Skill structures the pre-data methodology phase so the experiment can actually answer the question before time and samples are spent. ## Core Features & Use Cases - Hypothesis & Falsification Framing: Sharpens vague questions into testable claims with an explicit null hypothesis and the result that would kill the hypothesis. - Design Selection & Controls: Chooses among RCT, A/B, factorial, within/between-subjects, observational, and ablation designs, identifying confounds and how to control or declare them. - Power & Pre-Specified Analysis: Estimates sample size for a target effect size and locks the test, primary outcome, and success criterion before data exists. - Use Case: A team wants to test whether a new UI improves engagement by giving it to power users. The Skill catches the selection confound, proposes randomization within user segments, sizes the sample for a meaningful effect, and pre-specifies the analysis. ## Quick Start Ask the Skill to design an experiment testing whether your new model beats the baseline on a chosen metric, including controls, sample size, and the analysis plan.

Frequently Asked Questions about helix

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

FAQPage Schema
How do I design an experiment to test a hypothesis?▼

Start by sharpening the question into a testable claim, state the hypothesis and null, and define what result would falsify it. Then choose a design (RCT, A/B, factorial, observational, or ablation), control confounds, estimate sample size, and pre-specify the analysis before collecting data.

How many samples do I need for an A/B test?▼

Sample size depends on the effect size you care about, desired power, and significance threshold. For a medium effect (d≈0.5) at 80% power you need roughly 64 per group; small samples like 15 per group only detect very large effects and risk false nulls.

What is a confound and how do I control it?▼

A confound is a variable correlated with your treatment that could explain the result instead of your hypothesis. Control it through randomization, matching, adding control arms, or measuring it directly; anything you cannot control must be declared as a limitation.

When should I use an ablation study instead of an A/B test?▼

Use ablation when you want to know which components of a system matter: remove one component at a time from the full system and measure the performance drop. Use A/B tests when comparing two complete variants against each other on a single outcome.

Why pre-specify the analysis before collecting data?▼

Deciding the test after seeing data enables p-hacking, even unintentionally, since enough post-hoc tests will always find something significant. Locking the primary outcome, test, threshold, and multiple-comparison corrections in advance keeps the result interpretable.

What can I do when an RCT is unethical or infeasible?▼

Use the best feasible alternative, such as a matched observational design with propensity matching or difference-in-differences to approximate a control group. The causal claim is weaker, so state exactly what the design can and cannot license.