sigir-submission
Use when auditing a SIGIR full or short paper before the deadline — the 9-page vs 4-page budgets with appendices counted inside, ACM sigconf anonymization, per-track OpenReview groups, the PC-member nomination duty, cross-track double-submission bans, AI-use disclosure, and desk-reject triage for the ACM SIGIR conference.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigir-submission --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 Submission Run this audit before anything is uploaded to a SIGIR OpenReview group. SIGIR is a multi-track venue where the same manuscript can be legal in one track and desk-rejectable in another, so the audit starts with "which track is this PDF for?" and only then checks format. Reopen the current edition's track page — every number below is a 2026-cycle anchor (verified 2026-07-08, exact deadlines 待核实), not a rule. ## The two-format trap SIGIR's full and short formats are not a long and a short version of the same bar. A 4-page short paper is a complete argument about one focused finding; a 9-page full paper is expected to carry a rounded evidence program (multiple collections, ablations, significance tests, efficiency notes). The most common self-inflicted wound is submitting a compressed full paper as a short paper — reviewers see missing evidence, not admirable focus. | Check | Full papers | Short papers | |---|---|---| | Page budget (2026) | ≤ 9 pages, references excluded | ≤ 4 pages, references excluded | | Appendices | Count **inside** the budget (2025 wording: everything except references) | Same — no appendix escape hatch | | Template | ACM Primary Article Templat
- The two-format trap
- Anonymization for IR papers specifically
- Policy gates (2026, source: submission-policies page)
- Desk-reject triage
- Final-week sequence for a retrieval paper
- Abstract-deadline gotchas
- What this audit does not cover
- Output format
Pre-upload checks that catch the silent killers pdfinfo paper.pdf | grep -iE "author|creator" # metadata identity leak grep -inE "acknowledg|our (system|engine|company)" *.tex # textual leaks grep -c "documentclass\[sigconf" main.tex # right ACM class pdftotext paper.pdf - | grep -icE "p ?[<=] ?0\.05|t-test|significan" # stats present?
What does the sigir-submission skill do?
Use when auditing a SIGIR full or short paper before the deadline — the 9-page vs 4-page budgets with appendices counted inside, ACM sigconf anonymization, per-track OpenReview groups, the PC-member nomination duty, cross-track double-submission bans, AI-use disclosure, and desk-reject triage for the ACM SIGIR conference.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigir-submission --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 984 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.