conext-artifact-evaluation
Use when converting an accepted ACM CoNEXT paper's package into optional ACM reproducibility badges via the CoNEXT reproducibility committee — from the badge opt-in due before submission, to the one-page artifact description due within a week of acceptance, to the Available / Functional / Reusable / Reproduced criteria and evaluator-proof reuse docs.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-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.
# CoNEXT Artifact Evaluation Turn the accepted paper's package into **optional ACM reproducibility badges**, administered by CoNEXT's **reproducibility committee**. This is a distinct process from the paper review, with its own timing: the decisive move — **opting in before the paper submission deadline** — happens long before you have an accept. Treat badging as a track you enter at submission and complete after acceptance. ## The badge timeline (opt-in is the gate) ```text [Before submission deadline] OPT IN for ACM badging <-- miss this and you are ineligible this cycle [Within ~1 week of accept] send a ONE-PAGE artifact description + pointers to the committee [Post-accept evaluation] committee reviews the artifact against the ACM badge criteria [Camera-ready] approved badges appear on the PACMNET article (see conext-camera-ready) ``` ## The ACM badges (what each requires) CoNEXT uses the ACM Artifact Review and Badging scheme. In practice the ladder is: | Badge | What it certifies | What you must provide | |---|---|---| | **Artifacts Available** | The artifact is publicly archived | A DOI-issuing archive (Zenodo/figshare/Software Heritage) with an open license | | **Artifacts E
- The badge timeline (opt-in is the gate)
- The ACM badges (what each requires)
- The one-page artifact description
- Networking-specific evaluation hurdles
- Reusability that survives an evaluator
- Pre-evaluation checklist
- Output format
What does the conext-artifact-evaluation skill do?
Use when converting an accepted ACM CoNEXT paper's package into optional ACM reproducibility badges via the CoNEXT reproducibility committee — from the badge opt-in due before submission, to the one-page artifact description due within a week of acceptance, to the Available / Functional / Reusable / Reproduced criteria and evaluator-proof reuse docs.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-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.