vldb-camera-ready
Use when producing the final PVLDB version of an accepted VLDB paper, covering the volume-specific template, PDF/A compliance and font embedding, figure legibility floors, the availability paragraph and artifact URL, proceedings file naming and copyright steps, and planning presentation at the matching VLDB conference.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-camera-ready --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# VLDB Camera Ready Use this after a PVLDB acceptance. Publication is journal-style and fast: the paper enters a monthly PVLDB issue on vldb.org, usually well before the conference where it is presented. That speed cuts both ways — production errors go public quickly, and there is no long camera-ready season to catch them. ## Production gates - **Template**: fetch the *current* template from the volume's formatting page (`vldb.org/pvldb/volumes/<N>/formatting`). Templates carry volume-specific headers and tags; a stale copy produces wrong running heads that only the proceedings chairs will catch, late. - **PDF/A**: PVLDB has required PDF/A-compliant files (PDF/A-2 or newer in the Vol 16 instructions) with **every font embedded**, including fonts inside figures exported from plotting tools — the usual offender. Validate with a real PDF/A checker, not by eyeballing. - **Figure floor**: nothing in a figure below LaTeX `scriptsize` (Vol 16 rule). Regenerate rather than rescale. - **Naming and forms**: Vol 16 wanted `p[ID]-[lastname].pdf` plus a signed copyright form; the exact Vol 20 mechanics are 待核实 — follow the acceptance email over anything here. ## Availability paragraph Supplying
- Production gates
- Availability paragraph
- Final-pass checklist
- Conference leg
- What goes wrong here
- Output format
What does the vldb-camera-ready skill do?
Use when producing the final PVLDB version of an accepted VLDB paper, covering the volume-specific template, PDF/A compliance and font embedding, figure legibility floors, the availability paragraph and artifact URL, proceedings file naming and copyright steps, and planning presentation at the matching VLDB conference.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-camera-ready --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.