vldb-related-work
Use when positioning a PVLDB submission against prior literature, covering the deep database canon back to the 1980s VLDB proceedings, the SIGMOD/ICDE/CIDR neighborhood, concurrent work under rolling monthly deadlines, industrial and open-source systems as citable prior art, and overlap declarations for extended versions.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-related-work --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 Related Work Use this to pressure-test novelty before writing the contribution list. The database field has forty-plus years of proceedings and a reviewer pool with long memories; the classic VLDB rejection is not "compared badly" but "reinvented, without knowing it." ## The reinvention audit Before claiming a technique is new, sweep three strata: 1. **The deep canon (1975-2000)** — partitioning, replication, buffering, adaptive query processing, and materialization ideas recur under new hardware. Search old VLDB/SIGMOD proceedings and TODS for the *mechanism*, not today's terminology for it. 2. **The modern venue ring** — PVLDB itself, SIGMOD/PACMMOD, ICDE, EDBT, CIDR, plus the systems conferences (SOSP/OSDI, NSDI, EuroSys) where storage and dataflow work also lands. 3. **Running code** — features shipped in PostgreSQL, RocksDB, DuckDB, Spark, or the cloud warehouses count as prior art whether or not a paper exists. Citing a system's documentation is normal here; pretending an implemented idea is unpublished is a rejection with a hyperlink. If the mechanism existed, the honest contribution is the delta: new hardware assumptions, new scale, new workload class, or the first m
- The reinvention audit
- Lane coverage check
- Concurrency on a rolling calendar
- Extended versions and overlap
- Writing the positioning paragraphs
- Output format
What does the vldb-related-work skill do?
Use when positioning a PVLDB submission against prior literature, covering the deep database canon back to the 1980s VLDB proceedings, the SIGMOD/ICDE/CIDR neighborhood, concurrent work under rolling monthly deadlines, industrial and open-source systems as citable prior art, and overlap declarations for extended versions.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-related-work --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.