vldb-supplementary
Use when deciding what lives outside a PVLDB paper's page budget, covering the rule that appendices count against the limit, the extended technical report on arXiv under single-blind review, proof and algorithm placement, artifact repositories as the extra-results home, and keeping the paper self-contained for VLDB reviewers.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-supplementary --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 Supplementary Use this when the paper is overflowing its category budget. PVLDB's constraint is unusual: **references are free, but appendices are not** — every page of appendix, acknowledgement, or extra table counts inside the 12 (or 8, or 6) page limit. There is no separate supplementary upload lane to hide length in, so "supplementary material" at this venue means things that live *outside the PDF entirely*. ## The three external homes | Home | Best for | Constraint | |---|---|---| | Extended technical report (arXiv or institutional) | Full proofs, extra experiments, parameter sweeps, tuning details | Cite it from the paper by version; single-blind review makes this uncomplicated | | Artifact repository | Configs, raw results, additional plots, per-workload breakdowns | Must be tagged so cited numbers stay stable | | The paper itself | Anything a reviewer needs to *judge* the claims | The only place reviewers are obliged to look | Because PVLDB review is single-blind, posting the extended report under your own names is normal practice, not an anonymity hazard — the inverse of the double-anonymous venues in this collection. (Reconfirm the current identity policy on the li
- The three external homes
- The self-containment test
- Cut order when 14 pages must become 12
- Version discipline for external material
- Failure patterns
- Output format
What does the vldb-supplementary skill do?
Use when deciding what lives outside a PVLDB paper's page budget, covering the rule that appendices count against the limit, the extended technical report on arXiv under single-blind review, proof and algorithm placement, artifact repositories as the extra-results home, and keeping the paper self-contained for VLDB reviewers.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-supplementary --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.