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.
npx skills add product-on-purpose/pm-skills --skill measure-experiment-results --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # 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
- When to Use
- When NOT to Use
- Instructions
- Output Format
- Quality Checklist
- Examples
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 it?
Run `npx skills add product-on-purpose/pm-skills --skill measure-experiment-results --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From product-on-purpose/pm-skills, a repository with 518 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.