Individual skill

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.

MobiSys-Skills/skills/mobisys-topic-selection/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,392
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top