mobicom-workflow
Use when planning a MobiCom campaign across the rolling two-deadlines-per-year calendar — deciding which round to target and which edition it feeds, building a backward schedule that leaves room for over-the-air experiments, and sequencing the two-round review, rebuttal, and one-shot revision so a slip does not silently cost an edition.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-workflow --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 Workflow MobiCom's calendar is the part authors from single-deadline venues mis-plan most. There are **two rounds a year**, each feeds a **different edition**, and inside each round the review runs in **two stages with a rebuttal**. Plan the campaign around those facts, not around a single "the deadline." ## Which round, which edition Before scheduling anything, pin two facts on the live CFP / HotCRP `/deadlines` page: - **Which edition does this round feed?** The summer/fall round opening after MobiCom 2026 competes for **MobiCom 2027**. Submitting to it is a bet on next year's program, not this year's. - **What is the AoE cutoff in local time?** MobiCom prints an Eastern clock time for an AoE deadline; convert once, for every coauthor (`mobicom-submission`). Picking the round is a research-readiness decision: the earlier round gets your work in front of reviewers sooner, but only if the over-the-air evaluation is actually done. ## Backward schedule from the paper cutoff Radio experiments do not compress the way a proof or an ablation does — testbeds break, channels drift, and volunteers for mobility runs have to be scheduled. Work backward: | Weeks before paper cutoff |
- Which round, which edition
- Backward schedule from the paper cutoff
- Inside the round: two stages plus rebuttal
- Which edition a slip costs
- During the long review silence
- Output format
What does the mobicom-workflow skill do?
Use when planning a MobiCom campaign across the rolling two-deadlines-per-year calendar — deciding which round to target and which edition it feeds, building a backward schedule that leaves room for over-the-air experiments, and sequencing the two-round review, rebuttal, and one-shot revision so a slip does not silently cost an edition.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-workflow --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.