vldb-author-response
Use when a PVLDB paper receives a revision verdict and the response package must be built, covering the one-shot revision rule, the three-month window, reading the reviewers' required-changes list, planning new experiments against the clock, and writing the change document that VLDB reviewers re-evaluate against.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-author-response --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 Author Response Use this when PVLDB reviews arrive — typically around the 15th of the month after your deadline — and the verdict is **revise**. PVLDB has no rebuttal phase before decisions: the reviews and the outcome land together, so the author-response genre at this venue *is* the revision package. You get exactly one revision, and up to three months to deliver it. ## Read the verdict as a contract A PVLDB revision request is written to be specific: reviewers state what the revision must contain. Treat that list as the acceptance test. - Extract every required item into a numbered ledger before anyone starts editing; ambiguous requirements get a clarifying interpretation written down, not ignored. - Separate **required** changes from **suggested** ones. Required items decide the outcome; suggestions earn goodwill when cheap. - Estimate honestly whether the heaviest requirement — usually a new experiment or a stronger baseline — fits inside three months on your hardware. If it cannot, decide now between a scoped-down response and a withdrawal, because a failed revision consumes the only attempt. ## Budgeting the three months | Weeks | Activity | |---|---| | 1 | Ledger bui
- Read the verdict as a contract
- Budgeting the three months
- Writing the change document
- Response skeleton
- Judgment calls
- Output format
What does the vldb-author-response skill do?
Use when a PVLDB paper receives a revision verdict and the response package must be built, covering the one-shot revision rule, the three-month window, reading the reviewers' required-changes list, planning new experiments against the clock, and writing the change document that VLDB reviewers re-evaluate against.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-author-response --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.