Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when auditing an ICDM (IEEE International Conference on Data Mining) submission for readiness, covering Research-vs-Applied track choice and its anonymity regime, the…
Install Icdm Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdm-submission --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ICDM-Skills/skills/icdm-submission .claude/skills/icdm-submission && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "icdm-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDM-Skills/skills/icdm-submission into .claude/skills/icdm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdm-submission", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDM-Skills/skills/icdm-submissionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdm-submission --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ICDM-Skills/skills/icdm-submission .agents/skills/icdm-submission && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "icdm-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDM-Skills/skills/icdm-submission into .agents/skills/icdm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdm-submission", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdm-submission --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ICDM-Skills/skills/icdm-submission .cursor/skills/icdm-submission && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "icdm-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDM-Skills/skills/icdm-submission into .cursor/skills/icdm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdm-submission", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path ICDM-Skills/skills/icdm-submission--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdm-submission --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ICDM-Skills/skills/icdm-submission .gemini/skills/icdm-submission && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "icdm-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDM-Skills/skills/icdm-submission into .gemini/skills/icdm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdm-submission", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdm-submissionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-submission -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ICDM-Skills/skills/icdm-submission .github/skills/icdm-submission && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "icdm-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDM-Skills/skills/icdm-submission into .github/skills/icdm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdm-submission", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-submission -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdm-submission --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ICDM-Skills/skills/icdm-submission .opencode/skills/icdm-submission && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "icdm-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDM-Skills/skills/icdm-submission into .opencode/skills/icdm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdm-submission", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
icdm-submission- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 647 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing an ICDM (IEEE International Conference on Data Mining) submission for readiness, covering Research-vs-Applied track choice and its anonymity regime, the…
- Works in 5 steps: Freeze the track choice and confirm the… → Rebuild the PDF from a clean IEEEtran… → Run the triple-blind sweep against the… → …
- Auditing an ICDM (IEEE International Conference on Data Mining) submission for readiness
- SKILL.md covers Track and anonymity regime first, The triple-blind sweep…, The 10-page all-inclusive cap and Desk-level and severity table, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Icdm Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- 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
Example prompts
- “/icdm-submission”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Freeze the track choice and confirm the anonymity regime it implies.
- Rebuild the PDF from a clean IEEEtran checkout; measure to the bottom of page 10 with
- Run the triple-blind sweep against the list above (Research Track): names, self-cites,
- Export a fresh anonymized repository with no git history and no institutional paths;
- Register the abstract early in the week; upload the paper with hours, not minutes, of
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are latex).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Icdm Submission loads about 1.4k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 647 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 647 words, ~1,384 tokens.
Download SKILL.mdSave it as
.claude/skills/icdm-submission/SKILL.md (or your agent's skills folder).- name
- icdm-submission
- description
- 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.
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, known only to the PC Co-Chairs, and author names are revealed only after acceptance is finalized. Your obligation is to conceal identity throughout the whole paper, not just the title block.
- No author names, affiliations, acknowledgements, funding/grant numbers, or ORCIDs.
- No "in our previous work [X], we..." phrasing that de-anonymizes by self-reference; cite your own prior papers in the third person.
- No identifying system names, internal dataset names, institutional URLs, or repository links that resolve to a named account.
- Scrub figures, plots, PDF metadata, and any embedded file paths.
The 10-page all-inclusive cap
The single hardest ICDM formatting fact: 10 pages in IEEE two-column format, including the bibliography and any appendices. There is no separate reference budget and no separate appendix budget. Over-length papers are rejected without review.
% ICDM IEEE two-column setting (verify against the current track call)
\documentclass[conference]{IEEEtran}
% Everything below counts toward the 10-page cap: body, references, appendix.
% Do NOT shrink margins, fonts, or \baselineskip to reclaim space; IEEE
% proceedings checks and chairs detect a modified template.
% Plan the appendix as a first-class competitor for the same 10 pages as the body.- Content, references, and appendix together must end by page 10; if it does not fit, cut scope or move detail to an external anonymized repository, never squeeze the template.
- Reference the code/data repository inside the PDF, anonymized: because ICDM traditionally offers no rebuttal, a repository not cited at submission is invisible to reviewers for the whole cycle.
Show full SKILL.md (279 more words)Show less
Desk-level and severity table
| Trigger | Track affected | Severity | Fixable after deadline? |
|---|---|---|---|
| Over 10 pages (incl. refs + appendix) | Both | Rejected without review | No |
| Identity leak in body, figure, metadata, or repo | Research | Triple-blind violation | No |
| Modified IEEE template | Both | Desk-level / chair flag | No |
| Same paper in Research and Applied | Both | Rejection of both | No |
| Repository link absent from PDF | Both | Not fatal, but unrepairable without rebuttal | No |
| Wrong track for the contribution type | Both | Hostile review, mis-fit | Only before deadline |
Final-week sequence
- Freeze the track choice and confirm the anonymity regime it implies.
- Rebuild the PDF from a clean
IEEEtrancheckout; measure to the bottom of page 10 with references and appendix included. - Run the triple-blind sweep against the list above (Research Track): names, self-cites, system names, metadata, repo account.
- Export a fresh anonymized repository with no git history and no institutional paths; cite it in the body.
- Register the abstract early in the week; upload the paper with hours, not minutes, of AoE margin.
Vignette: a paper that lost a page to its own bibliography
A graph-mining team writes a tight 9.5-page body and adds a two-page appendix of proofs, forgetting that at ICDM the references (1.5 pages) and the appendix both live inside the 10-page cap. The compiled PDF is 12 pages — an automatic no-review reject. The fix is not cosmetic: they promote one proof sketch to the body, move the full proof and extra tables to the cited anonymized repository, and trim the related-work prose. The lesson: at ICDM, budget the appendix and references against the body from the first outline, because there is no separate allowance to grow into.
Output format
[ICDM readiness] Ready / Needs fixes / Not ready
[Track x anonymity] Research(triple-blind) | Applied(single-blind) | Blue Sky
[Page check] <= 10 pages incl. refs + appendix: pass / fail
[Anonymity] triple-blind sweep clean / leaks found (Research only)
[Artifact visibility] repo cited in PDF: yes / no
[Fix order] <ordered fixes before the AoE deadline>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in ICDM-Skills/skills/icdm-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icdm Submission next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Icdm Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Icdm Submission
What does Icdm Submission do?
A skill your agent uses when auditing an ICDM (IEEE International Conference on Data Mining) submission for readiness, covering Research-vs-Applied track choice and its anonymity regime, the…. Icdm Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Icdm Submission?
Icdm Submission fits situations like: 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.
How do I install Icdm Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-submission -a claude-code`. Or copy the skill folder (ICDM-Skills/skills/icdm-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icdm-submission in your project. Claude Code loads it when a task matches its description.
How do I install Icdm Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-submission -a codex`. Or copy the skill folder (ICDM-Skills/skills/icdm-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icdm-submission in your project. Codex loads it when a task matches its description.
Can I use Icdm Submission in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-submission -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/icdm-submission, .gemini/skills/icdm-submission, .github/skills/icdm-submission and .opencode/skills/icdm-submission in your project.
What does Icdm Submission need to run?
SKILL.md names no scripts, command-line tools or credentials: Icdm Submission is instructions for the agent only.
Does Icdm Submission access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Icdm Submission safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Icdm Submission use?
Icdm Submission is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Icdm Submission use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Icdm Submission?
Skills that share tags, products or a category with Icdm Submission: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icdm Submission?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.