experiment-report

Draft IMRaD-style experiment reports from run data and validate with a reviewer.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gp201/agent-skills --skill experiment-report-gp201
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: experiment-report
Source: https://github.com/gp201/agent-skills/tree/main/skills/experiment-report
Command: npx skills add https://github.com/gp201/agent-skills --skill experiment-report-gp201

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft a short, claim-driven IMRaD-style report for a completed experiment run, then hand it to a reviewer that validates structure and evidence against the run data.

Core Features & Use Cases

  • Generate an IMRaD-format report under reports/<slug>.md from run data under runs/<id>/.
  • Trigger a scientific-writing reviewer to assess claim-evidence linkage and uncertainty against the run.
  • Produce a concise, reviewer-ready document suitable for lab notebooks, PR descriptions, or internal memos.

Quick Start

Draft a report for runs/ABC123 and run the WRITING_RUBRIC reviewer.

Frequently Asked Questions about experiment-report

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

FAQPage Schema
How do I draft an IMRaD report from experiment run data?▼

To draft an IMRaD report from experiment run data, you need a completed run directory where the tool processes your run data to generate a formal write-up under reports/<slug>.md.

Does this experiment reporting tool validate claims against the actual run data?▼

Yes, the experiment reporting tool invokes a WRITING_RUBRIC reviewer subagent that validates claim-evidence linkage and uncertainty against the completed run data.

Can I use these IMRaD experiment reports for pull request descriptions and lab notes?▼

You can use the generated IMRaD experiment reports for lab notebooks, pull request descriptions, and internal memos because it produces concise, reviewer-ready documents.

What is the best way to automate scientific writing for completed experiment runs?▼

The best way to automate scientific writing for completed experiment runs is to trigger a report generation tool that drafts claim-driven IMRaD-style documents directly from your run directory.

Do I need a specific directory structure to generate scientific experiment reports?▼

You need an existing run directory structured as runs/<id>/ containing your completed experiment data to generate the corresponding scientific experiment report.

What are the limitations of using automated IMRaD report generation for experiments?▼

A limitation of automated IMRaD report generation is that it strictly requires an existing run directory with completed data, meaning it cannot draft reports for incomplete or missing experiment runs.