reproducibility

Promotes research reproducibility through guidance on pre-registration, open data/code sharing, replication study design, computational reproducibility, and open science best practices; trigger when users discuss replication, open science, pre-registration, data sharing, or research transparency.

564 stars

Best use case

reproducibility is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Promotes research reproducibility through guidance on pre-registration, open data/code sharing, replication study design, computational reproducibility, and open science best practices; trigger when users discuss replication, open science, pre-registration, data sharing, or research transparency.

Teams using reproducibility should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/reproducibility/SKILL.md --create-dirs "https://raw.githubusercontent.com/beita6969/ScienceClaw/main/skills/reproducibility/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/reproducibility/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How reproducibility Compares

Feature / AgentreproducibilityStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Promotes research reproducibility through guidance on pre-registration, open data/code sharing, replication study design, computational reproducibility, and open science best practices; trigger when users discuss replication, open science, pre-registration, data sharing, or research transparency.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

## When to Trigger

Activate this skill when the user mentions:
- Reproducibility, replicability, replication crisis
- Pre-registration, registered reports, AsPredicted
- Open data, data sharing, FAIR principles
- Open code, computational reproducibility, Docker, containers
- Open access publishing, preprints, green/gold OA
- Research transparency, open science framework (OSF)
- P-hacking, HARKing, questionable research practices
- Power analysis for replication, replication study design

## Step-by-Step Methodology

1. **Assess current reproducibility state** - Evaluate the research against reproducibility dimensions: methodological (sufficient detail to replicate), computational (code + data + environment = same results), and results reproducibility (independent replication yields consistent findings). Identify specific gaps.
2. **Pre-registration** - Guide pre-registration of hypotheses, methods, and analysis plan BEFORE data collection. Use appropriate platform: OSF Registries, AsPredicted, ClinicalTrials.gov (clinical), or PROSPERO (systematic reviews). Distinguish confirmatory from exploratory analyses.
3. **Data management** - Apply FAIR principles: Findable (persistent identifier, metadata), Accessible (open or controlled access with clear process), Interoperable (standard formats, vocabularies), Reusable (license, provenance). Create data dictionary documenting every variable. Use tidy data formats.
4. **Code and computational environment** - Share analysis code in a public repository (GitHub, GitLab, Zenodo for DOI). Document dependencies with requirements.txt, renv.lock, or conda environment.yml. For full reproducibility: containerize with Docker or use Binder. Include README with execution instructions.
5. **Replication study design** - For direct replication: match original methods as closely as possible. For conceptual replication: test same hypothesis with different methods. Conduct power analysis based on original effect size (use safeguard power: assume smaller effect). Determine sample size for meaningful replication test (use equivalence testing or Bayesian replication factors).
6. **Reporting transparency** - Follow reporting guidelines (CONSORT, STROBE, ARRIVE, PRISMA). Report all pre-specified analyses regardless of results. Clearly label exploratory analyses. Share full materials (stimuli, protocols, instruments) as supplementary files.
7. **Open science practices** - Adopt open science badges (data, materials, pre-registration). Consider registered reports format (peer review before results). Use preprint servers (bioRxiv, medRxiv, arXiv, SSRN). Choose open access publication route.

## Key Platforms and Tools

- **OSF (Open Science Framework)** - Project management and pre-registration
- **AsPredicted** - Streamlined pre-registration
- **Zenodo** - Data and code archival with DOI
- **GitHub / GitLab** - Code version control and sharing
- **Docker / Binder** - Computational environment reproducibility
- **FAIR self-assessment tool** - Data FAIRness evaluation
- **COS (Center for Open Science)** - Reproducibility guidelines

## Output Format

- Reproducibility assessment: checklist of current state vs. best practices.
- Pre-registration template: hypotheses, design, sample, variables, analysis plan.
- Data sharing package: dataset + data dictionary + codebook + license + README.
- Computational reproducibility: repository structure, Dockerfile, execution instructions.
- Replication study protocol: power analysis, design, success criteria (equivalence test bounds or replication Bayes factor thresholds).

## Quality Checklist

- [ ] Pre-registration completed before data collection/analysis
- [ ] Confirmatory and exploratory analyses clearly distinguished
- [ ] Data deposited in trusted repository with persistent identifier (DOI)
- [ ] FAIR principles self-assessment completed
- [ ] Analysis code shared and tested on a clean environment
- [ ] Computational environment documented or containerized
- [ ] All materials sufficient for independent replication
- [ ] Reporting guideline checklist completed
- [ ] License specified for data (CC-BY, CC0) and code (MIT, Apache)
- [ ] Deviations from pre-registration documented and justified

Related Skills

reproducibility-checklist

564
from beita6969/ScienceClaw

No description provided.

xurl

564
from beita6969/ScienceClaw

A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.

xlsx

564
from beita6969/ScienceClaw

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

writing

564
from beita6969/ScienceClaw

No description provided.

world-bank-data

564
from beita6969/ScienceClaw

World Bank Open Data API for development indicators. Use when: user asks about GDP, population, poverty, health, or education statistics by country. NOT for: real-time financial data or stock prices.

wikipedia-search

564
from beita6969/ScienceClaw

Search and fetch structured content from Wikipedia using the MediaWiki API for reliable, encyclopedic information

wikidata-knowledge

564
from beita6969/ScienceClaw

Query Wikidata for structured knowledge using SPARQL and entity search. Use when: (1) finding structured facts about entities (people, places, organizations), (2) querying relationships between entities, (3) cross-referencing external identifiers (Wikipedia, VIAF, GND, ORCID), (4) building knowledge graphs from linked data. NOT for: full-text article content (use Wikipedia API), scientific literature (use semantic-scholar), geospatial data (use OpenStreetMap).

weather

564
from beita6969/ScienceClaw

Get current weather and forecasts via wttr.in or Open-Meteo. Use when: user asks about weather, temperature, or forecasts for any location. NOT for: historical weather data, severe weather alerts, or detailed meteorological analysis. No API key needed.

wacli

564
from beita6969/ScienceClaw

Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).

voice-call

564
from beita6969/ScienceClaw

Start voice calls via the OpenClaw voice-call plugin.

visualization

564
from beita6969/ScienceClaw

Create publication-quality scientific figures and plots using Python (matplotlib, seaborn, plotly). Supports bar charts, scatter plots, heatmaps, box plots, violin plots, survival curves, network graphs, and more. Use when user asks to plot data, create figures, make charts, visualize results, or generate publication-ready graphics. Triggers on "plot", "chart", "figure", "graph", "visualize", "heatmap", "scatter plot", "bar chart", "histogram".

video-frames

564
from beita6969/ScienceClaw

Extract frames or short clips from videos using ffmpeg.