vldb-workflow
Use when planning a VLDB project on the PVLDB rolling calendar, covering month-picking strategy, the volume-to-conference mapping and acceptance cutoff, budgeting a possible three-month revision, coordinating author caps across a group, and backward planning from the 25th-abstract / 1st-paper rhythm.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-workflow --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 Workflow Use this as the project-management layer. PVLDB's defining freedom — a deadline every month — is also its trap: with no scarcity forcing quality, the calendar discipline must come from you. ## Know your volume geometry first On 2026-07-08 the live volume is **Vol 20**: deadlines April 1, 2026 through March 1, 2027, feeding VLDB 2027 (Athens, Aug 23-27, 2027). Vol 19 fed VLDB 2026 (Boston, Aug 31 - Sep 4, 2026) with a June 15, 2026 acceptance cutoff; acceptances after a cutoff roll to the next conference. Re-derive this geometry from the live guidelines whenever you plan — it resets every volume. ## Month-picking, done as arithmetic The right month is computed backward from what you want, not chosen by mood: | Goal | Computation | |---|---| | Present at the volume's conference | Cutoff month − 1.5 months (review) − 3 months (possible revision) − 1.5 months (re-review) ⇒ submit roughly **6 months before the cutoff** to keep the revision path open | | Accept-or-nothing, no revision slack | Cutoff − 1.5 months, accepting that a revise verdict rolls you past it | | No conference-year preference | The month your weakest experiment is actually fixed | | Thesis or job-marke
- Know your volume geometry first
- Month-picking, done as arithmetic
- One cycle, backward from the 1st
- Revision bandwidth is a scheduling object
- Group-level calendar management
- Conference logistics tail
- Output format
What does the vldb-workflow skill do?
Use when planning a VLDB project on the PVLDB rolling calendar, covering month-picking strategy, the volume-to-conference mapping and acceptance cutoff, budgeting a possible three-month revision, coordinating author caps across a group, and backward planning from the 25th-abstract / 1st-paper rhythm.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-workflow --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.