Agent skill

Uist Camera Ready

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

Install Uist Camera Ready

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-camera-ready -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-camera-ready --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ 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-camera-ready .claude/skills/uist-camera-ready && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "uist-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-camera-ready into .claude/skills/uist-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-camera-ready", 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

$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-camera-ready

Type 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-camera-ready -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-camera-ready --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-camera-ready .agents/skills/uist-camera-ready && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "uist-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-camera-ready into .agents/skills/uist-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-camera-ready", 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-camera-ready -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-camera-ready --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-camera-ready .cursor/skills/uist-camera-ready && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "uist-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-camera-ready into .cursor/skills/uist-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-camera-ready", 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

$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path UIST-Skills/skills/uist-camera-ready

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-camera-ready -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-camera-ready --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-camera-ready .gemini/skills/uist-camera-ready && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "uist-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-camera-ready into .gemini/skills/uist-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-camera-ready", 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.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-camera-ready

Installs 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).

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-camera-ready -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ 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-camera-ready .github/skills/uist-camera-ready && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "uist-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-camera-ready into .github/skills/uist-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-camera-ready", 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-camera-ready -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-camera-ready --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-camera-ready .opencode/skills/uist-camera-ready && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "uist-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-camera-ready into .opencode/skills/uist-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-camera-ready", 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-camera-ready
GitHub stars: 1.2k
Token cost: ~1.5k tokens
SKILL.md length: 694 words
Files: 1
Skills in repo: 2,387
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Converting a conditional UIST acceptance into a published paper — delivering the rebuttal-promised changes by the July deadline
SKILL.md covers Workstream 1: deliver the…, Workstream 2: production and…, Workstream 3: de-anonymize and… and TAPS realities, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Working the ACM TAPS pipeline with alt text for every figure and table

What it does

Uist Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.

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 Frontend & Design. 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

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

Example prompts

“/uist-camera-ready”

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 Camera Ready loads about 1.5k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 694 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~81
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

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). 694 words, ~1,492 tokens.

