A skill your agent uses when positioning an ICLR paper against prior work, concurrent OpenReview submissions, arXiv papers, benchmark lineages, and adjacent learning-representation claims.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-related-work --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/ICLR-Skills/skills/iclr-related-work .claude/skills/iclr-related-work && 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 "iclr-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-related-work into .claude/skills/iclr-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-related-work", 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/ICLR-Skills/skills/iclr-related-workType 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 iclr-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-related-work --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/ICLR-Skills/skills/iclr-related-work .agents/skills/iclr-related-work && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "iclr-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-related-work into .agents/skills/iclr-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-related-work", 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 iclr-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-related-work --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/ICLR-Skills/skills/iclr-related-work .cursor/skills/iclr-related-work && 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 "iclr-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-related-work into .cursor/skills/iclr-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-related-work", 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 ICLR-Skills/skills/iclr-related-work--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 iclr-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-related-work --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/ICLR-Skills/skills/iclr-related-work .gemini/skills/iclr-related-work && 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 "iclr-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-related-work into .gemini/skills/iclr-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-related-work", 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 iclr-related-workInstalls 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 iclr-related-work -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/ICLR-Skills/skills/iclr-related-work .github/skills/iclr-related-work && 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 "iclr-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-related-work into .github/skills/iclr-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-related-work", 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 iclr-related-work -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 iclr-related-work --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/ICLR-Skills/skills/iclr-related-work .opencode/skills/iclr-related-work && 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 "iclr-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-related-work into .opencode/skills/iclr-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-related-work", 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.
iclr-related-workA skill your agent uses when positioning an ICLR paper against prior work, concurrent OpenReview submissions, arXiv papers, benchmark lineages, and adjacent learning-representation claims.
Iclr Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an ICLR paper against prior work, concurrent OpenReview submissions, arXiv papers, benchmark lineages, and adjacent learning-representation claims. Use when a reviewer cites a paper you missed, when a public comment disputes your novelty, or when separating "shares a component with" from "solves the same representation-learning problem" so the claim survives permanent public scrutiny.
Its SKILL.md is about 1.6k 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, covering Literature review and Positioning and messaging. It works with arXiv. 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.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Iclr Related Work loads about 1.6k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 717 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.
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.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 717 words, ~1,589 tokens.
.claude/skills/iclr-related-work/SKILL.md (or your agent's skills folder).Use this to make the novelty claim robust under ICLR review. ICLR reviewers often know recent OpenReview, arXiv, and workshop work, so the related-work strategy must survive public comparison.
For each likely "this is just X" comparison, classify the relationship before writing prose.
| Relationship to prior work | Related-work action | Evidence needed |
|---|---|---|
| Same problem, same method family | Treat as a direct baseline, not a citation footnote | head-to-head result, ablation, or theory delta |
| Same component, different objective | Explain the objective and representation change | loss/objective statement plus experiment tied to the claimed change |
| Same benchmark, different question | Explain what the benchmark now tests | metric interpretation, split/regime difference, or stress test |
| Same claim, weaker evidence | Be precise and generous; do not imply priority without proof | dated citation plus the stronger evidence axis |
| Concurrent OpenReview/arXiv work | Cite and scope it without overclaiming precedence | date, venue/status, and one-sentence distinction |
If the paper cannot name the closest work and the difference axis, mark novelty risk high and
route to iclr-experiments before polishing prose.
Build the novelty claim as:
Prior work can <capability under stated conditions>.
It does not <specific missing capability or explanation>.
This paper shows <new mechanism/result/evidence>, under <scope>.
The claim is supported by <theory/experiment/artifact>.Add a claim ledger underneath the paragraph:
| Claim in paper | Closest work | Difference axis | Required support | Status |
|---|---|---|---|---|
| new capability | paper/system X | problem / assumption / method / evidence / scale / theory / artifact | experiment, proof, artifact, or dataset card | ready / weak / missing |
Any row marked weak or missing must either be softened in the abstract/introduction or backed by a new result. Do not leave the strongest novelty claim supported only by wording.
ICLR reviewers and even community members can post a "this is just X" comment that stays online next to your paper forever. The defense is a precise difference axis, decided before submission.
| "Just like X" objection | Robust ICLR response | Fragile response |
|---|---|---|
| Same architecture | Different objective and what it changes representationally | "Ours is bigger" |
| Same benchmark | Different question the benchmark now answers | Higher number only |
| Concurrent arXiv preprint | Dated, scoped distinction, cited generously | Ignoring it and hoping |
| Reuses a known loss | The new analysis or regime where it behaves differently | Renaming the loss |
A submission proposes a masked-prediction objective for time-series transformers. A reviewer links a recent arXiv paper with a similar mask. Rather than dispute priority, the authors add a paragraph: the prior work masks contiguous spans for forecasting, while this paper masks frequency components and shows the representation transfers across sampling rates, supported by a transfer ablation. The difference axis is "what is masked and which invariance it buys," not "we got there first."
When a reviewer or community comment challenges novelty, respond in a way that improves the permanent OpenReview record:
Escalate from prose to experiments when the difference axis is empirical. If the response would say "we believe our method is different" without a supporting result, novelty risk stays high.
[Closest work] <paper/system/benchmark>
[Difference axis] problem / assumption / method / evidence / scale / theory / artifact
[Claim ledger] <claim -> closest work -> support status>
[Must-cite items] <recent OpenReview/arXiv/ICLR-adjacent work>
[Novelty risk] low / medium / high
[Public response] acknowledgement + overlap + difference + manuscript change
[Revision text] <concise related-work paragraph or bullet>© 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
Just SKILL.md in ICLR-Skills/skills/iclr-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Iclr Related Work 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 |
|---|---|---|---|---|---|---|
| Iclr Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Ijcai Related Workfranklee16/academic-research-skills | 223 | 1 repos | ~427 | Automated safety check: Pass | None | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Systematic Literature Review Builderbytedance/deer-flow | 84k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Paper Research on arXivXiaomiMiMo/MiMo-Code | 14k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Literature Review AgentAr9av/PaperOrchestra | 679 | 1 repos | ~5.2k | Automated safety check: Pass | Custom licence |
franklee16/academic-research-skills
A skill your agent uses when positioning an IJCAI or IJCAI-ECAI submission against archival AI literature, arXiv preprints, workshop papers, prior rejected versions, dual-submission rules, shortened…
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
bytedance/deer-flow
Searches arXiv across many papers on one topic, extracts each paper's methodology and findings in parallel, and synthesizes a cited literature review.
XiaomiMiMo/MiMo-Code
Searches arXiv, fetches metadata, generates BibTeX, downloads PDFs and finds citations and related papers using a bundled Python script.
Ar9av/PaperOrchestra
Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). An agent skill from Ar9av/PaperOrchestra.
blazickjp/arxiv-mcp-server
A skill your agent uses when finding, comparing, reading, or monitoring arXiv papers, including requests for abstracts, citation graphs, original LaTeX, section-level technical details, or…
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…
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…
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…
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…
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…
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…
Works with
Categories
A skill your agent uses when positioning an ICLR paper against prior work, concurrent OpenReview submissions, arXiv papers, benchmark lineages, and adjacent learning-representation claims. Iclr Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an ICLR paper against prior work, concurrent OpenReview submissions, arXiv papers, benchmark lineages, and adjacent learning-representation claims.
Iclr Related Work fits situations like: positioning an ICLR paper against prior work; concurrent OpenReview submissions; benchmark lineages; adjacent learning-representation claims.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-related-work -a claude-code`. Or copy the skill folder (ICLR-Skills/skills/iclr-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/iclr-related-work in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-related-work -a codex`. Or copy the skill folder (ICLR-Skills/skills/iclr-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/iclr-related-work in your project. Codex loads it when a task matches its description.
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 iclr-related-work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/iclr-related-work, .gemini/skills/iclr-related-work, .github/skills/iclr-related-work and .opencode/skills/iclr-related-work in your project.
SKILL.md names no scripts, command-line tools or credentials: Iclr Related Work is instructions for the agent only.
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.
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.
Iclr Related Work is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Iclr Related Work: Ijcai Related Work (franklee16/academic-research-skills, 223 stars), Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Systematic Literature Review Builder (bytedance/deer-flow, 84k stars) and Paper Research on arXiv (XiaomiMiMo/MiMo-Code, 14k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.
