sigir-camera-ready
Use when an accepted SIGIR paper must become the ACM Digital Library version of record — de-anonymizing the sigconf source, CCS concepts and keywords, the e-rights form, TAPS source upload and proof checking, restoring real system and dataset names, and the April camera-ready window before the July conference.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigir-camera-ready --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.
# SIGIR Camera Ready SIGIR publishes through ACM: the version of record is produced by ACM's pipeline (e-rights, then TAPS) from your **source files**, and it appears in the Digital Library as both PDF and HTML (SIGIR 2025's volume is DOI 10.1145/3726302). The 2026 camera-ready window sat in late April for the tracks whose dates were verifiable (April 29, 2026 for Resources / Low Resource Environments); take your own track's date from the acceptance email, and note the July conference leaves little slack. ## What changes between the reviewed PDF and the record | Item | Reviewed submission | Version of record | |---|---|---| | Document class | `sigconf` + anonymous/review options | `sigconf` with rights commands from TAPS | | Authors | Hidden | Restored; order frozen **before** e-rights | | System name | Possibly a review alias | Real name, consistent with the public repo | | Dataset/log provenance | Genericized for anonymity | As precise as data agreements allow | | Repository link | Anonymous mirror | Public, licensed, stable (archival DOI best) | | Acknowledgments | Absent | Restored — and they cost body pages at SIGIR | | CCS concepts + keywords | Often placeholders | Final; the
- What changes between the reviewed PDF and the record
- The ACM production sequence
- Digital Library metadata that outlives the conference
- Artifacts at publication time
- Worked example: absorbing review debts into the budget
- Registration and presentation
- Timeline discipline
- Output format
Sweep before zipping for TAPS
grep -rn "ANON\|anonym" *.tex sections/ # stale review aliases
grep -rn "4open\|anonymous.4open" *.tex # anonymous mirror still linked?
grep -rn "vspace\|renewcommand{\\\\baselinestretch}" *.tex # spacing hacks
ls figures/ | wc -l && grep -c includegraphics *.tex # figure inventory matchWhat does the sigir-camera-ready skill do?
Use when an accepted SIGIR paper must become the ACM Digital Library version of record — de-anonymizing the sigconf source, CCS concepts and keywords, the e-rights form, TAPS source upload and proof checking, restoring real system and dataset names, and the April camera-ready window before the July conference.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigir-camera-ready --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.