Individual skill

icsme-reproducibility

Use when strengthening IEEE ICSME reproducibility and open-science evidence, covering the data-availability statement, anonymized-but-runnable artifacts, mining and LLM provenance pinning, claim-to-evidence mapping, honest degrees of reproducibility, and consistency between the paper and the artifact ahead of the ROSE-Festival IEEE badges.

ICSME-Skills/skills/icsme-reproducibility/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 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,405
Repository last updated
Sep 27, 2026
License
MIT

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

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

# ICSME Reproducibility

Use this before submission and again before camera-ready. ICSME's ROSE-Festival culture makes
reproducibility a valued, sometimes scored dimension rather than a courtesy: double-anonymous
review already expects an inspectable artifact, and the **Joint Artifact Evaluation Track and ROSE
Festival** rewards a permanent, open one with IEEE badges. The goal is that a competent maintainer
could rebuild your evidence — re-mine the corpus, re-run the technique — and reach your conclusions.

## Evidence map

- Map each research-question answer, technique claim, and reported number to a **verifiable
  location** — a paper section, a table generated from logged data, or a script in the artifact.
- For techniques, give enough of the algorithm, parameters, and environment that a reader could
  re-implement or re-run it on their own systems.
Back to top