uist-review-process
Use when interpreting the UIST review pipeline — anonymous PC-plus-external review of papers and videos, the rebuttal's role, PC-meeting decisions, conditional acceptance mechanics, reading systems-reviewer psychology, and choosing the demo/poster fallback or resubmission path after a rejection.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-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.
# UIST Review Process Understanding how UIST decides is mostly understanding who decides: a program committee of people who build interactive systems, supported by external reviewers drawn from the same community, converging in discussion and a PC meeting. The venue is single-track and relatively intimate — the person reviewing your haptics paper probably built a haptics device. The pipeline facts below are the 2026 cycle's (verified 2026-07-08); exact committee mechanics beyond the published dates are 待核实 each year. ## The 2026 pipeline | Stage | 2026 timing | What happens to your paper | |---|---|---| | Submission closes | Mar 31 | PDF + video + supplement enter PCS | | Review period | April-May | PC members and externals review paper *and* video | | Rebuttal | May 28 - Jun 5 | Authors respond in ≤ 5,000 characters | | Discussion + PC meeting | June | Recommendations formed from submission, rebuttal, reviews, and reviewer/PC discussion | | Notification | Jun 27 | Accept (conditional), or reject | | Camera-ready | Jul 24 | Conditions from the rebuttal must be delivered | Two structural notes: the decision explicitly weighs the rebuttal and the inter-reviewer discussion, so the reb
- The 2026 pipeline
- How systems reviewers actually read
- Reading your reviews
- Discussion dynamics in a small committee
- Calibrating expectations by decision class
- After rejection: the three exits
- Confidentiality and conduct
- Output format
What does the uist-review-process skill do?
Use when interpreting the UIST review pipeline — anonymous PC-plus-external review of papers and videos, the rebuttal's role, PC-meeting decisions, conditional acceptance mechanics, reading systems-reviewer psychology, and choosing the demo/poster fallback or resubmission path after a rejection.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-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.