Download SKILL.mdSave it as .claude/skills/uist-camera-ready/SKILL.md (or your agent's skills folder).

name: uist-camera-ready
description: 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 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 file mapping promise → location — useful if the process asks anyone to verify conditions, and essential when six co-authors edit in parallel.
The growth budget is +10%: one extra page for standard papers, half a page for short papers (2026 numbers). Promised additions get the space first; new camera-ready ambitions get what remains.
Do not silently make substantive changes nobody asked for; a camera-ready is a fulfillment step, not a second revision cycle.

Workstream 2: production and accessibility

Camera-ready flows through ACM TAPS (source upload, not just a PDF), and the 2026 guide adds accessible-PDF tagging via APTARA. The author-side accessibility obligations are concrete:

Item	2026 requirement
Alt text	Required for every figure, subfigure, and table
Tables	Real table markup, not images of tables
Math	Source-level math, not equation screenshots
Video	Final video figure with captions
PDF tagging	Applied in the TAPS/APTARA workflow from your source

Writing alt text for an interface-systems paper is its own small craft: describe the interaction state the figure evidences, not the pixels. "Annotated sequence: a finger drags on the forearm and the cursor traces the same path on the watch, 0.3 s later" beats "screenshot of the system."

text

Alt-text pass over the figure inventory:
  [ ] every \includegraphics has \Description{...}
  [ ] every subfigure has its own description
  [ ] tables described (what varies across rows/columns, the takeaway)
  [ ] teaser figure description states the core interaction
  [ ] no description says "image of" / "figure showing" boilerplate

Workstream 3: de-anonymize and finalize assets

Restore authors, affiliations, acknowledgements, and grant numbers; flip the acmart options from the review/anonymous configuration to the final one per the current guide.
Reverse the third-person self-citation contortions where they now read oddly — but only where the meaning improves.
Restore real repository and project-page URLs, and make them live before the proceedings do (see uist-artifact-evaluation for what should be at the other end).
Produce the final video figure: captioned, de-anonymized, credits added; check the current guide for any preview-video obligation (待核实 for 2026).
Complete ACM e-rights before TAPS will process; the open-access terms applying to UIST 2026 authors were not verifiable at check time (待核实) — read the e-rights form, not folklore.

Show full SKILL.md (288 more words)Show less

TAPS realities

TAPS consumes source (LaTeX or Word), not a hand-tuned PDF, which surprises teams whose submission compiled through local hacks:

Custom macros, non-standard packages, and manual float surgery that survived review can fail TAPS validation; budget one full rebuild-from-clean-template day.
Figures need production-quality originals (vector where possible); the screenshot that looked fine at review DPI may not at publication.
The \Description{} commands are part of the source, so the alt-text pass happens in LaTeX, not in a PDF editor afterward.
Validate early: upload a candidate build the week the system opens rather than on the deadline, because TAPS error messages arrive on production timelines, not chat timelines.
Keep the review PDF and the camera-ready in the same repository with a tagged divergence point; the "which version did we promise that in" question recurs for years.

Four-week schedule (notification June 27 → deadline July 24, 2026)

Week	Deliverable
1	Promise ledger reconstructed; edits assigned; e-rights initiated; registration/visa checks started
2	All contractual edits merged; +10% budget reconciled; figure originals collected
3	Alt-text pass; TAPS candidate upload; validation errors cleared
4	Final video captioned and uploaded; last TAPS build verified; buffer only

Conference logistics start now

Registration and the presenting author: confirm the current in-person requirement wording (待核实 for 2026) as soon as notification lands — visas for a US venue (Detroit, November 2-5, 2026) can take longer than the camera-ready window.
UIST talks are short and demo-culture shaped: build the talk around the live or recorded demonstration, not around related-work slides.
Plan the hallway demo: papers whose systems can be demonstrated at the conference compound their impact; shipping hardware to a venue takes lead time (and consider a Demos-track submission for the same system where the rules allow).

Output format

text

[Contract status] promises delivered <k>/<n>; open items with owners
[Page budget] final length vs +10% allowance
[TAPS status] source uploaded / validation errors / complete
[Accessibility] alt-text pass done? tables/math as markup? video captioned?
[Logistics] e-rights · registration · visa · demo shipping — each with a date

Files

Just SKILL.md in UIST-Skills/skills/uist-camera-ready of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Uist Camera Ready 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.

Uist Camera Ready compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Uist Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1.5k	Automated safety check: Pass	MIT	13 days ago
Web Artifacts Builderanthropics/skills	180k	40 repos	~769	Automated safety check: Pass	Apache-2.0	yesterday
React Doctormakeplane/plane	61k	12 repos	~657	Automated safety check: Pass	AGPL-3.0	yesterday
Impeccablebestofjs/bestofjs	3.1k	26 repos	~2.6k	Automated safety check: Pass	MIT	6 days ago
Figma Design System Builderwarpdotdev/warp	65k	2 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today
Web Interface Guidelines Reviewervercel-labs/openreview	1.7k	97 repos	~308	Automated safety check: Pass	None	7 mo ago

Similar skills

Web Artifacts Builder
anthropics/skills
Official
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
180k GitHub starsUsed in 40 repos~769 tokens
Frontend & DesignAuto-check passed
React Doctor
makeplane/plane
Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.
61k GitHub starsUsed in 12 repos~657 tokens
Frontend & DesignAuto-check passed
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
3.1k GitHub starsUsed in 26 repos~2.6k tokens
Frontend & DesignAuto-check passed
Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
65k GitHub starsUsed in 2 repos~4.4k tokens
Frontend & DesignAuto-check passed
Web Interface Guidelines Reviewer
vercel-labs/openreview
Official
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
1.7k GitHub starsUsed in 97 repos~308 tokens
Frontend & DesignAuto-check passed
Tailwindcss Development
anonaddy/anonaddy
Always invoke when the user's message includes 'tailwind' in any form.
4.9k GitHub starsUsed in 10 repos~865 tokens
Frontend & DesignAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

Aaag 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…
1.2k GitHub stars~1.3k tokensUpdated 13 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 13 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 13 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 13 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 13 days ago
Auto-check passed
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…
1.2k GitHub stars~1.6k tokensUpdated 13 days ago
Auto-check passed

Questions about Uist Camera Ready

What does Uist Camera Ready do?

A skill your agent uses 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…. Uist Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.

When should I use Uist Camera Ready?

Uist Camera Ready fits situations like: 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.

How do I install Uist Camera Ready in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-camera-ready -a claude-code`. Or copy the skill folder (UIST-Skills/skills/uist-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/uist-camera-ready in your project. Claude Code loads it when a task matches its description.

How do I install Uist Camera Ready in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-camera-ready -a codex`. Or copy the skill folder (UIST-Skills/skills/uist-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/uist-camera-ready in your project. Codex loads it when a task matches its description.

Can I use Uist Camera Ready 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-camera-ready -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-camera-ready, .gemini/skills/uist-camera-ready, .github/skills/uist-camera-ready and .opencode/skills/uist-camera-ready in your project.

What does Uist Camera Ready need to run?

SKILL.md names no scripts, command-line tools or credentials: Uist Camera Ready is instructions for the agent only.

Does Uist Camera Ready 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 Camera Ready 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 Camera Ready use?

Uist Camera Ready 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 Camera Ready 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 Camera Ready?

Skills that share tags, products or a category with Uist Camera Ready: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Uist Camera Ready?

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.

Install Uist Camera Ready

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

UIST Camera-Ready

Workstream 1: deliver the contract

Workstream 2: production and accessibility

Workstream 3: de-anonymize and finalize assets

TAPS realities

Four-week schedule (notification June 27 → deadline July 24, 2026)

Conference logistics start now

Output format

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Related

Questions about Uist Camera Ready