eurosys-review-process
Use when reasoning about how EuroSys decides papers — the two independent yearly rounds feeding one April conference, HotCRP double-blind reviewing, the accept/revise/reject outcome triple, the same-season resubmission ban after rejection, and community structures like the Shadow PC that shape who reviews.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-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.
# EuroSys Review Process Use this to model the decision machinery around a EuroSys submission. Facts below are the 2026/2027 cycles as rendered on 2026-07-08 from the EuroSys CFPs and conference pages; per-round mechanics (rebuttal windows, review counts, online PC meeting format) are set inside each HotCRP instance — 待核实 there. ## One conference, two juries Each EuroSys edition accepts papers through two temporally separate rounds — for 2027: spring (papers May 14, 2026 → notification August 21, 2026) and fall (papers September 24, 2026 → notification January 29, 2027). Both cohorts are published in the same proceedings and presented at the same April conference. Strategically this means: - Your competition is round-local; the PC calibrates within the round it reads. - A spring reject cannot simply "try again in the fall": the CFP bars a rejected paper from returning **until the same round of the next edition** — a full year, not one deadline. - A revision offer, by contrast, explicitly bridges rounds: revise-and-resubmit at the *subsequent* deadline, judged against the issued condition list. ## The outcome triple | Outcome | What it means | Author's next move | |---|---|---| | Ac
- One conference, two juries
- The outcome triple
- Who is reading
- What moves a PC discussion here
- A round from the author's seat
- Conduct boundaries
- Reading your reviews structurally
- Output format
What does the eurosys-review-process skill do?
Use when reasoning about how EuroSys decides papers — the two independent yearly rounds feeding one April conference, HotCRP double-blind reviewing, the accept/revise/reject outcome triple, the same-season resubmission ban after rejection, and community structures like the Shadow PC that shape who reviews.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-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.