cikm-supplementary
Use when deciding what supporting material accompanies a CIKM submission given budgets that count appendices inside the page limit, structuring the in-PDF appendix versus the anonymously cited artifact, keeping both double-blind, and handling the uncounted GenAI-disclosure and reference sections correctly.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-supplementary --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.
# CIKM Supplementary CIKM 2026 gives supporting material no free rider: every track's budget counts the appendix **inside** the page limit — 10 pages for full papers, 4/7/4/4 for short/applied/resource/demo — and only the references (full track: up to 2 pages) plus the GenAI Usage Disclosure section sit outside it (source map, 2026-07-08). There is no separate supplementary-upload channel in the verified 2026 calls. The design question is therefore three-way: costed appendix pages, the anonymously cited artifact, or cut. ## The three containers | Container | Costs | Right contents | |---|---|---| | Main body | Budget pages | Everything needed to evaluate the claim unaided | | In-PDF appendix | **Budget pages too** | Only material reviewers must see *during* review that the body cannot hold: a proof, a prompt set, a schema diagram | | Cited anonymous artifact | Zero pages, but discretionary attention | Configs, full hyperparameter grids, extra per-dataset tables, code, data cards | Decision rule per candidate item: *must a reviewer see this to score the paper?* If yes and it is short, appendix — knowing it displaces body content one-for-one. If yes and it is long, restructure the bo
- The three containers
- Building the anonymous artifact
- What the uncounted sections may and may not carry
- Appendix design rules (for the pages you do spend)
- Reviewer-attention economics
- Worked split: a 13-page full-paper draft
- Version-consistency discipline
- Pre-upload verification
- Output format
What does the cikm-supplementary skill do?
Use when deciding what supporting material accompanies a CIKM submission given budgets that count appendices inside the page limit, structuring the in-PDF appendix versus the anonymously cited artifact, keeping both double-blind, and handling the uncounted GenAI-disclosure and reference sections correctly.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-supplementary --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.