iclr-supplementary
Use when organizing ICLR appendices, supplementary files, anonymous code/data, revised PDFs, private links, and discussion-period updates under OpenReview rules. Use when deciding what stays in the main text versus the appendix, how to label a discussion-period revision so reviewers find changes fast, or how to package anonymous artifacts that remain part of the permanent public record after acceptance.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-supplementary --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 Supplementary Use this when deciding what belongs in the main PDF, appendix, supplementary files, or private discussion-period links. The goal is to make extra evidence easy to find without hiding the paper's core argument outside the main text. ## Structure - Keep central method, claims, and minimum evidence in the main text. - Put derivations, extended ablations, robustness, extra qualitative examples, hyperparameters, model cards, dataset cards, and ethics details in the appendix. - Use supplementary files for code, data, large tables, logs, demos, and artifacts that do not fit cleanly in the PDF. - Include a one-page appendix map at the start when the appendix is long. - Label discussion-period revisions explicitly so reviewers can find changes quickly. ## Anonymity and access - Remove author names, institutions, usernames, Git remotes, file paths, cloud buckets, and license headers that identify the team. - Avoid links that reveal visitors or owner accounts. Prefer anonymized repositories, static files, or private OpenReview-visible links permitted by the current guide. - Make supplementary filenames descriptive but neutral. - If code cannot be released, state the legal
- Structure
- Anonymity and access
- Main-text versus appendix placement
- Worked vignette
- Reviewer-pushback patterns
- Output format
What does the iclr-supplementary skill do?
Use when organizing ICLR appendices, supplementary files, anonymous code/data, revised PDFs, private links, and discussion-period updates under OpenReview rules. Use when deciding what stays in the main text versus the appendix, how to label a discussion-period revision so reviewers find changes fast, or how to package anonymous artifacts that remain part of the permanent public record after acceptance.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-supplementary --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.