uai-review-process
Use when reasoning about UAI peer review on OpenReview, including bidding, double-blind evaluation against the correctness, novelty, backing, and clarity criteria, the author-response window, the reviewer-and-area-chair discussion that follows it, decision timing, spotlight versus poster outcomes, and PMLR publication of accepted papers.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-review-process --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 Review Process Use this to model what happens to a UAI submission after upload, and to time author effort where it changes outcomes. Stage dates below are the published 2026 pipeline (verified 2026-07-08); the shape tends to persist across cycles, the dates never do. ## The 2026 pipeline, stage by stage | Stage | 2026 window | Who acts | Author leverage | |---|---|---|---| | Submission closes | Feb 25 (AoE) | Authors | Total — last moment anything enters the record | | Bidding | Mar 2–9 | SACs, ACs, reviewers | Indirect: title, abstract, subject areas drive matching | | Review writing | Mar 21 – Apr 11 | Reviewers | None — the paper speaks alone | | Author response | Apr 23 – May 2 | Authors | High on misreadings; low on true weaknesses | | Reviewer–AC discussion | May 2–8 | Reviewers + ACs | Only via the response already filed | | Notification | Jun 1 | Program Chairs | None | | Camera-ready | Jul 27 | Authors | Presentation of accepted content | | Conference | Aug 17–21 | Everyone | Talks, posters, corridor conversations — reputation, not decision | Note the gaps: reviews are written weeks before authors see them, and the decisive reviewer–AC conversation happens after auth
- The 2026 pipeline, stage by stage
- Matching is an author-controlled variable
- Who reviews at UAI
- Scale and format context
- Reading a UAI decision
- What authors see versus what actually happens
- Signals to log for the next cycle
- If the process misfires
- Confidentiality and conduct boundaries
- Output format
What does the uai-review-process skill do?
Use when reasoning about UAI peer review on OpenReview, including bidding, double-blind evaluation against the correctness, novelty, backing, and clarity criteria, the author-response window, the reviewer-and-area-chair discussion that follows it, decision timing, spotlight versus poster outcomes, and PMLR publication of accepted papers.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-review-process --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.