exp-lens-reproducibility-artifacts
Skill1 starsChanged 8 months agoMITView on GitHub
Create Reproducibility Artifacts experimental design diagram showing run instructions, environment capture, data availability, determinism controls, and audit trail. Transparency lens answering "Could an independent party reproduce this?
In this repository59 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- arch-lens-c4-containerSkill
- arch-lens-concurrencySkill
- arch-lens-data-lineageSkill
- arch-lens-deploymentSkill
- arch-lens-developmentSkill
- arch-lens-error-resilienceSkill
- arch-lens-module-dependencySkill
- arch-lens-operationalSkill
- arch-lens-process-flowSkill
- arch-lens-repository-accessSkill
- arch-lens-scenariosSkill
- arch-lens-securitySkill
- arch-lens-state-lifecycleSkill
- audit-archSkill
- audit-bugsSkill
- audit-cohesionSkill
- audit-defense-standardsSkill
- audit-frictionSkill
- audit-implSkill
- audit-testsSkill
- design-guardsSkill
- dry-walkthroughSkill
- elaborate-phaseSkill
- exp-lens-benchmark-representativenessSkill
- exp-lens-causal-assumptionsSkill
- exp-lens-comparator-constructionSkill
- exp-lens-error-budgetSkill
- exp-lens-estimand-claritySkill
- exp-lens-exploratory-confirmatorySkill
- exp-lens-fair-comparisonSkill
- exp-lens-governance-riskSkill
- exp-lens-iterative-learningSkill
- exp-lens-measurement-validitySkill
- exp-lens-pipeline-integritySkill
- exp-lens-randomization-blockingSkill
- exp-lens-sensitivity-robustnessSkill
- exp-lens-severity-testingSkill
- exp-lens-unit-interferenceSkill
- exp-lens-validity-threatsSkill
- exp-lens-variance-stabilitySkill
- id-slopSkill
- implement-worktreeSkill
- investigateSkill
- make-arch-diagSkill
- make-experiment-diagSkill
- make-groupsSkill
- make-planSkill
- make-reqSkill
- make-scenariosSkill
- mermaidSkill
- plan-arcSkill
- rectifySkill
- review-approachSkill
- update-architectureSkill
- update-reqsSkill
- update-specsSkill
- verify-diagSkill
- verify-proposed-diagSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Focus: Run Instructions, Environment Capture, Data Availability, Determinism Controls, Audit Trail
- Distinctive: line 30
Do not litter the codebase with useless comments, TODO markers, or explanatory annotations — the skill output and diagram speak for …
- Very specific: line 37
BEFORE creating any diagram, LOAD the /mermaid skill using the Skill tool - this is MANDATORY
- Very specific: line 49
Look for: requirements, Dockerfile, environment.yml, conda, pip, nix, lock
- Distinctive: line 53
Look for: download, checksum, hash, version, dvc, data_url, manifest
- Very specific: line 57
Look for: Makefile, run.sh, snakemake, nextflow, main, entrypoint, cli
- Distinctive: line 61
Look for: seed, random_state, deterministic, cudnn, PYTHONHASHSEED
- Distinctive: line 65
Look for: save, log, output, results, figures, checkpoint, wandb, mlflow
- Very specific: line 112
Write the diagram to: temp/exp-lens-reproducibility-artifacts/exp_diag_reproducibility_artifacts_{YYYY-MM-DD_HHMMSS}.md
- Distinctive: line 231
Before creating the diagram, verify:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Reproducibility Artifacts Experimental Design Lens
Philosophical Mode: Transparency Primary Question: "Could an independent party reproduce this?" Focus: Run Instructions, Environment Capture, Data Availability, Determinism Controls, Audit Trail
When to Use
- Evaluating reproducibility of computational experiments
- Auditing artifact completeness
- Checking for undocumented dependencies
- User invokes
/exp-lens-reproducibility-artifactsor/make-experiment-diag reproducibility
Critical Constraints
NEVER:
- Modify any source code files
- Do not litter the codebase with useless comments, TODO markers, or explanatory annotations — the skill output and diagram speak for themselves
ALWAYS:
- Trace the full chain from "clone repo" to "reproduce figures"
- Classify every artifact as available/unavailable and versioned/floating
- Identify the weakest link in the reproduction chain
- Flag all silent non-determinism risks
- BEFORE creating any diagram, LOAD the
/mermaidskill using the Skill tool - this is MANDATORY
Analysis Workflow
Step 1: Launch Parallel Exploration Subagents
Spawn Explore subagents to investigate:
Environment & Dependencies
- Find dependency files, container definitions, environment setup
- Look for: requirements, Dockerfile, environment.yml, conda, pip, nix, lock
Data Provenance
- Find data download scripts, checksums, versioning
- Look for: download, checksum, hash, version, dvc, data_url, manifest
Execution Entry Points
- Find run scripts, Makefiles, workflow managers
- Look for: Makefile, run.sh, snakemake, nextflow, main, entrypoint, cli
Random Seed & Determinism
- Find seed setting, nondeterminism controls
- Look for: seed, random_state, deterministic, cudnn, PYTHONHASHSEED
Output Artifacts & Logging
- Find result storage, logging, figure generation
- Look for: save, log, output, results, figures, checkpoint, wandb, mlflow
Step 2: Map the Reproduction Chain
Map the full chain from "clone repo" to "reproduce figures." Identify each link:
- Is it documented?
- Is it automated?
- Is it deterministic?
- What is the weakest link?
Step 3: Classify Each Artifact Dependency
CRITICAL — Analyze Reproduction Chain: For every artifact dependency:
- Is the source available (open vs gated)?
- Is the version pinned or floating?
- Is the transform deterministic?
- Could silent environment differences change results?
Assign a status of Pass, Warn, or Fail to each link in the chain based on reproducibility confidence.
Step 4: Create the Diagram
Use flowchart with:
Direction: LR (reproduction chain flows left to right)
Subgraphs:
- SOURCE CODE
- ENVIRONMENT
- DATA
- EXECUTION
- OUTPUTS
Node Styling:
cliclass: Entry points and run commandsstateNodeclass: Versioned and pinned artifactshandlerclass: Transforms and scriptsoutputclass: Results and figuresgapclass: Missing or undocumented linksdetectorclass: Checksum and validation gatesphaseclass: External dependencies
Edge Labels: pinned, floating, deterministic, nondeterministic, gated
Step 5: Write Output
Write the diagram to: temp/exp-lens-reproducibility-artifacts/exp_diag_reproducibility_artifacts_{YYYY-MM-DD_HHMMSS}.md
Output Template
# Reproducibility Artifacts Diagram: {Experiment Name}
**Lens:** Reproducibility Artifacts (Transparency)
**Question:** Could an independent party reproduce this?
**Date:** {YYYY-MM-DD}
**Scope:** {What was analyzed}
## Artifact Inventory
| Artifact | Available? | Versioned? | Deterministic? |
|----------|------------|------------|----------------|
| {artifact} | {Yes/No/Gated} | {Pinned/Floating/None} | {Yes/No/Unknown} |
## Reproduction Chain Diagram
```mermaid
%%{init: {'flowchart': {'nodeSpacing': 50, 'rankSpacing': 60, 'curve': 'basis'}}}%%
flowchart LR
%% CLASS DEFINITIONS %%
classDef cli fill:#1a237e,stroke:#7986cb,stroke-width:2px,color:#fff;
classDef stateNode fill:#004d40,stroke:#4db6ac,stroke-width:2px,color:#fff;
classDef handler fill:#e65100,stroke:#ffb74d,stroke-width:2px,color:#fff;
classDef phase fill:#6a1b9a,stroke:#ba68c8,stroke-width:2px,color:#fff;
classDef newComponent fill:#2e7d32,stroke:#81c784,stroke-width:2px,color:#fff;
classDef output fill:#00695c,stroke:#4db6ac,stroke-width:2px,color:#fff;
classDef detector fill:#b71c1c,stroke:#ef5350,stroke-width:2px,color:#fff;
classDef gap fill:#ff6f00,stroke:#ffa726,stroke-width:2px,color:#000;
classDef integration fill:#c62828,stroke:#ef9a9a,stroke-width:2px,color:#fff;
subgraph Source ["SOURCE CODE"]
REPO["Git Repository<br/>━━━━━━━━━━<br/>Commit hash<br/>Branch"]
ENTRY["Entry Point<br/>━━━━━━━━━━<br/>run.sh / Makefile"]
end
subgraph Env ["ENVIRONMENT"]
DEPS["Dependencies<br/>━━━━━━━━━━<br/>requirements.txt / lock"]
MISSING["Undocumented Dep<br/>━━━━━━━━━━<br/>No version pin"]
EXTDEP["External Service<br/>━━━━━━━━━━<br/>API / cloud resource"]
end
subgraph Data ["DATA"]
RAW["Raw Dataset<br/>━━━━━━━━━━<br/>Checksum available?"]
CHKSUM["Checksum Gate<br/>━━━━━━━━━━<br/>sha256 / md5"]
GATED["Gated Dataset<br/>━━━━━━━━━━<br/>Access required"]
end
subgraph Exec ["EXECUTION"]
SEED["Seed Control<br/>━━━━━━━━━━<br/>PYTHONHASHSEED<br/>random_state"]
SCRIPT["Pipeline Script<br/>━━━━━━━━━━<br/>Deterministic?"]
end
subgraph Outputs ["OUTPUTS"]
RESULTS["Results / Metrics<br/>━━━━━━━━━━<br/>Logged?"]
FIGS["Figures<br/>━━━━━━━━━━<br/>Reproducible?"]
end
%% REPRODUCTION CHAIN %%
REPO -->|"pinned"| ENTRY
ENTRY -->|"loads"| DEPS
DEPS -.->|"floating"| MISSING
MISSING -.->|"nondeterministic"| SCRIPT
EXTDEP -->|"gated"| SCRIPT
RAW -->|"verify"| CHKSUM
CHKSUM -->|"deterministic"| SCRIPT
GATED -.->|"gated"| SCRIPT
SEED -->|"controls"| SCRIPT
SCRIPT -->|"produces"| RESULTS
SCRIPT -->|"generates"| FIGS
%% CLASS ASSIGNMENTS %%
class REPO,ENTRY cli;
class DEPS,RAW stateNode;
class SCRIPT,SEED handler;
class EXTDEP phase;
class RESULTS,FIGS output;
class CHKSUM detector;
class MISSING,GATED gap;Color Legend:
| Color | Category | Description |
| Dark Blue | Entry Point | Run commands and source code |
| Teal | Versioned Artifact | Pinned dependencies and checksummed data |
| Orange | Transform / Script | Pipeline scripts and execution steps |
| Purple | External Dependency | External services and APIs |
| Dark Teal | Output | Results, metrics, and figures |
| Red | Validation Gate | Checksum and integrity checks |
| Amber | Missing Link | Undocumented or gated dependencies |
Reproduction Checklist
Step-by-step instructions with pass/fail status:
- Clone repository at pinned commit
- Reproduce environment from lock/container file
- Download data and verify checksums
- Set all random seeds as documented
- Execute pipeline via documented entry point
- Compare output metrics/figures to reported values
Weakest Links
| Link | Issue | Severity | Recommendation |
| {link} | {undocumented/gated/floating/nondeterministic} | {High/Medium/Low} | {action} |
---
## Pre-Diagram Checklist
Before creating the diagram, verify:
- [ ] LOADED `/mermaid` skill using the Skill tool
- [ ] Using ONLY classDef styles from the mermaid skill (no invented colors)
- [ ] Diagram will include a color legend table
---
## Related Skills
- `/make-experiment-diag` - Parent skill for lens selection
- `/mermaid` - MUST BE LOADED before creating diagram
- `/exp-lens-pipeline-integrity` - For data leakage audit
- `/exp-lens-variance-stability` - For result stability across seedsDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

