Individual skill

reproducibility-statement

Prepare the reproducibility, transparency and open-science parts of a paper, including data and code availability statements, reproducibility checklists (NeurIPS, ICML, ICLR, ACL Responsible NLP, Nature reporting summaries), research artifact packaging (Zenodo DOI, CITATION.cff, environment lockfiles, seeds), ethics/broader-impact statements, CRediT author contributions, competing interests and AI-use disclosures. Use when a venue requires any of these statements or checklists, or when preparing code/data for release alongside a paper.

plugins/KalarisLabs/research-agent-skills/skills/reproducibility-statement/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Reproducibility and Transparency Statements

## Workflow

1. List every statement and checklist the venue requires (section 1).
2. Deposit data and code, and obtain persistent identifiers before writing the statements.
3. Draft each statement with concrete locations, licenses and access conditions.
4. Verify every link and accession while logged out. Never claim availability that does not exist yet.
5. Answer checklists honestly, with a justification for each "No".

Editors increasingly desk-reject for missing or vague statements, and reviewers
check them. Treat each as a precise, verifiable claim, never boilerplate.

## 1. Find out what the venue requires