Agent skill · Documentation

eurosys-author-response

Use when writing a EuroSys rebuttal or managing a one-shot revision — reading reviews against the three possible outcomes (accept, revise, reject), answering systems reviewers' measurement and design objections, and turning a revision offer's condition list into a resubmission plan for the next EuroSys deadline.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-author-response --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: EuroSys-Skills/skills/eurosys-author-response/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# EuroSys Author Response Use this once EuroSys reviews arrive, or when a revision decision lands. The decisive EuroSys fact: every submission ends as **accept, reject, or a one-shot revision offer** (EuroSys 2026/2027 CFPs, rendered 2026-07-08). A response is not just damage control — it is the input that decides which of the three bins the PC discussion puts you in. Rebuttal mechanics (window length, word caps, whether a response phase exists at all in the current round) are set per cycle in HotCRP — 待核实 against the round's own instructions before drafting. ## Read the reviews as a bin-sorting problem | Review pattern | Likely bin | Response goal | |---|---|---| | Positive scores, factual misreadings | Accept-adjacent | Correct the record crisply; give the champion ammunition | | "Promising but evaluation incomplete" | Revision candidate | Show the missing experiment is bounded and specific | | Disputed novelty or contribution | Contested | Name the delta against the exact cited system | | Fundamental design objection | Reject-adjacent | Concede scope honestly; salvage what is defensible | The revision-candidate row matters most at this venue: reviewers who believe the fix is *en

What's inside
Steps it walks through
  1. Read the reviews as a bin-sorting problem
  2. Drafting rules for systems reviewers
  3. Response skeleton
  4. If the outcome is a one-shot revision
  5. Word-budget allocation
  6. Timeline discipline
  7. What sinks responses here
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the eurosys-author-response skill do?

Use when writing a EuroSys rebuttal or managing a one-shot revision — reading reviews against the three possible outcomes (accept, revise, reject), answering systems reviewers' measurement and design objections, and turning a revision offer's condition list into a resubmission plan for the next EuroSys deadline.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-author-response --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.

Keep going