Individual skill
ase-reproducibility
Use when building the open-science and reproducibility story for an ASE (IEEE/ACM Automated Software Engineering) submission, covering the mandatory Data Availability Statement, anonymized-but-runnable tools, tool and subject-system provenance pinning, cached LLM outputs, and staging for the ACM Available/Reusable artifact badges.
ASE-Skills/skills/ase-reproducibility/SKILL.md
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.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- engineering Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,305 bytes
Read excerpt
# ASE Reproducibility
Build the reproducibility story at data-collection time, not at submission. ASE requires a
**mandatory Data Availability Statement** in the paper and expects an **anonymized, runnable**
artifact at review time; automated-SE artifacts are usually *tools*, so "runnable" means a reviewer
can actually execute the automation on stated subjects. What is not pinned when you collect it
cannot be reconstructed later.
## The mandatory Data Availability Statement
- **Required**, placed **after the Conclusions** and **inside the 10-page limit** (it is not free
appendix space).
- State what exists — the tool, the dataset, the subject systems, the scripts, the logs — and
**where it will live** after acceptance (an archival DOI target).