Neuroarxiv
UditAkhourii/neuroarxiv
Grounds a coding agent's architecture decisions in real arXiv prior art before it builds something new.
A skill your agent uses when positioning a UIST submission against prior art — organizing by capability delta rather than paper lists, covering the technique lineage, toolkit ancestry, and…
Install Uist Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-related-work --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/UIST-Skills/skills/uist-related-work .claude/skills/uist-related-work && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "uist-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-related-work into .claude/skills/uist-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-related-work", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-related-workType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-related-work --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/UIST-Skills/skills/uist-related-work .agents/skills/uist-related-work && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "uist-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-related-work into .agents/skills/uist-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-related-work", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-related-work --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/UIST-Skills/skills/uist-related-work .cursor/skills/uist-related-work && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "uist-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-related-work into .cursor/skills/uist-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-related-work", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path UIST-Skills/skills/uist-related-work--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-related-work --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/UIST-Skills/skills/uist-related-work .gemini/skills/uist-related-work && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "uist-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-related-work into .gemini/skills/uist-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-related-work", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-related-workInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-related-work -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/UIST-Skills/skills/uist-related-work .github/skills/uist-related-work && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "uist-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-related-work into .github/skills/uist-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-related-work", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-related-work -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-related-work --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/UIST-Skills/skills/uist-related-work .opencode/skills/uist-related-work && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "uist-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-related-work into .opencode/skills/uist-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-related-work", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
uist-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 658 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when positioning a UIST submission against prior art — organizing by capability delta rather than paper lists, covering the technique lineage, toolkit ancestry, and…
- Works in 4 steps: Choose dimensions from your claims, not… → Fill each competitor cell from their… → Include at least one dimension where a… → …
- Positioning a UIST submission against prior art — organizing by capability delta rather than paper lists
- SKILL.md covers Organize by capability, not by…, The three lineages to cover, Where to search, and how to… and Building the comparison table…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Uist Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Literature review and Intellectual property. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Positioning a UIST submission against prior art — organizing by capability delta rather than paper lists
- Covering the technique lineage
- Toolkit ancestry
- Commercial systems reviewers know
Example prompts
- “/uist-related-work”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Choose dimensions from your claims, not from your strengths — a table whose
- Fill each competitor cell from their paper's own text, with the section
- Include at least one dimension where a prior system beats yours (maturity,
- Re-check cells against later versions — a 2019 system may have gained the
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Uist Related Work loads about 1.5k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 658 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 658 words, ~1,500 tokens.
Download SKILL.mdSave it as
.claude/skills/uist-related-work/SKILL.md (or your agent's skills folder).- name
- uist-related-work
- description
- 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.
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:
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 someone else's system must be defensible from their paper's text.
The three lineages to cover
| Lineage | What reviewers check | Where authors slip |
|---|---|---|
| Technique lineage | The chain of prior techniques for the same user intent, across decades | Citing only the last 5 years; UIST's canon runs to the early 1990s |
| Toolkit/platform ancestry | Which abstractions you inherit vs invent | Claiming novelty for what a mature toolkit already provides |
| Commercial and open-source practice | Shipping products that already do a version of it | Ignoring the product every reviewer owns |
Commercial systems lack papers but not existence: cite documentation or teardowns and state the capability difference plainly. "No academic paper describes X" is not a novelty claim when X ships on a phone.
Where to search, and how to verify
- Sweep the UIST main proceedings first, then the adjunct proceedings — demos and posters establish prior art too, and a 2-page poster that showed your idea must be cited and differentiated, not hidden.
- Continue through the sibling venues in both directions: CHI, TEI, IMWUT, ISMAR, IUI, SUI, CSCW — UIST reviewers move through the same circuit.
- Verify every venue attribution against the ACM DL record or dblp before the camera-ready; "CHI 2019" citations that were actually UIST 2019 (or an adjunct demo, or an arXiv preprint) are noticed at this venue in particular.
- For canonical anchors, the Lasting Impact lineage in
../../resources/exemplars/library.mdis verified against DL/dblp records; follow the same recipe for anything you add.
Show full SKILL.md (305 more words)Show less
Building the comparison table without libel
The capability-comparison table is high-value and high-risk. A defensible build procedure:
- Choose dimensions from your claims, not from your strengths — a table whose columns are exactly where you win reads as rigged, and reviewers discount it.
- Fill each competitor cell from their paper's own text, with the section number kept in your notes; "not reported" is a legitimate cell value and more honest than an inferred "no."
- Include at least one dimension where a prior system beats yours (maturity, cost, resolution); the table gains credibility exactly there.
- Re-check cells against later versions — a 2019 system may have gained the capability in its authors' 2023 follow-up, and those authors review at UIST.
Table skeleton (rows = closest systems, cols = capability dimensions):
| finger-free | continuous 2D | on unmodified skin | latency reported
SystemA '19 | no | 4 sites | yes | not reported
SystemB '22 | yes | 1D slider | no (sleeve) | 23 ms
Ours | yes | yes ±2.1 mm | yes | 11 ms medianAnonymization interacts with self-citation
UIST's 2026 rules (verified 2026-07-08) are specific and unusual in one respect:
- Cite your own prior work in the third person with a full, non-redacted reference — do not write "[anonymized for review]", which both leaks that the cited work is yours and breaks the reviewer's ability to check the delta.
- If a prior submission of yours overlaps heavily with this one, attach an anonymized copy of it as supplementary material so reviewers can judge the overlap themselves.
- The delta over your own prior system gets the same explicit treatment as anyone else's — self-succession without a stated capability difference reads as salami-slicing.
Timing note for the live cycle
Reviews for UIST 2026 papers are in (notification June 27, 2026). If you are
repositioning after rejection, mine the reviews for missed prior art before choosing
the next venue: an expert pointing at a system you did not cite is the cheapest
related-work audit you will ever get. For camera-ready papers, the +10% page
allowance is often best spent making the comparison table honest about points the
rebuttal conceded (see uist-camera-ready).
Output format
[Novelty frame] <the capability delta in one sentence>
[Nearest neighbors] <3-5 systems + the dimension separating each>
[Lineage gaps] technique / toolkit / commercial — which is thin
[Attribution check] verified via DL-dblp / pending
[Self-citation risk] third-person compliant / overlap attachment needed / clean© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in UIST-Skills/skills/uist-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Uist Related Work next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Uist Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| NeuroarxivUditAkhourii/neuroarxiv | 433 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Deltasci Groundboheling/deltasci | 144 | — | ~2k | Automated safety check: Pass | MIT | |
| Sciatlas Idea Groundingzjunlp/SciAtlas | 160 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Comm Lit Reviewbrycewang-stanford/Auto-Empirical-Research-Skills | 4.6k | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Mechanical Engineering Researchccplugins/awesome-claude-code-plugins | 970 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Deltasci Ground
boheling/deltasci
The grounding layer for AI-assisted research: scan the real prior art around an idea, gauge how crowded or open the gap is, and verify every citation against the source of truth.
Sciatlas Idea Grounding
zjunlp/SciAtlas
Use only SciAtlas search-papers to take a novice user from zero setup to final prior-art grounding for a research idea, including setup, registration guidance, configuration, retrieval, artifact…
Comm Lit Review
brycewang-stanford/Auto-Empirical-Research-Skills
Communications-domain literature review and related-work search with database-aware source control.
Mechanical Engineering Research
ccplugins/awesome-claude-code-plugins
Research, write, code, analyze, present, and develop proposals for thermal-fluid mechanical engineering work with source-aware rigor.
Patsnap Scientific Literature Journals
patsnap/mcp
Patsnap Scientific Literature & Journals MCP for AI agents. An agent skill from patsnap/mcp.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Uist Related Work
What does Uist Related Work do?
A skill your agent uses when positioning a UIST submission against prior art — organizing by capability delta rather than paper lists, covering the technique lineage, toolkit ancestry, and…. Uist Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Uist Related Work?
Uist Related Work fits situations like: positioning a UIST submission against prior art — organizing by capability delta rather than paper lists; covering the technique lineage; toolkit ancestry; commercial systems reviewers know.
How do I install Uist Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-related-work -a claude-code`. Or copy the skill folder (UIST-Skills/skills/uist-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/uist-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Uist Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-related-work -a codex`. Or copy the skill folder (UIST-Skills/skills/uist-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/uist-related-work in your project. Codex loads it when a task matches its description.
Can I use Uist Related Work in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-related-work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/uist-related-work, .gemini/skills/uist-related-work, .github/skills/uist-related-work and .opencode/skills/uist-related-work in your project.
What does Uist Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Uist Related Work is instructions for the agent only.
Does Uist Related Work access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Uist Related Work safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Uist Related Work use?
Uist Related Work is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Uist Related Work use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Uist Related Work?
Skills that share tags, products or a category with Uist Related Work: Neuroarxiv (UditAkhourii/neuroarxiv, 433 stars), Deltasci Ground (boheling/deltasci, 144 stars), Sciatlas Idea Grounding (zjunlp/SciAtlas, 160 stars) and Comm Lit Review (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Uist Related Work?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.