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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-reproducibility --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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). - Provide an **anonymized** link or upload now; "available upon request" reads as a scored weakness, not a neutral placeholder. - Match the statement to what the archive actually contains — an overclaiming statement is worse than a modest, honest one. ## Anonymized-but-runnable tools - Re-host the tool and dataset behind an **anonymizing service**; strip repository owner, commit author metadata, and any path revealing your identity (`/home/<y
- The mandatory Data Availability Statement
- Anonymized-but-runnable tools
- Provenance pinning (do this at collection time)
- Reproducibility failure modes (ASE-specific)
- From submission to the ACM badges
- Output format
What does the ase-reproducibility skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-reproducibility --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.