mobisys-workflow
Use when planning a MobiSys project timeline backward from the single early-December paper deadline through registration, two-round review with an early-reject cut, the rebuttal, notification, artifact evaluation, camera-ready, and the June conference — with device-experiment lead time built in and the one-deadline-per-year risk made explicit.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-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.
# MobiSys Workflow Use this as the project-management skill for a MobiSys submission. Replace every date with the current official timetable and work backward from the one hard December cutoff on the `mobisys<yy>.hotcrp.com/deadlines` page. MobiSys is a conference, not a journal: no standing editor-in-chief, no article-processing charge. The rotating leadership is the per-edition General Chairs and Program Chairs (2026 General Chairs: Fahim Kawsar and Cecilia Mascolo; Program Chairs 待核实). Committees rotate yearly — re-check the current organizing-committee page rather than carrying a name forward. ## The one-deadline calendar Unlike MobiCom and NSDI, which run two deadlines a year, **MobiSys runs a single paper deadline in early December feeding the following June conference**. There is no second gate this cycle to catch a slip. That single fact governs the whole plan: the device experiments must be finished, not started, before December. ## Milestones - Venue fit: confirm the contribution is a mobile/embedded *system* whose device behavior is the result (`mobisys-topic-selection`). - Evidence lock: freeze the system design and finish the on-device measurement campaign — energy, la
- The one-deadline calendar
- Milestones
- Backward plan from the December deadline
- Failure modes by stage
- Coordination notes
- Output format
What does the mobisys-workflow skill do?
Use when planning a MobiSys project timeline backward from the single early-December paper deadline through registration, two-round review with an early-reject cut, the rebuttal, notification, artifact evaluation, camera-ready, and the June conference — with device-experiment lead time built in and the one-deadline-per-year risk made explicit.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-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.