iclr-submission
Use when auditing an ICLR main-conference submission for OpenReview readiness, double-blind anonymity, page limits, reciprocal reviewing, LLM-use disclosure, dual-submission policy, supplementary material, and desk-reject risk.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-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.
# ICLR Submission Use this for an ICLR main-conference submission audit. Reopen the current CFP, Author Guide, OpenReview submission form, template, Code of Ethics, Code of Conduct, and LLM policy before giving deadline-ready advice. ## Submission audit - Confirm the target is the ICLR main conference, not a workshop, Tiny Paper, blog, affinity event, or later publication track. - Check that all authors have complete OpenReview profiles and that the author list follows the current freeze/change windows. - Verify that the abstract is substantive and non-duplicative before the abstract deadline; do not rely on a placeholder. - Confirm use of the current ICLR LaTeX template and current page-limit rules. In 2026, submissions used 9 pages of main text, references outside the limit, and appendices after references. - Inspect anonymity in the PDF, appendices, supplementary ZIP, code, data, demos, links, repository metadata, comments, acknowledgments, and file names. - Confirm reciprocal-reviewing compliance for the author team unless the current cycle grants an explicit exemption. - Complete any LLM-use disclosure truthfully. Hidden prompt injection, hallucinated citations, or undisclosed
- Submission audit
- Desk-reject and integrity risks
- Desk-reject triage table
- Worked vignette
- Reviewer-pushback patterns
- Output format
What does the iclr-submission skill do?
Use when auditing an ICLR main-conference submission for OpenReview readiness, double-blind anonymity, page limits, reciprocal reviewing, LLM-use disclosure, dual-submission policy, supplementary material, and desk-reject risk.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-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.