uist-author-response
Use when writing the UIST rebuttal — budgeting the 5,000-character self-contained response, prioritizing factual corrections and novelty defenses over taste disputes, promising only camera-ready changes you can deliver, and writing for the PC discussion that follows rather than for the reviewers alone.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-author-response --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 Author Response The UIST rebuttal is small, plain-text, and consequential: 5,000 characters, self-contained, written in about a week (May 28 - June 5 in the verified 2026 cycle), and explicitly listed among the inputs to the accept/reject recommendation. Its second life matters more than its first: because acceptances are conditional on "changes described in the rebuttal," this document becomes the **contract for your camera-ready**. Draft it as both an argument and a promise you must keep by July 24. ## Budgeting 5,000 characters That is roughly 700-800 words — three to five points argued well. Spend by expected value, not by emotional temperature: | Priority | Point type | Why it pays | |---|---|---| | 1 | Factual error in a review | Cheap to correct, moves discussion immediately | | 2 | Novelty challenge ("X does this") | A capability-delta answer can flip a score | | 3 | Direct reviewer questions | Unanswered questions read as concessions | | 4 | Evidence gap where evidence exists | Report the number; it was measured, not new | | 5 | Scope concession | Narrowing a claim can defuse a rejection rationale | | — | Taste disagreements | Skip; acknowledge in one clause if at a
- Budgeting 5,000 characters
- Structure that survives skimming
- A point, done badly and well
- Working the window
- What a rebuttal cannot do
- Deciding whether to rebut at all
- The promise ledger
- Output format
What does the uist-author-response skill do?
Use when writing the UIST rebuttal — budgeting the 5,000-character self-contained response, prioritizing factual corrections and novelty defenses over taste disputes, promising only camera-ready changes you can deliver, and writing for the PC discussion that follows rather than for the reviewers alone.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-author-response --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.