mobisys-topic-selection
Use when deciding whether a project belongs at MobiSys — testing whether the core contribution is a mobile or embedded system, application, or service whose on-device behavior is the result, and routing wireless, sensor-network, distributed-systems, ubicomp, or early-idea misfits to MobiCom, SenSys, NSDI/OSDI, IMWUT, or HotMobile.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-topic-selection --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 Topic Selection MobiSys is the ACM SIGMOBILE venue for **mobile systems, applications, and services** — the system that runs *on* the device, not the radio underneath it. The fastest way to waste a year-long cycle is to submit a paper whose real contribution belongs one venue over. This skill is a **fit and routing** tool, not a substitute for the current CFP scope list. ## The fit test A MobiSys-shaped paper answers all four: 1. **Is the contribution a mobile or embedded *system*?** A runtime, an OS/platform mechanism, an on-device inference engine, a sensing pipeline, an offload scheduler, a mobile application or service — something built and run on the device, not an algorithm evaluated in the abstract. 2. **Does the device constraint shape the result?** If compute, energy, latency, memory, or thermal budget could be idealized away with no loss, the contribution is probably not MobiSys's. 3. **Is there on-device evidence, or a credible plan for it?** MobiSys expects real phones, wearables, or embedded boards; a simulation-only story is a fit risk (`mobisys-experiments`). 4. **Would MobiSys's systems-and-services reviewers be the right audience?** Say why in one sentenc
- The fit test
- Routing map
- Contribution-type honesty
- Common misfit patterns
- Re-routing decision
- Output format
What does the mobisys-topic-selection skill do?
Use when deciding whether a project belongs at MobiSys — testing whether the core contribution is a mobile or embedded system, application, or service whose on-device behavior is the result, and routing wireless, sensor-network, distributed-systems, ubicomp, or early-idea misfits to MobiCom, SenSys, NSDI/OSDI, IMWUT, or HotMobile.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-topic-selection --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.