Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/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.
Passed 21 of 22 test cases with the skill, and 16 of 22 without it.
and 7 more in the full report
6 fixed15 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
A researcher received a paper acceptance notification from CoNEXT today and wants to apply for ACM badges, but they did not check the artifact opt-in box during original paper submission 4 months ago. Can they submit an artifact now?
| Checked | Without skill | With skill |
|---|---|---|
| Confirms that missing the submission deadline opt-in makes them ineligible for artifact badging | Missed | Passed |
The instructions your model reads when the skill loads.
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.
[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)
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 Evaluated — Functional | It is documented, complete, and runs | Clear docs, a runnable package, and a "getting started" path that works |
| Artifacts Evaluated — Reusable | It is functional and others can build on it | Reusability docs, clean structure, parameterization, and a license that permits reuse |
| Results Reproduced | Key results were regenerated by evaluators | A scripted path that regenerates the paper's central figures/tables from the inputs |
Confirm the exact badge set and names offered by the current CoNEXT reproducibility committee — the scheme is stable but wording is cycle-volatile (待核实).
The committee starts from your one-pager, so make it do work:
test cases passed, vs 16 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.