mobicom-review-process
Use when reasoning about where a MobiCom paper sits in the two-round review process — the early-reject cut after round one, the released reviews and rebuttal window after round two, the accept / one-shot revision / reject outcome space, reviewer continuity across a revision, and how the rolling-deadline structure shapes what to do next.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-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.
# MobiCom Review Process Understanding MobiCom's review structure changes what you do at each stage. Unlike a single-verdict venue, MobiCom runs **two rounds per deadline** with an early-reject cut and a rebuttal, and then keeps a **one-shot revision** channel on top. Knowing which state you are in — and what each state affords — is the difference between a wasted rolling deadline and a converging paper. ## The stages and the outcome space ```text Submission -> Round 1 review -> EARLY REJECT (reviews returned) [use them for the next round] -> advance to Round 2 -> Round 2 review -> reviews RELEASED -> REBUTTAL window -> PC decision -> ACCEPT -> ONE-SHOT REVISION (required-changes list) -> REJECT ``` | State | What it means | What you do | |---|---|---| | Early reject | did not clear round 1; full reviews returned | mine reviews, decide next round (`mobicom-workflow`) | | Advanced | reached round 2; reviews will come with a rebuttal window | prepare to respond fast (`mobicom-author-response`) | | Accept | in the program | artifacts + camera-ready (`mobicom-camera-ready`) | | One-shot revision | conditional; a list of required changes | treat as a contract; plan the experiments | | R
- The stages and the outcome space
- The early reject is data, not just a loss
- The rebuttal window is short and fixed
- The one-shot revision is a commitment
- Reviewer continuity shapes strategy
- Confidentiality and conduct
- Output format
What does the mobicom-review-process skill do?
Use when reasoning about where a MobiCom paper sits in the two-round review process — the early-reject cut after round one, the released reviews and rebuttal window after round two, the accept / one-shot revision / reject outcome space, reviewer continuity across a revision, and how the rolling-deadline structure shapes what to do next.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-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.