AgentStack
SKILL verified MIT Self-run

Experiment Designer

skill-hardiktiwari-pm-operating-os-experiment-designer · by hardiktiwari

Help PMs design rigorous experiments (A/B tests, feature rollouts). Use before any A/B test, feature experiment, pricing test, or phased rollout.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-hardiktiwari-pm-operating-os-experiment-designer

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README — it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-hardiktiwari-pm-operating-os-experiment-designer)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Experiment Designer? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Experiment Designer

Help PMs design rigorous experiments with clear hypotheses, variants, metrics, and decision criteria. Ensures experiments are statistically sound and actionable.

When to Use

  • Before any A/B test
  • Feature experiment design
  • Pricing or packaging test
  • Phased rollout planning
  • When asked "how do we test this?"
  • Before setting up an experiment in an experimentation platform

Process / Template

1. Capture the Hypothesis

Use format: "We believe [action] will [outcome] for [segment] because [rationale]"

  • Action — what you're changing (feature, copy, flow)
  • Outcome — expected metric movement
  • Segment — who you're testing with
  • Rationale — why you believe this (research, prior data)

2. Define Control vs. Treatment

  • Control — baseline experience (no change)
  • Treatment — the change being tested
  • Be explicit about what differs between variants

3. Define Success Metrics

  • Primary metric — main success signal (one metric)
  • Secondary metrics — supporting signals
  • Guardrail metrics — must not regress (e.g., revenue, retention)

4. Determine Experiment Type

  • A/B test — two variants, single change
  • Multivariate — multiple factors
  • Phased rollout — gradual % rollout
  • Holdout — long-term impact test

5. Calculate Sample Size and Duration

  • Power — typically 80%
  • MDE (Minimum Detectable Effect) — smallest effect you care about
  • Traffic — daily eligible users
  • Duration — run until sufficient sample size

6. Define Decision Criteria

| Result | Action | |--------|--------| | Primary metric improves, guardrails hold | Ship | | Primary metric flat, secondary improves | Iterate (refine and re-test) | | Primary metric declines | Kill | | Inconclusive (low power) | Extend or increase traffic |

7. Document Risks

  • What could invalidate results? (seasonality, external events)
  • Confounding factors?
  • Technical implementation risks?

Output

An Experiment Design Doc with:

| Section | Content | |---------|---------| | Hypothesis | Full hypothesis statement | | Variants | Control and treatment definitions | | Primary Metric | Main success metric | | Secondary Metrics | Supporting metrics | | Guardrail Metrics | Metrics that must not regress | | Sample Size | Required sample per variant | | Duration | Estimated run length | | Decision Criteria | Ship / iterate / kill thresholds | | Risks | What could invalidate results |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.