Markdown Article Formatter
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
A skill your agent uses when organizing ICLR appendices, supplementary files, anonymous code/data, revised PDFs, private links, and discussion-period updates under OpenReview rules.
Install Iclr Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-supplementary --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-supplementary .claude/skills/iclr-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-supplementary into .claude/skills/iclr-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-supplementary", 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-supplementaryType 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-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-supplementary --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-supplementary .agents/skills/iclr-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-supplementary into .agents/skills/iclr-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-supplementary", 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-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-supplementary --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-supplementary .cursor/skills/iclr-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-supplementary into .cursor/skills/iclr-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-supplementary", 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-supplementary--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-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-supplementary --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-supplementary .gemini/skills/iclr-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-supplementary into .gemini/skills/iclr-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-supplementary", 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-supplementaryInstalls 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-supplementary -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-supplementary .github/skills/iclr-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-supplementary into .github/skills/iclr-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-supplementary", 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-supplementary -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-supplementary --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-supplementary .opencode/skills/iclr-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-supplementary into .opencode/skills/iclr-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-supplementary", 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
iclr-supplementary- GitHub stars
- 1.2k
- Token cost
- ~906 tokens
- SKILL.md length
- 400 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when organizing ICLR appendices, supplementary files, anonymous code/data, revised PDFs, private links, and discussion-period updates under OpenReview rules.
- Organizing ICLR appendices
- SKILL.md covers Structure, Anonymity and access, Main-text versus appendix… and Worked vignette, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Supplementary files
What it does
Iclr Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 910 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 Documents & Office. 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
- Organizing ICLR appendices
- Supplementary files
- Anonymous code/data
- Discussion-period updates under OpenReview rules
Example prompts
- “/iclr-supplementary”
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
Iclr Supplementary loads about 906 tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 400 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). 400 words, ~906 tokens.
Download SKILL.mdSave it as
.claude/skills/iclr-supplementary/SKILL.md (or your agent's skills folder).- name
- iclr-supplementary
- description
- 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.
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 or privacy constraint and provide a smaller reproducibility substitute.
Main-text versus appendix placement
ICLR's single-track format means the main PDF carries the argument and appendices come after references with generous room. The risk is burying decisive evidence where a time-pressed reviewer never looks, while padding the appendix with material that proves nothing.
| Content | Belongs in | Why |
|---|---|---|
| Central claim and its key result | Main text | Reviewers may not open the appendix |
| Full proof / extended derivation | Appendix | Needed for rigor, not for the headline |
| Hyperparameters, model/dataset cards | Appendix | Reference material, not argument |
| Code, logs, large tables, checkpoints | Supplementary ZIP | Too big or interactive for the PDF |
| Decisive ablation a claim depends on | Main text | Moving it weakens the narrative |
Show full SKILL.md (113 more words)Show less
Worked vignette
A generative-model paper hides its only fairness-of-comparison ablation in Appendix G, so a reviewer concludes the headline gain is unsupported. The fix: promote a compact version into the main text near the claim, leave the full grid in the appendix, and add an appendix map. During discussion the authors upload a revision and label the changelog so the relocation is obvious.
Reviewer-pushback patterns
- "Key evidence is buried." Promote it; an appendix map is not a substitute for main-text placement.
- "Cannot tell what changed in the revision." Add a dated changelog at the top of the revised PDF.
- "Supplement leaks identity." Re-check file paths, license headers, and remotes before upload.
Output format
[Supplement plan] PDF appendix / ZIP / anonymous repo / private link / no supplement
[Main-text dependencies] <claims that must move back into main text>
[Reviewer navigation] <appendix map and file names>
[Anonymity risks] <paths, metadata, links, licenses>
[Discussion update note] <short changelog if revised>© 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 ICLR-Skills/skills/iclr-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Iclr Supplementary 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 Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~906 | Automated safety check: Pass | MIT | |
| Markdown Article FormatterJimLiu/baoyu-skills | 27k | 6 repos | ~3.5k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Obsidian MarkdownAtmosphere/atmosphere | 3.8k | 20 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| DOCXrvdbreemen/OTGW-firmware | 207 | 33 repos | ~4.3k | Automated safety check: Pass | Proprietary | |
| Word Document Reader and WriterHKUDS/DeepTutor | 41k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Obsidian Markdown
Atmosphere/atmosphere
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.
DOCX
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
Word Document Reader and Writer
HKUDS/DeepTutor
Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.
Crossposting
wasp-lang/wasp
Crosspost Wasp blog articles (MDX) to DEV.to and Medium. An agent skill from wasp-lang/wasp.
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 Iclr Supplementary
What does Iclr Supplementary do?
A skill your agent uses when organizing ICLR appendices, supplementary files, anonymous code/data, revised PDFs, private links, and discussion-period updates under OpenReview rules. Iclr Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when organizing ICLR appendices, supplementary files, anonymous code/data, revised PDFs, private links, and discussion-period updates under OpenReview rules.
When should I use Iclr Supplementary?
Iclr Supplementary fits situations like: organizing ICLR appendices; supplementary files; anonymous code/data; discussion-period updates under OpenReview rules.
How do I install Iclr Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-supplementary -a claude-code`. Or copy the skill folder (ICLR-Skills/skills/iclr-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/iclr-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Iclr Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-supplementary -a codex`. Or copy the skill folder (ICLR-Skills/skills/iclr-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/iclr-supplementary in your project. Codex loads it when a task matches its description.
Can I use Iclr Supplementary 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 iclr-supplementary -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-supplementary, .gemini/skills/iclr-supplementary, .github/skills/iclr-supplementary and .opencode/skills/iclr-supplementary in your project.
What does Iclr Supplementary need to run?
SKILL.md names no scripts, command-line tools or credentials: Iclr Supplementary is instructions for the agent only.
Does Iclr Supplementary 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 Iclr Supplementary 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 Iclr Supplementary use?
Iclr Supplementary 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 Iclr Supplementary use?
About 906 tokens (SKILL.md is roughly 3.6k 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 Iclr Supplementary?
Skills that share tags, products or a category with Iclr Supplementary: Markdown Article Formatter (JimLiu/baoyu-skills, 27k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and DOCX (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Iclr Supplementary?
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.