Individual skill

uist-camera-ready

Use when converting a conditional UIST acceptance into a published paper — delivering the rebuttal-promised changes by the July deadline, working the ACM TAPS pipeline with alt text for every figure and table, de-anonymizing correctly, finalizing the video figure, and preparing the Detroit talk and demo.

UIST-Skills/skills/uist-camera-ready/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# UIST Camera-Ready

A UIST acceptance is conditional: the June 27 notification (2026 cycle, verified
2026-07-08) accepts the paper *as amended by your rebuttal*, and the July 24
camera-ready is where those amendments come due. This phase has three workstreams —
the contractual edits, the ACM production pipeline with its accessibility
requirements, and conference logistics — and they share four weeks.

## Workstream 1: deliver the contract

Reconstruct the promise ledger from your rebuttal (see `uist-author-response`) and
the meta-review or condition list in the notification:

- Make each promised change where you said you would make it, and keep a diff-notes
Back to top