Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when performing the final pre-upload audit of a UIST paper in PCS — the abstract-then-paper deadline pair, 10-page/5-page two-column limits with desk-reject enforcement…
Install Uist Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-submission --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-submission .claude/skills/uist-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-submission into .claude/skills/uist-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-submission", 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-submissionType 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-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-submission --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-submission .agents/skills/uist-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-submission into .agents/skills/uist-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-submission", 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-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-submission --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-submission .cursor/skills/uist-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-submission into .cursor/skills/uist-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-submission", 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-submission--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-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-submission --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-submission .gemini/skills/uist-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-submission into .gemini/skills/uist-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-submission", 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-submissionInstalls 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-submission -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-submission .github/skills/uist-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-submission into .github/skills/uist-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-submission", 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-submission -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-submission --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-submission .opencode/skills/uist-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-submission into .opencode/skills/uist-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-submission", 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-submission- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 767 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when performing the final pre-upload audit of a UIST paper in PCS — the abstract-then-paper deadline pair, 10-page/5-page two-column limits with desk-reject enforcement…
- Works in 2 steps: Abstract deadline (one week out). Title,… → Paper deadline. The PDF, the video…
- Performing the final pre-upload audit of a UIST paper in PCS — the abstract-then-paper deadline pair
- SKILL.md covers What PCS collects, and when, Format gate, Anonymity, the UIST version and Deadline-week order of…, plus 4 more sections
- Calls pdftotext and ffprobe
What it does
Uist Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when performing the final pre-upload audit of a UIST paper in PCS — the abstract-then-paper deadline pair, 10-page/5-page two-column limits with desk-reject enforcement, anonymous acmart options, video-figure and supplementary uploads, the prior-work overlap rule, and deadline-week sequencing.
Its SKILL.md is about 1.6k 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. 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
- Performing the final pre-upload audit of a UIST paper in PCS — the abstract-then-paper deadline pair
- 10-page/5-page two-column limits with desk-reject enforcement
- Anonymous acmart options
- Video-figure and supplementary uploads
Example prompts
- “/uist-submission”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Abstract deadline (one week out). Title, abstract, author list, and metadata
- Paper deadline. The PDF, the video figure, and all supplementary files.
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
Shell commands in SKILL.md call:
pdftotextffprobe
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 Submission loads about 1.6k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 767 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). 767 words, ~1,588 tokens.
Download SKILL.mdSave it as
.claude/skills/uist-submission/SKILL.md (or your agent's skills folder).- name
- uist-submission
- description
- Use when performing the final pre-upload audit of a UIST paper in PCS — the abstract-then-paper deadline pair, 10-page/5-page two-column limits with desk-reject enforcement, anonymous acmart options, video-figure and supplementary uploads, the prior-work overlap rule, and deadline-week sequencing.
UIST Submission
This is the audit to run in the final week before the Papers deadline. Numbers below
are the verified 2026 cycle (checked 2026-07-08 via search renderings of
uist.acm.org/2026/, direct fetch blocked): abstracts March 24, papers March 31,
both 11:59 pm AoE. The 2026 deadline has passed — apply this skill to a 2027
submission only after re-reading that year's Author Guide, and expect the numbers to
move.
What PCS collects, and when
UIST runs on PCS (Precision Conference Solutions): in the submission form, choose society "SIGCHI", conference "UIST 2026", track "UIST 2026 Papers". Two deadlines structure the week:
- Abstract deadline (one week out). Title, abstract, author list, and metadata must exist in PCS. This gates reviewer assignment — a placeholder abstract that drifts from the final paper lands you with mismatched reviewers, the least fixable submission error.
- Paper deadline. The PDF, the video figure, and all supplementary files. Everything reviewed arrives now; there is no later supplement slot.
Format gate
| Check | 2026 rule | Enforcement |
|---|---|---|
| Template | Two-column acmart, \documentclass[sigconf,review,anonymous]{acmart} | Manual + visual |
| Body length | 10 pages (standard) or 5 pages (short), excluding references and appendices | Desk reject if exceeded |
| Appendices | Inside the same PDF, after references; body must stand alone | Review-stage damage |
| Video figure | Optional, strongly encouraged: ≤ 3 min, 1080p/4K, MP4 H.264 | Reviewer-side (see uist-supplementary) |
| Anonymity | Paper, video, and supplement all purged of identity | Desk reject |
A short paper is a distinct category (smaller complete contribution), not a truncated standard paper — do not switch categories on deadline night to dodge the page count.
Anonymity, the UIST version
The standard is "reasonable effort," with two venue-specific twists:
- Third-person self-citation with full references. Do not redact your own citations; write about your prior work as if someone else built it.
- Overlap attachment. If a prior submission of yours overlaps significantly, upload an anonymized copy of it as supplementary material.
Sweep everything that ships: PDF text, PDF metadata, acknowledgements and grant numbers, repository and project-page URLs, video frames (lab posters, faces, institutional wallpaper), video audio (narrator self-identification), file names, and archive contents.
# Mechanical pass over the actual upload set
pdfinfo paper.pdf | grep -Ei 'author|creator|producer'
pdftotext paper.pdf - | grep -nEi 'github|gitlab|osf\.io|acknowledg|grant' | head
ffprobe -v error -show_entries format=duration:stream=width,height,codec_name video.mp4
unzip -l supplement.zip | grep -Ei '\.git|DS_Store|/Users/|/home/' | headDeadline-week order of operations
- T-7d: abstract deadline — final title/abstract in PCS, authors and conflicts complete, subject metadata chosen for reviewer routing.
- T-5d: body frozen at the page limit; appendix absorbs the overflow.
- T-4d: video locked (edits, captions, anonymization) and compressed to spec; verify PCS accepts the file size early, since caps were not published (待核实).
- T-2d: full anonymity sweep on the merged PDF, video, and archive; run the mechanical checks above on the exact files to be uploaded.
- T-1d: upload everything, then re-download from PCS and open cold — the re-downloaded copy is what reviewers see. Confirm the PCS abstract matches the PDF abstract word for word.
- T-0: buffer only. AoE means UTC-12; convert once, write it on the wall.
Show full SKILL.md (303 more words)Show less
PCS form fields worth drafting early
The form is read before the PDF and configured per track; draft its contents days ahead rather than composing in the upload session:
- Title and abstract — identical to the PDF, since the abstract drives reviewer matching from the abstract deadline onward.
- Author list and conflicts — complete at abstract time; adding authors later in the process is at minimum awkward and possibly restricted (待核实 per cycle).
- Subject/topic descriptors — choose for the reviewer pool you want; a fabrication paper tagged only "AI" gets AI reviewers.
- Prior-submission declarations — where the form asks about overlapping or previously reviewed material, answer literally; this is also where the anonymized overlap attachment gets referenced.
- Track category — standard vs short is a claim about contribution scale; reviewers hold you to the category you picked.
Last-day failure modes, ranked by frequency
| Failure | Prevention |
|---|---|
| Video upload stalls or exceeds an unpublished cap | Upload media a full day early; keep a lower-bitrate export ready |
| Final LaTeX rebuild shifts the paper past the limit | Freeze the body two days out; late edits go to the appendix |
| PDF metadata carries an author name from a home template | Mechanical sweep on the exact export, every export |
| PCS abstract diverges from a last-minute PDF abstract edit | One person owns both texts; diff them at T-1d |
| A co-author's "tiny fix" reintroduces an acknowledgements block | Lock the repo after the anonymity sweep |
Dual-track and dual-venue rules
- Papers under review elsewhere may not be under review at UIST at the same time.
- Within UIST 2026, the same work sent to both Demos and Posters is treated as a demo submission and rejected from Posters — pick one adjunct lane deliberately.
- A prior adjunct publication (demo/poster abstract) of the same system does not anonymize away: cite it in the third person and state the delta.
Output format
[Submission status] ready / blocked / at risk
[Format gate] pages <n>/<limit> · template ok? · video spec ok?
[Anonymity sweep] clean / leaks: <file: location>
[PCS state] abstract locked · uploads verified by re-download?
[Remaining actions] <ordered, with owner and hour>© 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-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Uist Submission 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 Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
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 Submission
What does Uist Submission do?
A skill your agent uses when performing the final pre-upload audit of a UIST paper in PCS — the abstract-then-paper deadline pair, 10-page/5-page two-column limits with desk-reject enforcement…. Uist Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when performing the final pre-upload audit of a UIST paper in PCS — the abstract-then-paper deadline pair, 10-page/5-page two-column limits with desk-reject enforcement, anonymous acmart options, video-figure and supplementary uploads, the prior-work overlap rule, and deadline-week sequencing.
When should I use Uist Submission?
Uist Submission fits situations like: performing the final pre-upload audit of a UIST paper in PCS — the abstract-then-paper deadline pair; 10-page/5-page two-column limits with desk-reject enforcement; anonymous acmart options; video-figure and supplementary uploads.
How do I install Uist Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-submission -a claude-code`. Or copy the skill folder (UIST-Skills/skills/uist-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/uist-submission in your project. Claude Code loads it when a task matches its description.
How do I install Uist Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-submission -a codex`. Or copy the skill folder (UIST-Skills/skills/uist-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/uist-submission in your project. Codex loads it when a task matches its description.
Can I use Uist Submission 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-submission -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-submission, .gemini/skills/uist-submission, .github/skills/uist-submission and .opencode/skills/uist-submission in your project.
What does Uist Submission need to run?
Going by SKILL.md and its folder, Uist Submission needs the command-line tools its instructions call (pdftotext and ffprobe).
Does Uist Submission 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 Submission 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 Submission use?
Uist Submission 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 Submission use?
About 1.6k tokens (SKILL.md is roughly 6.4k 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 Submission?
Skills that share tags, products or a category with Uist Submission: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Uist Submission?
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.