Audit Preparation
sickn33/agentic-awesome-skills
Audit preparation register: required document, period covered, request and receipt dates, preparer and reviewer, auditor queries and adjustments.
A skill your agent uses when preparing a WSDM camera-ready after acceptance - de-anonymization order, ACM rights and TAPS production into the Digital Library proceedings, CCS concepts and keywords…
MITAuto-check passed
Install Wsdm Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wsdm-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wsdm-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/WSDM-Skills/skills/wsdm-camera-ready .claude/skills/wsdm-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 "wsdm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WSDM-Skills/skills/wsdm-camera-ready into .claude/skills/wsdm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wsdm-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/WSDM-Skills/skills/wsdm-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 wsdm-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wsdm-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/WSDM-Skills/skills/wsdm-camera-ready .agents/skills/wsdm-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 "wsdm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WSDM-Skills/skills/wsdm-camera-ready into .agents/skills/wsdm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wsdm-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 wsdm-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wsdm-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/WSDM-Skills/skills/wsdm-camera-ready .cursor/skills/wsdm-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 "wsdm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WSDM-Skills/skills/wsdm-camera-ready into .cursor/skills/wsdm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wsdm-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 WSDM-Skills/skills/wsdm-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 wsdm-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wsdm-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/WSDM-Skills/skills/wsdm-camera-ready .gemini/skills/wsdm-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 "wsdm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WSDM-Skills/skills/wsdm-camera-ready into .gemini/skills/wsdm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wsdm-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 wsdm-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 wsdm-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/WSDM-Skills/skills/wsdm-camera-ready .github/skills/wsdm-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 "wsdm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WSDM-Skills/skills/wsdm-camera-ready into .github/skills/wsdm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wsdm-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 wsdm-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 wsdm-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/WSDM-Skills/skills/wsdm-camera-ready .opencode/skills/wsdm-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 "wsdm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WSDM-Skills/skills/wsdm-camera-ready into .opencode/skills/wsdm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wsdm-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
wsdm-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 703 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when preparing a WSDM camera-ready after acceptance - de-anonymization order, ACM rights and TAPS production into the Digital Library proceedings, CCS concepts and keywords…
- Preparing a WSDM camera-ready after acceptance - de-anonymization order
- SKILL.md covers The order of operations that…, De-anonymization is an editing…, Reviewer-requested changes… and Production checklist, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- ACM rights and TAPS production into the Digital Library proceedings
What it does
Wsdm Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing a WSDM camera-ready after acceptance - de-anonymization order, ACM rights and TAPS production into the Digital Library proceedings, CCS concepts and keywords, page-allowance verification, artifact link restoration, and registration/presentation duties at a single-track winter conference.
Its SKILL.md is about 1.8k 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
- Preparing a WSDM camera-ready after acceptance - de-anonymization order
- ACM rights and TAPS production into the Digital Library proceedings
- CCS concepts and keywords
- Page-allowance verification
Example prompts
- “/wsdm-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
Wsdm Camera Ready loads about 1.8k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 703 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). 703 words, ~1,788 tokens.
Download SKILL.mdSave it as
.claude/skills/wsdm-camera-ready/SKILL.md (or your agent's skills folder).- name
- wsdm-camera-ready
- description
- Use when preparing a WSDM camera-ready after acceptance - de-anonymization order, ACM rights and TAPS production into the Digital Library proceedings, CCS concepts and keywords, page-allowance verification, artifact link restoration, and registration/presentation duties at a single-track winter conference.
WSDM Camera-Ready
Turn an accepted WSDM paper into its archival form in the ACM Digital Library. WSDM proceedings are ACM proceedings (WSDM '26 is DOI 10.1145/3773966; each edition gets its own volume), so the mechanics run through ACM's standard production chain. Warning up front: the pack could not verify the current edition's camera-ready deadline or final page allowance - both are 待核实 items that the acceptance email and author-kit page settle, and nothing here substitutes for them.
The order of operations that avoids rework
1. Read the acceptance email twice; extract deadline, page allowance,
required class options, and the rights-form sender to whitelist.
2. Complete the ACM e-rights form FIRST - it generates the exact
copyright block and \setcopyright values your LaTeX must carry.
3. De-anonymize: author block, third-person self-citations back to
first person where natural, acknowledgements and grants restored.
4. Restore real artifact URLs (the anonymous repo becomes the public
one) and re-run every link.
5. Add/verify CCS concepts and keywords via the ACM CCS tool.
6. Rebuild with the camera-ready class options; check the allowance.
7. Submit source (TAPS-style production expects LaTeX/Word source,
not just a PDF); fix validation errors early - TAPS queues clog
near deadlines.
8. Register an author and confirm who presents (talk and/or poster).Steps 2 before 3-6 matters: the rights confirmation dictates copyright text, DOI string, and reference format, and TAPS-produced output will be rejected or regenerated if the rights block is wrong.
De-anonymization is an editing pass, not a toggle
Removing anonymous from the class options is the trivial part. The real work:
- Self-citations written as "Prior work [12] showed..." to hide identity often read strangely once names return; decide sentence by sentence whether to restore first person.
- The rounded or role-anonymized platform descriptions (see
wsdm-submission) can now be made precise if your organization's disclosure review permits it. Industry authors: start internal publication approval the day of acceptance - it is the most common cause of missed camera-ready deadlines, not LaTeX. - Acknowledge funders and colleagues; ACM's authorship policy governs who may be listed as an author, and additions after acceptance typically need chair approval - ask, never quietly add.
Reviewer-requested changes without a rebuttal record
Because WSDM historically has no rebuttal, there is no author-committed change list from a discussion phase. The reviews and the SPC meta-review are still a soft contract: implement the factual and presentational fixes they request, and keep a one-page internal log of what changed. If the meta-review conditions acceptance on specific fixes, treat those as hard requirements and make them findable (a sentence in the right section beats a silent table tweak).
Production checklist
| Item | Check | Common failure |
|---|---|---|
| Rights form | Completed by the listed corresponding author | Form sat in a spam folder |
| Copyright block | Matches e-rights output exactly | Stale \setcopyright from a template |
| Page allowance | Camera-ready cap per the author kit (待核实 each edition) | Assuming the submission cap carries over |
| CCS + keywords | Generated from the CCS tool, pasted as XML/commands | Hand-typed concepts that fail validation |
| Metadata | Title/authors in the form == PDF exactly, including accents | Unicode mismatch breaking DL indexing |
| Artifact links | Public repo resolvable, tagged release, license file | Link still pointing at the anonymous mirror |
| Ethics section | Retained in final form | Deleted to reclaim space |
| ORCID | Current ACM production requests ORCIDs for authors | One coauthor without an ORCID at deadline |
Show full SKILL.md (279 more words)Show less
Edge cases that eat deadlines
- Author changes. Adding, removing, or reordering authors after acceptance needs explicit chair approval under ACM authorship norms; requests sent the week of the camera-ready deadline often cannot be processed in time. Raise them the day of acceptance.
- Title or abstract changes. Meta-review-driven retitles are usually fine but must be mirrored in the production system's metadata, or the DL landing page and the PDF will disagree forever.
- Preprint posture. Posting the accepted version to arXiv is common in this community, but verify the rights form's language about accepted-version posting and embargoes before uploading; the form you signed in step 2 governs, not habit.
- Figure regressions. TAPS-style recompilation with the publisher's tool
chain can shift floats and break subfigure references that looked fine
locally. Recheck every
\refin the produced PDF, not your local build. - Third-party content. A screenshot of a platform UI or a licensed dataset's example rows may require permission statements at production time; the anonymized submission hid the problem, the camera-ready surfaces it.
Money and presence
- ACM's open-access arrangements (ACM Open) determine whether your institution faces an APC-like charge for open access; WSDM-specific terms and any registration-bundled publication fee are 待核实 per edition - verify on the edition's registration page before budgeting.
- WSDM is small and traditionally single-track: an accepted long paper's talk is in front of essentially the whole community, and the poster session is a real hiring/collaboration floor. Decide the presenter early, check visa lead times for the host country (2027: Hong Kong, February 15-19), and confirm whether the edition requires in-person presentation - the pack found no verified remote-presentation policy for current editions.
Two-week runbook (adjust to the real deadline)
Day 0-1 acceptance email parsed; e-rights kicked off; disclosure
review opened (industry authors)
Day 2-5 de-anonymization edit pass; meta-review fixes implemented
Day 6-8 artifact goes public: real repo, license, tagged release,
archival snapshot; links restored in the source
Day 9-11 CCS concepts, ORCID sweep, metadata parity check
Day 12 production submission; validation errors fixed same day
Day 13-14 buffer for the error you did not predictOutput format
[Camera-ready status] on track / at risk (deadline: <from acceptance email>)
[Rights] e-rights done -> copyright block synced: yes / no
[De-anonymization] author block / self-citations / acks / links: done or pending
[Allowance] final page count vs verified cap: pass / over / cap unverified
[Meta-review conditions] <fix -> location implemented>
[Presence] registrant, presenter, visa lead time, disclosure approval 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 WSDM-Skills/skills/wsdm-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Wsdm 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 |
|---|---|---|---|---|---|---|
| Wsdm Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Audit Preparationsickn33/agentic-awesome-skills | 47k | 1 repos | ~5.3k | Automated safety check: Pass | MIT | |
| QA Acceptancepaperclipai/paperclip | 99k | — | ~964 | Automated safety check: Pass | MIT | |
| Release PreparationCherryHQ/cherry-studio | 53k | — | ~4.3k | Automated safety check: Pass | AGPL-3.0 | |
| 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 |
Similar skills
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.
Release Preparation
CherryHQ/cherry-studio
Prepares a Cherry Studio release by resolving the version, collecting commits, writing bilingual release notes, updating version files and creating a release branch.
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.
Prepare Paperclip PR
paperclipai/paperclip
Prepare a Paperclip branch for PR with commits, template body, and checks.
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 Wsdm Camera Ready
What does Wsdm Camera Ready do?
A skill your agent uses when preparing a WSDM camera-ready after acceptance - de-anonymization order, ACM rights and TAPS production into the Digital Library proceedings, CCS concepts and keywords…. Wsdm Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing a WSDM camera-ready after acceptance - de-anonymization order, ACM rights and TAPS production into the Digital Library proceedings, CCS concepts and keywords, page-allowance verification, artifact link restoration, and registration/presentation duties at a single-track winter conference.
When should I use Wsdm Camera Ready?
Wsdm Camera Ready fits situations like: preparing a WSDM camera-ready after acceptance - de-anonymization order; ACM rights and TAPS production into the Digital Library proceedings; CCS concepts and keywords; page-allowance verification.
How do I install Wsdm Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wsdm-camera-ready -a claude-code`. Or copy the skill folder (WSDM-Skills/skills/wsdm-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/wsdm-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Wsdm Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wsdm-camera-ready -a codex`. Or copy the skill folder (WSDM-Skills/skills/wsdm-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/wsdm-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Wsdm 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 wsdm-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/wsdm-camera-ready, .gemini/skills/wsdm-camera-ready, .github/skills/wsdm-camera-ready and .opencode/skills/wsdm-camera-ready in your project.
What does Wsdm Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Wsdm Camera Ready is instructions for the agent only.
Does Wsdm 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 Wsdm 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 Wsdm Camera Ready use?
Wsdm 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 Wsdm Camera Ready use?
About 1.8k tokens (SKILL.md is roughly 7.2k 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 Wsdm Camera Ready?
Skills that share tags, products or a category with Wsdm Camera Ready: Audit Preparation (sickn33/agentic-awesome-skills, 47k stars), QA Acceptance (paperclipai/paperclip, 99k stars), Release Preparation (CherryHQ/cherry-studio, 53k stars) and Acceptance Orchestrator (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wsdm 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.