uai-submission
Use when auditing a UAI submission for OpenReview readiness, covering the February paper deadline, the 8-page main part with unlimited appendices in one PDF, the 15 MB file cap, the optional 50 MB supplementary ZIP, double-blind rules, the reviewer-volunteer agreement, dual-submission checks, and desk-reject triage before upload.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-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.
# UAI Submission Run this audit before uploading to the UAI OpenReview site. Every number below was read from the UAI 2026 pages on 2026-07-08; treat them as one cycle's snapshot and reopen the current Call for Papers and submission instructions at auai.org before acting on any of them. ## What the 2026 cycle required UAI packages the whole submission into a single PDF, which changes how deadline week feels compared with venues that collect a separate supplement later: - Submission ran on OpenReview (the `auai.org/UAI/2026/Conference` group), open from January 25, 2026 and closing February 25, 2026, 23:59 Anywhere on Earth. No separate abstract-registration deadline was posted for 2026 — do not assume one exists, and do not assume one will never appear. - The main part of the manuscript could not exceed 8 pages. References and appendices (proofs, experimental protocols, extra detail) were unlimited but had to follow the main part **inside the same PDF**. - The PDF itself was capped at 15 MB; an optional supplementary ZIP (source code, data) was capped at 50 MB. Reviewers were not required to look inside the ZIP. - Manuscripts had to use the UAI LaTeX template. - At least one author
- What the 2026 cycle required
- Anonymity sweep, UAI phrasing
- Desk-risk triage
- Ordering the final week
- Template discipline
- Claims the paper must survive
- OpenReview form, drafted before deadline day
- Cycle-volatile items — reverify every year
- Output format
Pre-upload mechanical checks on the single submission PDF and ZIP pdfinfo paper.pdf | grep -Ei 'author|creator' # metadata identity fields pdftotext paper.pdf - | grep -nEi 'github\.com|gitlab|acknowledg|grant no' | head du -h paper.pdf supplement.zip # 15 MB PDF / 50 MB ZIP caps unzip -l supplement.zip | grep -Ei '\.git/|DS_Store|/home/|users/' | head
What does the uai-submission skill do?
Use when auditing a UAI submission for OpenReview readiness, covering the February paper deadline, the 8-page main part with unlimited appendices in one PDF, the 15 MB file cap, the optional 50 MB supplementary ZIP, double-blind rules, the reviewer-volunteer agreement, dual-submission checks, and desk-reject triage before upload.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-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 984 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.