experiment-provenance

Record experiment provenance and reproducible run metadata for research workflows.

88|16|Updated Feb 12, 2026

Search Tags:#workflow #auditing #provenance #evidence #traceability #reproducibility #experiments

Ready to run

npx skills add https://github.com/drpedapati/sciclaw --skill experiment-provenance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: experiment-provenance
Source: https://github.com/drpedapati/sciclaw/tree/main/skills/experiment-provenance
Command: npx skills add https://github.com/drpedapati/sciclaw --skill experiment-provenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture provenance of experiments to ensure reproducibility and provide an auditable trail for scientific claims.

Core Features & Use Cases

Track provenance: objective, hypothesis, exact commands, inputs, environment assumptions, and output artifacts.
Log run details and decision points to support manuscript validation.
Link provenance notes to plans/main-plan-activity.md and plans/main-plan-log.csv for full traceability.
Use-case example: during a lab workflow, record the steps, outputs, and rationale to reproduce results and defend claims.

Quick Start

Record the experiment intent, run deterministically where possible, and attach outputs to the provenance records.

Frequently Asked Questions about experiment-provenance

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

FAQPage Schema

What is experiment provenance and why do I need to track it for reproducible research?▼

Experiment provenance records the objectives, hypotheses, exact commands, inputs, and environment assumptions of a run. Tracking provenance provides an auditable evidence trail to support manuscript claims and ensure scientific reproducibility.

How do I capture reproducible run metadata for a data analysis workflow?▼

Capture reproducible run metadata by logging the experiment intent, running commands deterministically where possible, and attaching output artifacts. You then record validation status, uncertainty notes, and decision points to link provenance to planning artifacts.

Can I use provenance tracking to link experiment outputs directly to manuscript validation logs?▼

Yes, provenance tracking links run details and decision points to support manuscript validation. It connects captured evidence and output artifacts directly to planning logs for full traceability of scientific claims.

What's the best way to maintain traceability across scientific experiments and planning artifacts?▼

Maintain traceability by linking provenance notes to planning artifacts and logs. This connects objectives, exact commands, and environment assumptions to the main planning files for a full auditable trail across experiments.

Does experiment provenance tracking require specific dependencies or environment setup tools?▼

Experiment provenance tracking does not require specific dependencies or environment setup tools. It functions by recording environment assumptions and exact commands directly to capture evidence and validate reproducibility.

What should provenance records include to fully defend scientific claims during auditing?▼

Provenance records should include objectives, hypotheses, exact commands, inputs, environment assumptions, outputs, validation status, and uncertainty notes. Capturing these elements provides the evidence needed to defend manuscript claims during auditing.