mobisys-related-work
Use when positioning a MobiSys submission against the mobile-systems literature — offload, on-device ML, mobile OS and runtimes, sensing services, and energy — covering the right lanes, handling concurrent work, verifying that cited "MobiSys papers" are MobiSys rather than MobiCom/SenSys/OSDI, and self-citing without breaking double-blind.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-related-work --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 Related Work Use this to audit novelty and coverage. Reopen the current CFP for dual-submission, anonymity, and prior-publication rules before advising authors. At MobiSys the failure mode is usually a **too-narrow** related-work section that misses a sibling-venue predecessor. ## Positioning checks - Separate the **system contribution** from an engineering improvement: a new runtime mechanism, scheduling policy, on-device inference system, sensing service, or platform. - Cover the mobile-systems lanes below; a bibliography that cites only machine-learning papers tells a systems reviewer that known mobile-systems work may be getting rediscovered. - Treat ACM DL, USENIX, and IEEE proceedings as archival unless current rules say otherwise. - Cite arXiv and workshop versions in a way that preserves double-blind review; do not point reviewers to identity-revealing pages. - Use related work to sharpen what is new: a tighter energy budget, a lower latency tail, an on-device capability that previously required the cloud, or a deployment others only simulated. ## Literature lanes to sweep | Lane | Typical venues | What MobiSys reviewers check | |---|---|---| | Computation offload
- Positioning checks
- Literature lanes to sweep
- Venue-verification discipline
- Concurrent-work judgment calls
- Positioning vignette
- Output format
What does the mobisys-related-work skill do?
Use when positioning a MobiSys submission against the mobile-systems literature — offload, on-device ML, mobile OS and runtimes, sensing services, and energy — covering the right lanes, handling concurrent work, verifying that cited "MobiSys papers" are MobiSys rather than MobiCom/SenSys/OSDI, and self-citing without breaking double-blind.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-related-work --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.