uist-related-work
Use when positioning a UIST submission against prior art — organizing by capability delta rather than paper lists, covering the technique lineage, toolkit ancestry, and commercial systems reviewers know, citing your own work in the third person, and verifying venue attribution through the ACM DL and dblp.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-related-work --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 Related Work At UIST, related work is a **novelty proof**, not a literature survey. The section exists to establish that no prior system delivers your capability, and its jury includes people who built the prior systems. Precision about what neighbors can and cannot do is therefore worth more than coverage breadth — and misdescribing a reviewer's own system is the fastest way to earn a hostile expert review. ## Organize by capability, not by paper Structure subsections around the dimensions on which your artifact differs, and end each with an explicit delta sentence: ```text WEAK: "Several systems have explored on-skin input [4,9,12]. Others used acoustic sensing [7,15]. We also use acoustic sensing." STRONG: "Prior on-skin input systems localize touches on the forearm [4,9] or hand [12], but all require instrumentation of the touching finger. Acoustic approaches remove finger instrumentation [7,15] yet resolve only 4-6 discrete locations. Our contribution is continuous 2D localization with no finger instrumentation." ``` A comparison table (rows: closest systems; columns: the 3-5 capability dimensions) is often the strongest half-page in the paper — but every cell about som
- Organize by capability, not by paper
- The three lineages to cover
- Where to search, and how to verify
- Building the comparison table without libel
- Anonymization interacts with self-citation
- Timing note for the live cycle
- Output format
What does the uist-related-work skill do?
Use when positioning a UIST submission against prior art — organizing by capability delta rather than paper lists, covering the technique lineage, toolkit ancestry, and commercial systems reviewers know, citing your own work in the third person, and verifying venue attribution through the ACM DL and dblp.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-related-work --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.