icdm-supplementary
Use when organizing supplementary and appendix material for an ICDM (IEEE International Conference on Data Mining) paper - deciding what belongs in the body, in an appendix that counts inside the single 10-page IEEE cap, or in an external anonymized repository, plus planning the compression if the paper is accepted as a short paper.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-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.
# ICDM Supplementary Decide where each piece of evidence lives under ICDM's unusual constraint: the appendix is **not** free space. At ICDM the 10-page IEEE two-column cap **includes the bibliography and any appendices**, so an appendix competes with the body for the same pages. Anything that will not fit belongs in the **external anonymized repository**, cited in the PDF. ## The three containers | Container | Counts toward 10 pages? | What belongs there | |---|---|---| | Body | Yes | The mining task, mechanism, main results, the argument's spine | | In-cap appendix | **Yes** | Short proofs, a key ablation table, protocol detail the body references | | External anonymized repo | No | Code, full logs, extra datasets, long proofs, overflow tables | The mistake ICDM punishes is treating the appendix like a KDD/CIKM "extra pages after references" allowance. There is no such allowance here — every appendix line is a body line you chose not to write. ## Allocation rules - The body must be **self-contained**: a reviewer should grasp the contribution and judge correctness without opening the repository, because there is traditionally no rebuttal to clarify later. - Put in the in-cap append
- The three containers
- Allocation rules
- Keep every container triple-blind (Research Track)
- Plan the short-paper compression now
- Vignette: the appendix that cost a reject
- Output format
What does the icdm-supplementary skill do?
Use when organizing supplementary and appendix material for an ICDM (IEEE International Conference on Data Mining) paper - deciding what belongs in the body, in an appendix that counts inside the single 10-page IEEE cap, or in an external anonymized repository, plus planning the compression if the paper is accepted as a short paper.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-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.