vldb-submission
Use when auditing a PVLDB submission before a monthly deadline, covering the mandatory abstract on the 25th, the CMT window, the 1st-of-month 5:00 PM Pacific cutoff, category and page-budget choice, single-blind cover-page requirements, the per-month and per-year author caps, and desk-reject hazards specific to VLDB.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-submission --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 Submission Run this in the two weeks before a PVLDB monthly deadline. VLDB research papers enter through PVLDB (Proceedings of the VLDB Endowment), and the volume's own guidelines page — not the conference site's summary — is the governing document. Everything dated below was checked 2026-07-08; reopen the live volume page first. ## The three clocks of one deadline PVLDB splits a single submission across three dates, and missing the first one kills the cycle quietly: 1. **20th of the prior month** — CMT opens for the cycle. 2. **25th of the prior month** — mandatory abstract (title, authors, abstract, subject areas) registered in CMT. No abstract, no paper slot. 3. **1st of the month, 5:00 PM Pacific Time** — full paper due. This is a Pacific-clock deadline, not AoE; for most of the world it lands in the middle of the night *before* the date your calendar shows. No extensions. ## Category and budget check Pick the category deliberately — reviewers calibrate expectations to it: | Category (VLDB 2026 cycle) | Body budget | What reviewers expect | |---|---|---| | Regular Research | 12 pp + refs | New technique with systems evidence | | Experiment, Analysis & Benchmark | 12 pp +
- The three clocks of one deadline
- Category and budget check
- Identity and caps
- Pre-deadline audit sequence
- What draws a desk rejection here
- Output format
What does the vldb-submission skill do?
Use when auditing a PVLDB submission before a monthly deadline, covering the mandatory abstract on the 25th, the CMT window, the 1st-of-month 5:00 PM Pacific cutoff, category and page-budget choice, single-blind cover-page requirements, the per-month and per-year author caps, and desk-reject hazards specific to VLDB.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-submission --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 984 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.