mlsys-author-response
Use when drafting MLSys author responses on OpenReview under the venue's compressed rebuttal window, prioritizing systems-reviewer objections about workload representativeness, baseline tuning, and missing measurements, deciding whether to run new experiments in days, and keeping replies anonymous and decision-focused.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-author-response --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.
# MLSys Author Response Use this when MLSys reviews land. The controlling fact about this venue's rebuttal is **time**: in the 2026 cycle, reviews were released January 12 and author responses were due January 16 — four days, including whatever new measurements you attempt. Verify the current window on the mlsys.org dates page the day reviews are scheduled, then plan hours, not weeks. ## Hour-zero triage (the four-day clock) | Window | Action | |---|---| | Hours 0-4 | All authors read all reviews once without replying; classify each point as factual error / missing measurement / scope objection / preference | | Hours 4-12 | Decide the at-most-two new experiments that are actually runnable; launch them immediately — machines, not prose, are the bottleneck | | Day 2 | Draft skeleton replies per reviewer around the launched runs; resolve internal disagreements about concessions | | Day 3 | Insert numbers as runs finish; cut everything that does not move a score | | Final hours | Anonymity and tone pass; submit well before the cutoff — OpenReview traffic spikes at deadline | A run that cannot finish by day 3 does not exist for rebuttal purposes. Promise it for the camera-ready or artif
- Hour-zero triage (the four-day clock)
- What systems reviewers actually object to
- Reply skeleton per point
- Rules and boundaries
- Prioritization when everything is on fire
- Worked triage: a typical MLSys review set
- Tone calibration
- Cycle-volatility warnings
- Output format
What does the mlsys-author-response skill do?
Use when drafting MLSys author responses on OpenReview under the venue's compressed rebuttal window, prioritizing systems-reviewer objections about workload representativeness, baseline tuning, and missing measurements, deciding whether to run new experiments in days, and keeping replies anonymous and decision-focused.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-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 984 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.