edbt-review-process
Use when reasoning about how an EDBT research submission is evaluated, covering Microsoft CMT reviewing, the author-feedback phase, the accept / revise / reject decision, the in-cycle revise-and-resubmit second read by the original reviewers, the cycle-to-conference roll, and how EDBT's rolling model differs from SIGMOD/VLDB/ICDE and the co-located ICDT.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill edbt-review-process --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 Review Process Model the pipeline before interpreting any single review. EDBT's process is a **multiple-cycle rolling model** with a real **in-cycle revise-and-resubmit**: within one cycle, a paper is reviewed, gets an author-feedback exchange, receives **accept / revise / reject**, and — if *revise* — is revised and re-read by the same reviewers before a final accept/reject. The most consequential mental shift for authors arriving from a one-shot conference is that a *revise* is a genuine second chance inside the same cycle, not a soft rejection. ## Process model - Reviewing runs in **Microsoft CMT** (Conference Management Toolkit). Confirm the blind policy for the cycle — single- vs double-blind is decided per edition (**待核实**; EDBT has historically used author-identified single-blind reviewing). - Each paper is read by multiple program-committee members who weigh the significance of the data-management contribution, technical soundness, the fairness and honesty of the evaluation (real workloads, tuned baselines, realistic scale), reproducibility, and clarity. - The cycle includes an **author-feedback phase** on the initial reviews, then a first notification of **accept /
- Process model
- Reading a decision against the categories
- How EDBT differs from its siblings
- Who reads you
- Where author leverage actually exists
- Reading a review packet
- Misreadings to avoid
- Output format
What does the edbt-review-process skill do?
Use when reasoning about how an EDBT research submission is evaluated, covering Microsoft CMT reviewing, the author-feedback phase, the accept / revise / reject decision, the in-cycle revise-and-resubmit second read by the original reviewers, the cycle-to-conference roll, and how EDBT's rolling model differs from SIGMOD/VLDB/ICDE and the co-located ICDT.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill edbt-review-process --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.