Measure Experiment Results
Documents the results of a completed experiment or A/B test with statistical analysis, learnings, and recommendations. Use after experiments conclude to communicate findings, inform decisions, and build organizational knowledge.
Install
/plugin marketplace add product-on-purpose/pm-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add product-on-purpose/pm-skills --skill measure-experiment-resultsgit clone --depth 1 https://github.com/product-on-purpose/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/skills/measure-experiment-results ~/.claude/skills/measure-experiment-resultsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Experiment Results An experiment results document captures what happened when you tested a hypothesis, including statistical outcomes, segment analysis, learnings, and clear recommendations. Good results documentation turns individual experiments into organizational knowledge that improves future decision-making. ## When to Use - After an A/B test or experiment reaches statistical significance - When an experiment is ended early (for any reason) - To communicate findings to stakeholders who weren't involved - During decision-making about whether to ship, iterate, or kill a feature - To build a repository of learnings that inform future experiments ## When NOT to Use - The experiment is not designed or run yet -> use `measure-experiment-design` - The results demand a direction decision -> use `iterate-pivot-decision`; this skill reports the evidence, that one decides - You want the transferable learning banked for the organization -> follow up with `iterate-lessons-log` - Your data is survey responses, not a controlled experiment -> use `measure-survey-analysis` ## Instructions When asked to document experiment results, follow these steps: 1. **Summarize the Experiment** Provide context: what was tested, when it ran, how much traffic it received. Link to the original experiment design document if one exists. 2. **Restate the Hypothesis** Remind readers what you believed would happen and why. This frames the results interpretation.
Details
- Skill name
measure-experiment-results- Repository
- product-on-purpose/pm-skills
- Path
skills/measure-experiment-results/SKILL.md- License
- Apache-2.0
- Repo updated
- 17 November 2026
FAQ
What does the Measure Experiment Results skill do?
Documents the results of a completed experiment or A/B test with statistical analysis, learnings, and recommendations. Use after experiments conclude to communicate findings, inform decisions, and build organizational knowledge.
How do I install the Measure Experiment Results skill?
Claude Code plugin: /plugin marketplace add product-on-purpose/pm-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Measure Experiment Results popular?
It lives in product-on-purpose/pm-skills, which has 819 GitHub stars and 104 forks, and is included in 2 curated skill lists.
Related skills
<phase or Classification Skill Name>
819product-on-purpose/pm-skills
<single-line 20-100 word description; include trigger keywords and do not use folded YAML>
Define Hypothesis
819product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.
Define Jtbd Canvas
819product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.
Tool Design Sprint Test and Score
819product-on-purpose/pm-skills
Day 5 (Friday) sprint-closing move of a Design Sprint that produces the bundled Friday artifact covering per-customer interview observations, best quotes, scorecard grid (sprint questions by customers), observed patterns, hot takes from each team member, and the Decider summary (build, iterate, pivot, or stop, plus highest-confidence learning, most important revision, and next artifact). Use Friday after Thursday's prototype passes trial run and during/after the 5 customer interviews. The sprint's payoff artifact.
Measure Experiment Design
819product-on-purpose/pm-skills
Designs an A/B test or experiment with variants, success metrics, sample size, and duration for an existing hypothesis. Use when planning an experiment to validate a product change or test an assumption you have already framed. To articulate the hypothesis itself first, use define-hypothesis.
Swift Testing Pro
483twostraws/Swift-Testing-Agent-Skill
Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.