experiment-structure

Scaffold a canonical experiment folder layout with configs, src, data, runs, analysis, figures, and documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical folder layout for computational experiments and the conventions that keep them reproducible. It ensures new work starts from a solid, auditable structure and guides where things belong.

Core Features & Use Cases

  • Provides a canonical layout template (configs/, src/, data/, runs/, analysis/, figures/, README) and the rules that keep it honest.
  • Used when starting a new experiment or when another skill needs a destination directory and none exists.
  • Answers common questions like "where does X go?" by providing a single authoritative structure to follow.

Quick Start

Create a new experiment folder using the canonical structure described here.

Frequently Asked Questions about experiment-structure

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

FAQPage Schema
What is the best way to organize reproducible experiment folders?

A canonical folder layout for reproducible experiments includes directories for configs, src, data, runs, analysis, and figures. This structure enforces provenance rules and provides an auditable map for where project files belong.

How do I scaffold a new computational experiment project structure?

To scaffold a new computational experiment, generate the canonical directory tree containing configs, src, data, runs, analysis, figures, and documentation. This establishes required conventions immediately and ensures the project starts from an auditable structure.

When do I need a provenance structure for my computational experiments?

You need a provenance structure for computational experiments when starting new work or when a process requires a destination directory. It ensures your project remains organized, auditable, and reproducible by enforcing where data, source, and analysis files belong.

Does this experiment scaffold work without external dependencies?

Yes, this experiment scaffold works without external dependencies. It defines the required directories and provenance rules for project organization natively, ensuring your computational experiments remain reproducible without needing additional frameworks.

Where do configuration and analysis files go in a reproducible project layout?

In a reproducible project layout, configuration files go in the configs directory and analysis files go in the analysis directory. This canonical experiment folder structure provides a single authoritative answer for where every project artifact belongs.