soda-artifact-evaluation
Use when deciding how code, computations, or data attach to a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — SODA itself runs no artifact track, so this skill covers computer-assisted proof evidence, implementation companions, and when to route the artifact to co-located ALENEX's formal artifact evaluation instead.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soda-artifact-evaluation --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.
# SODA Artifact Evaluation First, the venue truth: **SODA has no artifact-evaluation track.** Referees judge proofs, not repositories. But two kinds of computational objects still matter to a SODA author, and the co-located satellite ALENEX runs a genuine AE process — for the 2027 cycle, ALENEX's dates were: submission July 20, 2026; notification early September 2026; artifact submission September 11, 2026; AE rebuttal October 12-14; AE results by October 16, 2026, with a dedicated HotCRP AE site (`alenex27ae.hotcrp.com`; checked 2026-07-08 via search renderings of the SIAM ALENEX27 pages). ## Which of three situations are you in? | Situation | Artifact's role | Correct home | |---|---|---| | Proof relies on machine computation (case enumeration, SAT/ILP certificate, verified numerics) | Part of the proof — reviewers must be able to check it | The SODA submission itself, described in the paper, archive linked | | Implementation exists but the claim is the theorem | Supporting color; zero review weight at SODA | arXiv full version appendix + repository; one paragraph in the paper | | The experiments are the contribution (engineering, tuning, real datasets) | The reviewed object | AL
- Which of three situations are you in?
- Computer-assisted proof evidence at SODA
- Certificate patterns by claim type
- Routing to ALENEX AE
- Referee psychology of computer-assisted claims
- Post-acceptance artifact hygiene (either venue)
- Output format
What does the soda-artifact-evaluation skill do?
Use when deciding how code, computations, or data attach to a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — SODA itself runs no artifact track, so this skill covers computer-assisted proof evidence, implementation companions, and when to route the artifact to co-located ALENEX's formal artifact evaluation instead.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soda-artifact-evaluation --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.