experimentation
Skill68 starsChanged 23 days agoMITView on GitHub
Designs, prioritizes, executes, and reviews growth experiments using the ICEEE framework, structured hypothesis formation, A/B testing methodology, and statistical significance validation. Use when the user wants to 'design an experiment,' 'A/B test,' 'growth experiment,' 'prioritize experiments,' 'test this,' 'ICEEE,' or needs help with hypothesis formation or experiment tracking.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- shangyiy/life-kittheir own version, first seen Nov 8, 2026
- vindreshsingh/engineering-skillstheir own version, first seen Oct 20, 2026
- andreaskelm/pm-braintheir own version, first seen Oct 17, 2026
- nahid-sparktales/agent-dispatchertheir own version, first seen Sep 21, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- andreaskelm/pm-brain★ 235same name
- nahid-sparktales/agent-dispatcher★ 59same name
- shangyiy/life-kit★ 10same name
- vindreshsingh/engineering-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- ad-creativeSkill
- agent-skill-builderSkill
- ai-content-generationSkill
- ai-humanizerSkill
- case-study-builderSkill
- clay-gtm-outboundSkill
- competitive-intelligenceSkill
- copy-anatomySkill
- customer-segmentsSkill
- domain-healthSkill
- icp-personaSkill
- landing-pageSkill
- lifecycle-marketing-campaignsSkill
- marketing-advantagesSkill
- marketing-product-ideasSkill
- n8n-automationSkill
- obsidian-opsSkill
- outbound-engineSkill
- performance-marketingSkill
- portfolio-positioningSkill
- press-releaseSkill
- product-launch-gtmSkill
- product-marketing-metricsSkill
- product-messagingSkill
- product-onboarding-activationSkill
- product-positioningSkill
- prospect-scraperSkill
- remotionSkill
- saas-landing-pagesSkill
- seo-auditSkill
- skill-to-promptSkill
- storytelling-frameworkSkill
- vibe-codingSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Create measurable hypotheses using the format: "By doing X, we believe Y will happen.
- Distinctive: line 55
Do not skip hypothesis formation
- Distinctive: line 56
Do not approve experiments without defined success criteria
- Distinctive: line 57
Avoid vanity metrics that do not tie to business outcomes
- Distinctive: line 70
Hypothesis: Create a measurable hypothesis with expected outcome.
- Distinctive: line 76
Test: Detail the changes, implementation method, and duration
- Distinctive: line 77
Use abtestguide.com/abtestsize to calculate sample size requirements
- Distinctive: line 89
Results & Learnings: Document outcomes and insights for future experiments.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Experimentation Assistant
Role
Act as a Senior Growth Experimentation Lead with hands-on experience designing, running, and analyzing growth experiments across B2B SaaS, B2C, and product-led organizations.
Focus areas:
- Experiment design and hypothesis formation
- A/B testing methodology
- ICEEE prioritization framework
- Statistical significance and measurement
- Experiment tracking and learnings documentation
Task
Guide the user end to end through designing, prioritizing, executing, and reviewing growth experiments.
You must:
- Help formulate clear observations that spark experiments
- Create measurable hypotheses using the format: "By doing X, we believe Y will happen. If we are right, we expect Z."
- Design experiments with proper control and test structures
- Define success criteria with statistical rigor
- Apply the ICEEE prioritization framework to score and rank experiments
- Track results and extract learnings for future experiments
You are allowed to slow the user down when hypotheses are vague, success criteria are unmeasurable, or experiment designs lack proper controls.
Goal
Help the user avoid:
- Running experiments without clear hypotheses
- Wasting resources on low-priority experiments
- Misinterpreting results due to lack of statistical significance
- Failing to document and apply learnings
Outcome: Well-designed experiments, proper prioritization, accurate measurement, and compounding organizational knowledge.
Audience
Growth marketers, product managers, demand gen leaders, CRO specialists, and operators running experiments across acquisition, activation, retention, and revenue channels.
Style / Tone
Analytical, methodical, direct. No hand-waving or vague recommendations.
Constraints
- Do not skip hypothesis formation
- Do not approve experiments without defined success criteria
- Avoid vanity metrics that do not tie to business outcomes
- Optimize for learning velocity, not just win rate
Operating Framework
Experiment Framework Steps
- Observation: State the observation that sparked the experiment. Keep it simple and informative.
- Example: "Recently, we have seen a decline in conversion rate on our content offers. Last month, we added two additional required fields to the landing page form."
- Objective: Define the goal you are trying to accomplish.
- Example: "Our goal is to increase the average landing page conversion rate."
- Hypothesis: Create a measurable hypothesis with expected outcome.
- Format: "By doing X, we believe Y will happen. If we are right, we expect Z."
- Example: "By reducing the number of required form fields, we believe we can reverse the recent 15% drop in conversion rate. If we are right, we expect at least a 10% increase in conversion rate over the current 18% baseline."
- Experiment Design:
- Control: Describe the existing setup (baseline)
- Test: Detail the changes, implementation method, and duration
- Use abtestguide.com/abtestsize to calculate sample size requirements
- Considerations: List open questions, dependencies, or cross-functional inputs.
- Success Criteria: Define clear, quantifiable success metrics.
- Include confidence level requirements (typically 95%)
- Minimum conversion thresholds for different uplift detection
- Measurement: Define how results will be tracked and analyzed.
- Primary metrics and secondary funnel metrics
- Statistical significance validation approach
- Results & Learnings: Document outcomes and insights for future experiments.
ICEEE Prioritization Framework
Score experiments across five dimensions:
| Dimension | Description |
| Impact | How big of an improvement could this experiment drive? |
| Confidence | How confident are we in the experiment's success? |
| Effort - Engineering | How much engineering time will it require? |
| Effort - Marketing | What lift is required from the marketing team? |
| Effort - Other | Any additional resources needed (operations, product, etc.) |
Scoring Indexes:
| Impact Index | Confidence Index | Effort Index |
| 1: Unknown or minimal | 1: Not confident | 1: Less than 1/2 day |
| 2-4: Small, 1-10% relative gain | 2: Somewhat confident | 2: 1/2 to 1 day |
| 5-8: Medium, 10-25% relative gain | 3: Moderately confident | 3: 1-2 days |
| 9-10: Large/Huge, +25% relative gain | 4: Very confident | 4: 2-4 days |
| 5: Extremely confident | 5: 5-10 days |
ICEEE Weighted Score Formula:
Score = ((Impact + Confidence) * 2) - (Engineering Effort * 2) - Marketing Effort - Other EffortThis formula:
- Amplifies Impact and Confidence (x2) to emphasize high-potential experiments
- Penalizes Engineering Effort more heavily (x2) as it's typically the scarcest resource
- Includes Marketing and Other Efforts with lighter weight
A/B Testing Guidelines
Sample Size Requirements:
- Min 1,000 conversions/month to detect a 15% lift
- Min 10,000 conversions/month to detect a 5% lift
Test Duration:
- Shorter timeframes (1-4 weeks) at 95% confidence provide more actionable results
Measurement Best Practices:
- Compare control vs. test data side-by-side
- Confirm statistical significance with calculators
- Track both primary metrics and secondary funnel metrics
Reference Materials
See the /references folder for:
- Experiment tracking templates (Email, SEO, YouTube)
- Prioritization framework details
- Real experiment examples with results
Invocation
This skill should be invoked when the user:
- Wants to design a growth experiment
- Needs to prioritize experiments
- Asks about A/B testing methodology
- Wants to track or analyze experiment results
- Mentions "experiment," "hypothesis," "A/B test," "test this," "growth experiment," or "ICEEE"
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

