mobisys-review-process
Use when explaining or planning around MobiSys peer review — the two-round process with an early-reject cut after round 1, the round-2 rebuttal window, double-blind HotCRP mechanics, the systems-and-services reviewer pool, and decision criteria for on-device claims, so response strategy fits how MobiSys decides.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-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.
# MobiSys Review Process Use this to reason about review-stage strategy. Reopen the current CFP, the HotCRP site, and the organizing-committee page before making process claims — the mechanics are cycle-specific. ## Process model - MobiSys uses HotCRP for submission and review, with a paper-registration step preceding the paper upload and **double-blind** review (author identities hidden since 2017). - Review runs in **two rounds**. Papers that do not advance past round 1 receive an **early rejection with reviews**, so authors can re-plan before the process ends. Round-2 survivors reach reviews and a **rebuttal window**. - The rebuttal is **scope-limited**: correct factual errors and answer specific reviewer questions; new results are admissible only when directly responsive, or may be promised for camera-ready (`mobisys-author-response`). - Unlike MobiCom and NSDI, the rendered 2026 CFP describes accept/reject through the rebuttal, **not** a separate one-shot revision channel; treat any revision path as 待核实 per cycle. - Accepted papers are published in the ACM Digital Library, so camera-ready compliance and artifact badges matter as much as the initial accept. ## Who reviews here
- Process model
- Who reviews here
- Scoring leverage table
- Stage-by-stage realism
- Output format
What does the mobisys-review-process skill do?
Use when explaining or planning around MobiSys peer review — the two-round process with an early-reject cut after round 1, the round-2 rebuttal window, double-blind HotCRP mechanics, the systems-and-services reviewer pool, and decision criteria for on-device claims, so response strategy fits how MobiSys decides.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-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.