edbt-supplementary
Use when deciding what belongs in an EDBT paper body versus its artifact and appendices, covering the per-shape page budget with unlimited references, the rule that decision-critical evidence stays inside the reviewed pages, and how to split a database-systems paper between body and reproducible package.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill edbt-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.
# EDBT Supplementary Use this when assembling EDBT supplementary material. The governing rule is simple and strict: **the paper must be judgeable from the reviewed pages alone.** The artifact and any appendix support the paper; they do not hold the argument. Reviewers open the artifact at their discretion, so anything the decision depends on lives in the body. ## What goes where | Content | Body (within page budget) | Artifact / appendix | |---|---|---| | The problem, contribution, and what it enables | Yes | — | | Core mechanism / system design | Yes | Full parameter grids, extra configs | | The headline results and the scope/overhead | Yes | Full result tables, secondary sweeps | | The evaluation setup a claim depends on | Named in the body | The complete harness and logs | | Workload / dataset summary + derivation | Summary + criterion | The full derivation scripts and data | | Raw logs, build scripts, containers | — | Yes | | Reproduction instructions | A pointer | The README and run scripts | If a reviewer would need to open the artifact to know whether to accept, the paper is mis-partitioned — move that evidence into the body. ## The page-budget discipline (per shape) EDBT's
- What goes where
- The page-budget discipline (per shape)
- Reproducibility-forward supplementary rules
- Appendix architecture (when the template allows in-body appendices)
- Vignette: splitting a distributed-systems paper
- Output format
What does the edbt-supplementary skill do?
Use when deciding what belongs in an EDBT paper body versus its artifact and appendices, covering the per-shape page budget with unlimited references, the rule that decision-critical evidence stays inside the reviewed pages, and how to split a database-systems paper between body and reproducible package.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill edbt-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.