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 Web Conference (WWW) camera-ready after acceptance, covering the uniform 12-page/8-content proceedings budget, de-anonymization and restored…
MITAuto-check passed
Install Webconf Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-camera-ready .claude/skills/webconf-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 "webconf-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-camera-ready into .claude/skills/webconf-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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/The-Web-Conference-Skills/skills/webconf-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 webconf-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-camera-ready .agents/skills/webconf-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 "webconf-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-camera-ready into .agents/skills/webconf-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 webconf-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-camera-ready .cursor/skills/webconf-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 "webconf-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-camera-ready into .cursor/skills/webconf-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 The-Web-Conference-Skills/skills/webconf-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 webconf-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-camera-ready .gemini/skills/webconf-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 "webconf-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-camera-ready into .gemini/skills/webconf-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 webconf-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 webconf-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/The-Web-Conference-Skills/skills/webconf-camera-ready .github/skills/webconf-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 "webconf-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-camera-ready into .github/skills/webconf-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 webconf-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 webconf-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/The-Web-Conference-Skills/skills/webconf-camera-ready .opencode/skills/webconf-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 "webconf-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-camera-ready into .opencode/skills/webconf-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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
webconf-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 853 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 Web Conference (WWW) camera-ready after acceptance, covering the uniform 12-page/8-content proceedings budget, de-anonymization and restored…
- Works in 3 steps: e-rights: the corresponding author… → TAPS (The ACM Publishing System)… → ACM Open exposure: whether an APC…
- Preparing a Web Conference (WWW) camera-ready after acceptance
- SKILL.md covers The proceedings budget is a…, De-anonymization sweep, ACM production pipeline… and Registration and presentation, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Webconf Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing a Web Conference (WWW) camera-ready after acceptance, covering the uniform 12-page/8-content proceedings budget, de-anonymization and restored acknowledgements, ACM e-rights and TAPS production, ACM Open cost exposure, author registration, and the artifact-badging submission that rides along with the final files.
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 Web Conference (WWW) camera-ready after acceptance
- Covering the uniform 12-page/8-content proceedings budget
- De-anonymization and restored acknowledgements
- ACM e-rights and TAPS production
Example prompts
- “/webconf-camera-ready”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- e-rights: the corresponding author receives the ACM rights form. The choice
- TAPS (The ACM Publishing System) compiles your source, not your PDF, and
- ACM Open exposure: whether an APC applies depends on the corresponding
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 bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
acm.org
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
Webconf Camera Ready loads about 1.8k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 853 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). 853 words, ~1,809 tokens.
Download SKILL.mdSave it as
.claude/skills/webconf-camera-ready/SKILL.md (or your agent's skills folder).- name
- webconf-camera-ready
- description
- Use when preparing a Web Conference (WWW) camera-ready after acceptance, covering the uniform 12-page/8-content proceedings budget, de-anonymization and restored acknowledgements, ACM e-rights and TAPS production, ACM Open cost exposure, author registration, and the artifact-badging submission that rides along with the final files.
Web Conference Camera-Ready
The 2026 notification-to-camera-ready gap was twelve days (January 13 to January 25, 2026) — short enough that de-anonymization, rights forms, registration, and artifact deposit must be prepared before the decision arrives. Everything below is anchored to the 2026 edition; the ACM pipeline steps are the publisher's standard flow and the WWW-specific instructions arrive by email after acceptance, so treat the sequence as fixed and the details as 待核实 until that email lands.
The proceedings budget is a different shape
Accepted papers all receive the same maximum length: 12 pages, of which 8 are content pages, in the ACM Digital Library. Note what did not change from submission: the content allowance. Unlike venues that grant an extra page for addressing reviews, the 2026 Web Conference held content at 8 pages, so every rebuttal promise ("we will add baseline B to Table 2") must be paid for by cutting something. Budget the cuts when writing the rebuttal, not after acceptance.
| Task | Depends on | Can be done before notification? |
|---|---|---|
| De-anonymized source with author block | acmart, no anonymous option | Yes — keep a parallel branch |
| Acknowledgements + funding numbers restored | grant records | Yes |
| Rebuttal-promised edits drafted | review packet | Yes |
| ACM e-rights form | acceptance email | No — but decide licensing stance now |
| TAPS source upload and HTML/PDF proof check | e-rights completion | No |
| Author registration | fee schedule | Decide payer now |
| Artifact deposit + badge application | camera-ready deadline | Yes — deposit early |
De-anonymization sweep
Reverse every anonymity edit deliberately; half-reversed papers are the classic failure. Check: author block and ORCIDs (ACM requires ORCIDs for the publishing workflow — have every co-author's ready), acknowledgements, grant numbers, third-person self-citations back to first person where natural, dataset names that were masked ("a large e-commerce platform" → the real name, if the data agreement permits naming it), and repository links now pointing at the real, non-anonymous archive.
# Sanity greps on the de-anonymized LaTeX before TAPS upload
grep -rn "anonymous\|Anonymized\|redacted\|our institution" *.tex # leftovers
grep -rn "\\\\documentclass" main.tex # 'anonymous' and 'review' options removed?
grep -c "orcid" main.tex # one per author expected in acmart
pdfinfo main.pdf | grep -i "author\|title" # metadata restored, not "anonymous"ACM production pipeline (e-rights → TAPS → DL)
- e-rights: the corresponding author receives the ACM rights form. The choice
set (copyright transfer, licence, or open access under ACM Open) determines what
appears in the copyright block — the
\setcopyright{...}and conference metadata commands in the final source must match the form, or TAPS bounces the paper. - TAPS (The ACM Publishing System) compiles your source, not your PDF, and emits both PDF and responsive HTML for the Digital Library. Non-standard packages, hand-positioned floats, and bitmap-only figures are the usual casualties; run the source through TAPS early in the window and read the HTML rendering, which is what many readers will actually see.
- ACM Open exposure: whether an APC applies depends on the corresponding author's institutional agreement with ACM; amounts, waivers, and any subsidy for the 2026 volume were not verifiable when this pack was built — check the acceptance email and https://www.acm.org/publications/openaccess before assuming either "free" or a specific fee.
Registration and presentation
At least one author registering is the norm for ACM proceedings venues, and the 2026 edition's postponement announcement explicitly extended the author registration deadline to March 30, 2026 — evidence that author registration was a tracked obligation. The postponement also promised a format decision (in-person vs. hybrid) "by May," so presentation-mode rules for 2026 were genuinely fluid; whatever edition you are in, get the current attendance rule in writing from the official site rather than from precedent.
Show full SKILL.md (315 more words)Show less
The artifact rider
Artifact badging submissions were due together with the camera-ready in 2026.
If the paper has a dataset, model, or code artifact, run webconf-artifact-evaluation
in parallel with this checklist — the archival deposit (DOI-bearing repository, not
a bare GitHub URL) takes longer than the badge form. The final paper should cite
the deposited artifact's persistent identifier, which means the deposit must exist
before the final PDF freezes.
Edge cases the twelve days do not forgive
- Author corrections after the freeze. The submission-time freeze allowed only spelling and affiliation fixes; a co-author who changed institutions between October and January updates their affiliation now, but a missing contributor cannot be added at camera-ready either — that door closed at the abstract deadline, and pleading at production time fails.
- The masked platform that must stay masked. If the data agreement never permitted naming the platform, the camera-ready keeps the anonymized description permanently. Decide this with the data owner before acceptance; legal review does not fit in twelve days.
- Postponement fallout. The 2026 edition moved its dates after camera-ready closed. Published papers were unaffected, but visa letters, talk scheduling, and registration transfers all reopened. Keep the team's travel plans decoupled from the publication pipeline — the paper is done when TAPS accepts it.
- The rebuttal promise that no longer fits. If a promised addition cannot be honored within 8 content pages, honor its substance in condensed form and note the full version in the artifact. Silently dropping a commitment that reviewers conditioned acceptance on is the one camera-ready sin with reputation cost.
Twelve-day sequence
- Days 1-2: e-rights form; lock licensing; start registration.
- Days 3-6: apply rebuttal-promised edits inside the 8-content-page budget; de-anonymization sweep; artifact deposit finalized, DOI cited in the paper.
- Days 7-9: TAPS upload; fix compile and HTML-rendering issues.
- Days 10-12: proof-read TAPS output (PDF and HTML), submit badge application, confirm registration receipt.
Output format
[Camera-ready status] on track / blocked
[Budget] content=<n>/8, total=<n>/12; rebuttal promises paid for: yes/no
[De-anonymization] author block / acks / self-citations / data names / metadata
[ACM pipeline] e-rights done? TAPS compiled? HTML proof read?
[Money] registration state; ACM Open status (verified / 待核实)
[Artifact rider] deposit DOI in paper: yes / no / N-A© 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 The-Web-Conference-Skills/skills/webconf-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Webconf 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 |
|---|---|---|---|---|---|---|
| Webconf 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 | |
| Release PreparationCherryHQ/cherry-studio | 52k | — | ~4.3k | Automated safety check: Pass | AGPL-3.0 | |
| Prepare Paperclip PRpaperclipai/paperclip | 99k | — | ~954 | Automated safety check: Pass | MIT | |
| Prepare MCP Integrationpaperclipai/paperclip | 99k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Frost Sequence Camera Orbitheygen-com/hyperframes | 59k | 1 repos | ~9.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
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.
Prepare Paperclip PR
paperclipai/paperclip
Prepare a Paperclip branch for PR with commits, template body, and checks.
Prepare MCP Integration
paperclipai/paperclip
Prepare MCP/vendor integrations through cited research, a content PR, exact-revision human approval, and one governed Paperclip connector PR per approved connection.
Frost Sequence Camera Orbit
heygen-com/hyperframes
A ready-made HyperFrames video block where an orbiting camera follows an ice logo that shatters, reforms into two text lines and fades, at 1920×1080.
Prepare PR
mengxi-ream/read-frog
Prepare all work before creating a pull request, optionally for the issue provided as argument
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 Webconf Camera Ready
What does Webconf Camera Ready do?
A skill your agent uses when preparing a Web Conference (WWW) camera-ready after acceptance, covering the uniform 12-page/8-content proceedings budget, de-anonymization and restored…. Webconf Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing a Web Conference (WWW) camera-ready after acceptance, covering the uniform 12-page/8-content proceedings budget, de-anonymization and restored acknowledgements, ACM e-rights and TAPS production, ACM Open cost exposure, author registration, and the artifact-badging submission that rides along with the final files.
When should I use Webconf Camera Ready?
Webconf Camera Ready fits situations like: preparing a Web Conference (WWW) camera-ready after acceptance; covering the uniform 12-page/8-content proceedings budget; de-anonymization and restored acknowledgements; ACM e-rights and TAPS production.
How do I install Webconf Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-camera-ready -a claude-code`. Or copy the skill folder (The-Web-Conference-Skills/skills/webconf-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/webconf-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Webconf Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-camera-ready -a codex`. Or copy the skill folder (The-Web-Conference-Skills/skills/webconf-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/webconf-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Webconf 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 webconf-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/webconf-camera-ready, .gemini/skills/webconf-camera-ready, .github/skills/webconf-camera-ready and .opencode/skills/webconf-camera-ready in your project.
What does Webconf Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Webconf Camera Ready is instructions for the agent only.
Does Webconf Camera Ready access the network?
SKILL.md names 1 domain. As links in the text: acm.org. This is read from the text; nothing was executed.
Is Webconf 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 Webconf Camera Ready use?
Webconf 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 Webconf 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 Webconf Camera Ready?
Skills that share tags, products or a category with Webconf Camera Ready: Audit Preparation (sickn33/agentic-awesome-skills, 47k stars), Release Preparation (CherryHQ/cherry-studio, 52k stars), Prepare Paperclip PR (paperclipai/paperclip, 99k stars) and Prepare MCP Integration (paperclipai/paperclip, 99k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Webconf Camera Ready?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.