vldb-writing-style
Use when revising a PVLDB paper's prose, covering the page-one contract for systems readers, scoping performance claims to measured regimes, stating design trade-offs instead of hiding them, terminology and notation discipline across a 12-page budget, and the tone VLDB's builder-reviewers reward.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-writing-style --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 Writing Style Use this during revision passes. The PVLDB reader is a systems builder deciding, inside the first page, whether your design decision is worth their evening. Style at this venue is not ornament — it is claim hygiene. ## The page-one contract By the end of page one the reader must know: 1. **The workload that breaks current systems** — concrete, not "growing data volumes." 2. **The design decision** — the bet your system makes that others do not. 3. **What was built** — real system, extension of a named engine, or simulation; readers calibrate trust to this immediately. 4. **The headline measurement, scoped** — metric, scale, baseline, hardware class, all in one sentence. A running example introduced early and reused through design and evaluation sections is the genre's most effective device; pick one query, one tenant, one failure trace and let it carry the mechanism. ## Claim scoping table | Unscoped (review bait) | Scoped (survives) | |---|---| | "significantly faster than X" | "2.1x median speedup over X (v3.4, tuned per §6.1) on workload W at 1TB" | | "scales to large clusters" | "near-linear to 64 nodes; efficiency drops to 71% at 128 (Fig. 9)" | | "negligi
- The page-one contract
- Claim scoping table
- Trade-off candor
- Budget and terminology discipline
- Self-edit sweep
- Output format
What does the vldb-writing-style skill do?
Use when revising a PVLDB paper's prose, covering the page-one contract for systems readers, scoping performance claims to measured regimes, stating design trade-offs instead of hiding them, terminology and notation discipline across a 12-page budget, and the tone VLDB's builder-reviewers reward.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-writing-style --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.