experiment-report

Generate a complete experiment report from A/B test results and design context.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/weisberg/agile_agentic_analytics --skill experiment-report-weisberg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experiment-report
Source: https://github.com/weisberg/agile_agentic_analytics/tree/main/plugins/ab-testing/skills/experiment-report
Command: npx skills add https://github.com/weisberg/agile_agentic_analytics --skill experiment-report-weisberg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a complete, stakeholder-ready experiment report from A/B test results, consolidating data, hypotheses, and outcomes into a clear narrative.

Core Features & Use Cases

  • Structured reporting: produces executive summaries, background, methodology, results, discussion, and recommendations.
  • Audience-aware: adapts depth and language for technical and executive readers.
  • Traceable inputs: includes hypothesis, metrics, sample sizes, guardrails, segment analyses, and appendices for reproducibility.

Quick Start

Describe the experiment name, results, and key metrics, then request a stakeholder-ready report.

Frequently Asked Questions about experiment-report

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

FAQPage Schema
How do I generate an A/B test report for stakeholders from raw experiment data?

To generate an A/B test report, input your experiment results, hypothesis, and key metrics. The tool produces a structured document with executive summaries, methodology, segment analyses, and formal recommendations tailored for both technical and executive readers.

How do I present A/B testing statistics and segment analyses to executive stakeholders?

Present A/B testing statistics to executives by adapting the report's depth and language to be audience-aware. It translates segment analyses and guardrails into a clear narrative with an executive summary and formal recommendation, bridging technical data and business impact.

What is the best way to structure an experiment report to include methodology and statistical results?

The best way to structure an experiment report is through dedicated sections for background, methodology, results, and discussion. This organizes statistical methods, sample sizes, and segment data into a traceable narrative that satisfies formal reporting requirements.

Can I use this reporting approach for both technical and executive audiences?

Yes, this reporting approach is audience-aware and adapts its depth and language for both technical and executive readers. It includes detailed appendices for reproducibility while providing high-level executive summaries and formal recommendations for decision-makers.

What do I need to prepare before generating a stakeholder-ready A/B test report?

Before generating an A/B test report, you need to describe the experiment name, results, and key metrics. You should also have your hypothesis, guardrails, and segment data ready to ensure the final report includes all necessary traceable inputs for stakeholders.