Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when reasoning about the ICDM (IEEE International Conference on Data Mining) review machinery - the triple-blind mechanics, the Accept / Accept-as-Short / Reject outcome…
Install Icdm Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdm-review-process --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-review-process .claude/skills/icdm-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDM-Skills/skills/icdm-review-process into .claude/skills/icdm-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdm-review-process", 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-review-processType 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-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdm-review-process --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-review-process .agents/skills/icdm-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDM-Skills/skills/icdm-review-process into .agents/skills/icdm-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdm-review-process", 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-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdm-review-process --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-review-process .cursor/skills/icdm-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDM-Skills/skills/icdm-review-process into .cursor/skills/icdm-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdm-review-process", 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-review-process--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-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdm-review-process --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-review-process .gemini/skills/icdm-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDM-Skills/skills/icdm-review-process into .gemini/skills/icdm-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdm-review-process", 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-review-processInstalls 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-review-process -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-review-process .github/skills/icdm-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDM-Skills/skills/icdm-review-process into .github/skills/icdm-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdm-review-process", 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-review-process -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-review-process --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-review-process .opencode/skills/icdm-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDM-Skills/skills/icdm-review-process into .opencode/skills/icdm-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdm-review-process", 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-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 441 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about the ICDM (IEEE International Conference on Data Mining) review machinery - the triple-blind mechanics, the Accept / Accept-as-Short / Reject outcome…
- Reasoning about the ICDM (IEEE International Conference on Data Mining) review machinery - the triple-blind mechanics
- SKILL.md covers Triple-blind mechanics, The outcome space, The reviewer pool and The no-rebuttal posture, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The Accept / Accept-as-Short / Reject outcome space
What it does
Icdm Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about the ICDM (IEEE International Conference on Data Mining) review machinery - the triple-blind mechanics, the Accept / Accept-as-Short / Reject outcome space, the mixed data-mining reviewer pool, PC Co-Chair decision-making, the traditional no-rebuttal posture, and how to read an ICDM decision packet.
Its SKILL.md is about 1.1k 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
- Reasoning about the ICDM (IEEE International Conference on Data Mining) review machinery - the triple-blind mechanics
- The Accept / Accept-as-Short / Reject outcome space
- The mixed data-mining reviewer pool
- PC Co-Chair decision-making
Example prompts
- “/icdm-review-process”
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.
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 Review Process loads about 1.1k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 441 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). 441 words, ~1,111 tokens.
Download SKILL.mdSave it as
.claude/skills/icdm-review-process/SKILL.md (or your agent's skills folder).- name
- icdm-review-process
- description
- Use when reasoning about the ICDM (IEEE International Conference on Data Mining) review machinery - the triple-blind mechanics, the Accept / Accept-as-Short / Reject outcome space, the mixed data-mining reviewer pool, PC Co-Chair decision-making, the traditional no-rebuttal posture, and how to read an ICDM decision packet.
ICDM Review Process
Understand how ICDM decisions are actually made, so you can write for the process and read the outcome correctly. ICDM's Research Track runs a triple-blind review, has a distinctive short-paper outcome, and traditionally offers no author rebuttal — a very different shape from OpenReview venues with public discussion.
Triple-blind mechanics
- Author identities and referee identities are both concealed. Since 2011, referee names are hidden even from each other during discussion; only the PC Co-Chairs know who is who.
- Author names are disclosed only after ranking and acceptance are finalized — so nothing in the review can be swayed by who you are, for better or worse.
- Practical consequence: the paper is judged purely on the anonymized PDF and its cited anonymized artifact. Write for a reviewer who knows nothing about you.
The outcome space
| Outcome | What it means | Your move |
|---|---|---|
| Accept (regular) | In as a full paper | Camera-ready at full length |
| Accept as Short | Contribution valued, but scoped/evidenced for short length | Compress to the short camera-ready (see icdm-camera-ready) |
| Reject | Not accepted this edition | Revise and route (SDM/CIKM/KDD next window) |
The Accept-as-Short outcome is ICDM's signature: a full submission can be offered acceptance at
short length rather than rejected outright. Plan for it (see icdm-workflow), because it arrives
with the notification and a compressed camera-ready deadline.
The reviewer pool
- ICDM reviewers are data-mining specialists: algorithmic, graph, temporal, and applied-mining researchers. They reward a named mechanism, careful baselines, and defensible discovery, and they punish leaderboard-only novelty and un-checkable claims.
- The Applied Track (single-blind, new in 2026) draws a more application-oriented pool that weights deployment and measured real-world impact.
- Expertise varies within a paper's reviews; the self-contained body (no rebuttal to clarify) is your defense against a reviewer who misreads the setup.
Show full SKILL.md (151 more words)Show less
The no-rebuttal posture
- Historically ICDM has no author-response window; whether the current edition adds one is
待核实 (see
icdm-author-response). Assume none when planning. - This makes the submitted PDF and cited artifact your only argument. Every likely reviewer question — baseline fairness, leakage, variance, scale — must be pre-answered on the page.
- A weakness "left for the rebuttal" is a weakness left unaddressed.
Reading a decision packet
1. Find the decision line: Accept / Accept-as-Short / Reject.
2. If Accept-as-Short, read reviews for WHAT to cut vs keep - the mechanism stays.
3. Cluster review concerns: correctness, baselines, novelty, scale, clarity, validity.
4. Separate factual misreadings (fixable in camera-ready framing) from real gaps
(need new experiments -> next venue).
5. Note anything the reviewers could not see because it was missing from the PDF/artifact;
that is your no-rebuttal lesson for next time.Vignette: reading an Accept-as-Short correctly
A paper comes back "accepted as a short paper": reviewers found the mechanism novel but felt one of three experiments was under-developed. The wrong read is disappointment; the right read is a scoping instruction. The team keeps the mechanism and its strongest experiment in the short body, moves the two weaker experiments and all protocol detail to the cited repository, and ships a tight short paper on time — the contribution is preserved, just at the length reviewers judged it earned.
Output format
[Decision] Accept / Accept-as-Short / Reject
[Regime read] triple-blind (Research) / single-blind (Applied)
[Concern clusters] correctness / baselines / novelty / scale / clarity / validity
[Misreading vs gap] <which concerns are framing-fixable vs need new work>
[No-rebuttal lesson] <what was missing from PDF/artifact that reviewers needed>
[Next move] camera-ready / short-compression / revise-and-route© 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-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icdm Review Process 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 Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | 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 Review Process
What does Icdm Review Process do?
A skill your agent uses when reasoning about the ICDM (IEEE International Conference on Data Mining) review machinery - the triple-blind mechanics, the Accept / Accept-as-Short / Reject outcome…. Icdm Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about the ICDM (IEEE International Conference on Data Mining) review machinery - the triple-blind mechanics, the Accept / Accept-as-Short / Reject outcome space, the mixed data-mining reviewer pool, PC Co-Chair decision-making, the traditional no-rebuttal posture, and how to read an ICDM decision packet.
When should I use Icdm Review Process?
Icdm Review Process fits situations like: reasoning about the ICDM (IEEE International Conference on Data Mining) review machinery - the triple-blind mechanics; the Accept / Accept-as-Short / Reject outcome space; the mixed data-mining reviewer pool; PC Co-Chair decision-making.
How do I install Icdm Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-review-process -a claude-code`. Or copy the skill folder (ICDM-Skills/skills/icdm-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icdm-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Icdm Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-review-process -a codex`. Or copy the skill folder (ICDM-Skills/skills/icdm-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icdm-review-process in your project. Codex loads it when a task matches its description.
Can I use Icdm Review Process 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-review-process -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-review-process, .gemini/skills/icdm-review-process, .github/skills/icdm-review-process and .opencode/skills/icdm-review-process in your project.
What does Icdm Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Icdm Review Process is instructions for the agent only.
Does Icdm Review Process 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 Review Process 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 Review Process use?
Icdm Review Process 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 Review Process use?
About 1.1k tokens (SKILL.md is roughly 4.4k 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 Review Process?
Skills that share tags, products or a category with Icdm Review Process: 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 Review Process?
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.