edbt-writing-style
Use when revising an EDBT paper for a data-management contribution on the first page, a reproducibly described mechanism, an evaluation that survives a database-systems reviewer, honest scope, and disciplined use of the per-shape page budget (Regular / Experiments-&-Analysis / Vision) in the OpenProceedings template.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill edbt-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.
# EDBT Writing Style Use this when revising the main paper. EDBT papers are read by database-systems reviewers and published open access on OpenProceedings, so they need a **data-management contribution stated on the first page** and an evaluation a skeptic trusts. The failure this skill prevents is a technically fine paper that reads like a vague performance claim or a re-skinned ML result with a database title. ## Revision rules - **Lead with the data-management contribution:** the concrete problem (a storage, query-processing, indexing, transaction, integration, or data-quality problem), why current systems fall short, the contribution (mechanism and/or study), the evidence on real workloads, and what it enables. - **Make the mechanism reproducible in prose.** Describe the algorithm, data structures, parameters, and system integration precisely enough that a competent reader could reimplement it — vagueness here is the "I cannot tell how it works" revise. - **Pair every claim with proportional evidence** — a real workload, a tuned baseline, a measurement at realistic scale with reported variance — not adjectives like "significantly faster." - **State scope honestly, in the body.
- Revision rules
- Paper-shape skeletons
- Sentence-level rewrites
- Scope discipline
- Vignette: compressing an over-scoped systems paper
- Output format
What does the edbt-writing-style skill do?
Use when revising an EDBT paper for a data-management contribution on the first page, a reproducibly described mechanism, an evaluation that survives a database-systems reviewer, honest scope, and disciplined use of the per-shape page budget (Regular / Experiments-&-Analysis / Vision) in the OpenProceedings template.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill edbt-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.