icdm-submission
Use when auditing an ICDM (IEEE International Conference on Data Mining) submission for readiness, covering Research-vs-Applied track choice and its anonymity regime, the triple-blind sweep, the 10-page IEEE all-inclusive cap, the single June deadline, in-paper artifact references, and the desk-level triggers that get an ICDM paper rejected without review.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-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.
# ICDM Submission Run this audit twice: once when the abstract is registered and once before the full-paper deadline about a week later (2026: abstract May 30, paper June 6, AoE). ICDM runs a **single deadline**, not KDD-style cycles, so there is no next window this year — the paper you upload in June is the paper that gets reviewed. Reopen the current **track** call first; Research and Applied now differ on anonymity. ## Track and anonymity regime first - **Research Track is triple-blind**; the **2026 Applied Track is single-blind**; the **Blue Sky Track** (CCC-sponsored) is a separate visionary lane. Pick the track before formatting, because it decides whether the paper must hide author identity at all. - One paper, one track: do not submit the same work to Research and Applied at once. - If the contribution is a deployed system with measured real-world impact, the Applied Track may fit better and its single-blind regime removes the anonymization burden — but confirm the current call's Applied scope before switching. ## The triple-blind sweep (Research Track) ICDM's triple-blind tradition (since 2011) is stricter than double-blind: author *and* referee identities are hidden, know
- Track and anonymity regime first
- The triple-blind sweep (Research Track)
- The 10-page all-inclusive cap
- Desk-level and severity table
- Final-week sequence
- Vignette: a paper that lost a page to its own bibliography
- Output format
What does the icdm-submission skill do?
Use when auditing an ICDM (IEEE International Conference on Data Mining) submission for readiness, covering Research-vs-Applied track choice and its anonymity regime, the triple-blind sweep, the 10-page IEEE all-inclusive cap, the single June deadline, in-paper artifact references, and the desk-level triggers that get an ICDM paper rejected without review.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-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 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.