Convert
remotion-dev/remotion
Start the local @remotion/convert app and open it in the Codex browser.
A skill your agent uses when converting an accepted UAI paper into its PMLR proceedings version, covering de-anonymization, final formatting against the UAI template, metadata for the PMLR volume…
MITAuto-check passed
Install Uai Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-camera-ready --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/UAI-Skills/skills/uai-camera-ready .claude/skills/uai-camera-ready && 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 "uai-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-camera-ready into .claude/skills/uai-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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 install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-camera-readyType 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 uai-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-camera-ready --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/UAI-Skills/skills/uai-camera-ready .agents/skills/uai-camera-ready && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "uai-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-camera-ready into .agents/skills/uai-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-camera-ready --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/UAI-Skills/skills/uai-camera-ready .cursor/skills/uai-camera-ready && 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 "uai-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-camera-ready into .cursor/skills/uai-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path UAI-Skills/skills/uai-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.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-camera-ready --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/UAI-Skills/skills/uai-camera-ready .gemini/skills/uai-camera-ready && 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 "uai-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-camera-ready into .gemini/skills/uai-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-camera-readyInstalls 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 uai-camera-ready -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/UAI-Skills/skills/uai-camera-ready .github/skills/uai-camera-ready && 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 "uai-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-camera-ready into .github/skills/uai-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-camera-ready -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 uai-camera-ready --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/UAI-Skills/skills/uai-camera-ready .opencode/skills/uai-camera-ready && 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 "uai-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-camera-ready into .opencode/skills/uai-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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
uai-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 805 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when converting an accepted UAI paper into its PMLR proceedings version, covering de-anonymization, final formatting against the UAI template, metadata for the PMLR volume…
- Works in 6 steps: Week 1: changelog from review… → Weeks 2–3: text edits, restored… → Week 4: public repository release,… → …
- Converting an accepted UAI paper into its PMLR proceedings version
- SKILL.md covers Where the paper is going, De-anonymization pass, Reconciling with the review… and Production checklist, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Uai Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an accepted UAI paper into its PMLR proceedings version, covering de-anonymization, final formatting against the UAI template, metadata for the PMLR volume, restoring public code and data links, poster and spotlight preparation for the conference, and sequencing work back from the camera-ready deadline.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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 an accepted UAI paper into its PMLR proceedings version
- Covering de-anonymization
- Final formatting against the UAI template
- Metadata for the PMLR volume
Example prompts
- “/uai-camera-ready”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Week 1: changelog from review commitments; assign owners.
- Weeks 2–3: text edits, restored identities, regenerated figures.
- Week 4: public repository release, tagged and linked from the paper.
- Weeks 5–6: PMLR forms and metadata; internal proofread of the merged PDF.
- Before the deadline: upload, then re-download and cold-read the archived file.
- Remaining weeks: registration, visa/travel if attending in person, poster print,
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 (its code samples are bibtex).
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
Uai Camera Ready loads about 1.7k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 805 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). 805 words, ~1,727 tokens.
Download SKILL.mdSave it as
.claude/skills/uai-camera-ready/SKILL.md (or your agent's skills folder).- name
- uai-camera-ready
- description
- Use when converting an accepted UAI paper into its PMLR proceedings version, covering de-anonymization, final formatting against the UAI template, metadata for the PMLR volume, restoring public code and data links, poster and spotlight preparation for the conference, and sequencing work back from the camera-ready deadline.
UAI Camera Ready
Use this after the acceptance email. In the 2026 cycle, notification was June 1 and camera-ready files were due July 27, ahead of the August 17–21 conference in Amsterdam — roughly eight weeks that also contain registration, travel, and poster production. Reopen the current camera-ready instructions on the UAI site before starting; PMLR mechanics and page allowances are settled per cycle and were not fully published at pack-verification time (final-version page allowance: 待核实).
Where the paper is going
Accepted UAI papers are published as a volume of the Proceedings of Machine Learning Research. The series is open access with no author-side publication fee; the conference is funded by registration. Recent anchors, useful for citing prior UAI work correctly and for knowing what your own entry will look like: UAI 2021 = PMLR v161, 2022 = v180, 2023 = v216, 2024 = v244, 2025 = v286. The 2026 volume number is assigned by PMLR (待核实 until the volume page exists).
@inproceedings{deshpande24a,
title = {Calibrated and Conformal Propensity Scores for Causal Effect Estimation},
author = {Deshpande, Shachi and Kuleshov, Volodymyr},
booktitle = {Proceedings of the Fortieth Conference on Uncertainty in Artificial Intelligence},
series = {Proceedings of Machine Learning Research},
volume = {244},
pages = {1083--1111},
year = {2024},
publisher = {PMLR}
}Use this shape (verified against the PMLR v244 metadata) as the model for your own eventual entry and for citing UAI papers in the camera-ready bibliography.
De-anonymization pass
Reverse every anonymity measure deliberately rather than by memory:
- Restore the author block, affiliations, and correct ordering; cross-check against the OpenReview author list, which feeds proceedings metadata.
- Rewrite third-person self-references back to natural phrasing where it helps clarity.
- Reinstate acknowledgements and grant numbers that the submission rules forced out.
- Replace the anonymized supplementary archive with a public, versioned repository link; the CFP's strong encouragement of code and data release is easiest to honor now, when no anonymity constraint remains.
- Re-run metadata checks in reverse: the PDF should now carry the true title and authors.
Reconciling with the review record
- Implement every change you committed to during the author-response phase; area chairs occasionally check, and co-authors always remember differently.
- Fold in reviewer-requested clarifications that fit without altering claims. Camera-ready is for sharpening accepted content, not for smuggling in new results.
- Keep a one-page changelog mapping each commitment to the section where it landed — useful internally and if chairs ask.
Production checklist
| Item | Failure it prevents |
|---|---|
| Current-cycle UAI template, final (non-anonymous) mode | Volume-wide formatting mismatch flagged by proceedings editors |
| Title/abstract identical across PDF, OpenReview, and PMLR forms | Broken indexing and citation splits |
| Every appendix referenced from the main text still resolves | Dangling "see App. D" after camera-ready edits |
| Figures regenerated from final code | Plot-vs-table divergence in the archival version |
| License and copyright forms as required this cycle | Publication held back on paperwork (exact forms: 待核实) |
| Repository tagged with a release matching the paper | "Code link rots by conference week" failure |
Show full SKILL.md (373 more words)Show less
Presentation obligations
For 2026 the conference stated that all accepted papers are presented in poster sessions and spotlight presentations, physically or remotely, with selected papers receiving longer slots. Practical consequences:
- Prepare a poster and a short spotlight talk as the default; treat a longer oral as a bonus you learn about later.
- The physically-or-remotely wording is UAI 2026's; whether remote presentation remains available, and what registration category it requires, must be reconfirmed against the current attendance and registration pages (fees and mandatory-registration rules: 待核实).
- Build the poster from the paper's inference story — the model, the assumption set, the guarantee or diagnostic, one decisive experiment — rather than shrinking eight pages onto A0.
Small print that bites in July
- European venue logistics (2026: Amsterdam) put visa timelines on the critical path for many authors — start the invitation-letter process the week of notification.
- August conferences collide with European institutional holidays; confirm your co-authors' availability for the forms-and-proofread window before assuming it.
- Poster printing on-site versus shipping is a real decision at international venues; decide two weeks out, not on arrival.
Sequence from acceptance to the conference
- Week 1: changelog from review commitments; assign owners.
- Weeks 2–3: text edits, restored identities, regenerated figures.
- Week 4: public repository release, tagged and linked from the paper.
- Weeks 5–6: PMLR forms and metadata; internal proofread of the merged PDF.
- Before the deadline: upload, then re-download and cold-read the archived file.
- Remaining weeks: registration, visa/travel if attending in person, poster print, spotlight rehearsal.
Metadata consistency sweep
PMLR entries are generated from structured metadata, so one inconsistency propagates to Google Scholar, DBLP, and every future citation. Sweep these pairs:
- PDF title ↔ OpenReview title ↔ PMLR form title (including math in titles, which PMLR renders from LaTeX — check the escaped form).
- Author name spellings and diacritics ↔ each author's canonical publishing name; a dropped accent forks a Scholar profile.
- Author order ↔ what the group actually agreed; camera-ready is the last cheap moment to fix it.
- Abstract in the form ↔ abstract in the PDF after final edits.
- Repository URL in the paper ↔ the tagged release, not the moving main branch.
- BibTeX self-entry drafted for your own website ↔ the volume's eventual format (model it on the verified entry above).
Output format
[Camera-ready state] not started / in edits / forms pending / uploaded
[Deadline distance] <days to current official camera-ready date>
[Commitment coverage] <review promises implemented / total>
[Public artifacts] repo tagged? data linked? license chosen?
[Presentation prep] poster / spotlight / long-talk status© 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 UAI-Skills/skills/uai-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Uai 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Uai Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Convertremotion-dev/remotion | 63k | — | ~247 | Automated safety check: Pass | Custom licence | |
| QA Acceptancepaperclipai/paperclip | 99k | — | ~964 | Automated safety check: Pass | MIT | |
| Acceptance Orchestratorsickn33/agentic-awesome-skills | 47k | 2 repos | ~943 | Automated safety check: Pass | MIT | |
| Acceptance Evidence for Deliverieslobehub/lobehub | 83k | — | ~9.7k | Automated safety check: Pass | Apache-2.0 | |
| Word to Markdown Convertergithub/awesome-copilot | 40k | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
QA Acceptance
paperclipai/paperclip
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
Acceptance Orchestrator
sickn33/agentic-awesome-skills
A skill your agent uses when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
- Official
Word to Markdown Converter
github/awesome-copilot
Converts Word .docx files to Markdown with a bundled script before analysis, extracting embedded images and handling whole folders alongside the PDF and Excel converters.
Change, Accept or Leave Framework
kangarooking/cangjie-skill
Helps someone stuck ruminating over an unchangeable situation decide whether to change it, accept it, or leave it, drawn from a chapter of Navalism-style writing.
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…
Questions about Uai Camera Ready
What does Uai Camera Ready do?
A skill your agent uses when converting an accepted UAI paper into its PMLR proceedings version, covering de-anonymization, final formatting against the UAI template, metadata for the PMLR volume…. Uai Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an accepted UAI paper into its PMLR proceedings version, covering de-anonymization, final formatting against the UAI template, metadata for the PMLR volume, restoring public code and data links, poster and spotlight preparation for the conference, and sequencing work back from the camera-ready deadline.
When should I use Uai Camera Ready?
Uai Camera Ready fits situations like: converting an accepted UAI paper into its PMLR proceedings version; covering de-anonymization; final formatting against the UAI template; metadata for the PMLR volume.
How do I install Uai Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-camera-ready -a claude-code`. Or copy the skill folder (UAI-Skills/skills/uai-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/uai-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Uai Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-camera-ready -a codex`. Or copy the skill folder (UAI-Skills/skills/uai-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/uai-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Uai 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 uai-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/uai-camera-ready, .gemini/skills/uai-camera-ready, .github/skills/uai-camera-ready and .opencode/skills/uai-camera-ready in your project.
What does Uai Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Uai Camera Ready is instructions for the agent only.
Does Uai 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 Uai 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 Uai Camera Ready use?
Uai 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 Uai Camera Ready use?
About 1.7k tokens (SKILL.md is roughly 6.9k 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 Uai Camera Ready?
Skills that share tags, products or a category with Uai Camera Ready: Convert (remotion-dev/remotion, 63k stars), QA Acceptance (paperclipai/paperclip, 99k stars), Acceptance Orchestrator (sickn33/agentic-awesome-skills, 47k stars) and Acceptance Evidence for Deliveries (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Uai 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.