MobiCom Skills

A 12-skill depth pack for ACM MobiCom submissions: SIGMOBILE wireless/mobile-networking venue fit, the twice-a-year rolling-deadline calendar with two-round review and rebuttal, the retained one-shot revision path, HotCRP double-blind submission audits, real-testbed and RF/energy evaluation rigor, ACM artifact badges, and double-column camera-ready. Grounded in the MobiCom 2026 and 2027-cycle offi

by @brycewang-stanford 12 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/mobicom-skills

One command, no setup. In Claude Code it lands as a managed plugin you can enable, disable or remove with /plugin. On any other agent it installs the 12 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-mobicom-skills@skillmd

Adds the marketplace once; later plugins need the second line only.

Or install by hand

Download the plugin and unzip its skills/ folder into your agent's skills directory. Works with every agent, no CLI needed.

Download plugin Paths per agent

Just the markdown? SKILL.md files only.

This plugin

skills: 12
authors: 1

Published by a registry member. Review its skills before installing.

Skills in this plugin

▌
Mobicom Workflow · brycewang-stanford
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.

1k repo stars
▌
Mobicom Submission · brycewang-stanford
Use when running the final pre-upload audit of a MobiCom submission — confirming the right per-edition HotCRP site and round, the AoE cutoff printed as an Eastern clock time, the 12-page double-column cap, the abstract-registration prerequisite, and the double-blind sweep including wireless-testbed identity leaks.

1k repo stars
▌
Mobicom Experiments · brycewang-stanford
Use when designing or auditing the evaluation of a MobiCom submission — building real-device testbeds, choosing RF and channel measurement methodology, injecting realistic mobility and interference, profiling energy on hardware, picking tuned baselines, and reporting distributions so wireless reviewers see where the mechanism wins and breaks.

1k repo stars
▌
Mobicom Camera Ready · brycewang-stanford
Use when preparing an accepted MobiCom paper for publication — de-anonymizing into the double-column final version, discharging every rebuttal and revision promise, completing ACM rights and metadata, coordinating the artifact-badge timeline, and planning the in-person presentation for the Austin program.

1k repo stars
▌
Mobicom Related Work · brycewang-stanford
Use when building or auditing the related-work of a MobiCom paper — sweeping the SIGMOBILE and networking literature lanes, proving each citation's venue on dblp/ACM DL against the INFOCOM/SIGCOMM/NSDI misattribution traps, positioning against the current rolling-cohort cohort, and self-citing without breaking double-blind.

1k repo stars
▌
Mobicom Supplementary · brycewang-stanford
Use when deciding what goes in the MobiCom 12-page double-column body versus references, optional appendices, and HotCRP fields — placing channel-model derivations, full protocols, and extended measurements outside the cap, keeping the contribution self-contained, and ensuring rebuttal and revision packets stay off the page count.

1k repo stars
▌
Mobicom Writing Style · brycewang-stanford
Use when drafting or revising a MobiCom paper for house style — putting the wireless/mobile mechanism and its operating regime on the first page, pairing every claim with over-the-air measurement, replacing superlatives with percentiles and intervals, and fitting the argument into the double-column 12-page body.

1k repo stars
▌
Mobicom Review Process · brycewang-stanford
Use when reasoning about where a MobiCom paper sits in the two-round review process — the early-reject cut after round one, the released reviews and rebuttal window after round two, the accept / one-shot revision / reject outcome space, reviewer continuity across a revision, and how the rolling-deadline structure shapes what to do next.

1k repo stars
▌
Mobicom Author Response · brycewang-stanford
Use when writing a MobiCom rebuttal after round-two reviews or executing a one-shot revision — triaging reviewer points by severity, fitting a factual, concession-honest rebuttal into its length limit, and turning a required-changes list into a change-highlighted revision with a change summary that the same reviewers can verify.

1k repo stars
▌
Mobicom Reproducibility · brycewang-stanford
Use when making a MobiCom result reproducible on a different testbed — recording radio, hardware, channel, and mobility provenance as the runs happen, characterizing the variance that over-the-air measurement introduces, and deciding early which traces, firmware, and deployment data can legally and safely ship for artifact evaluation.

1k repo stars
▌
Mobicom Topic Selection · brycewang-stanford
Use when deciding whether a project belongs at MobiCom or a sibling venue — testing whether the core contribution is a mobile/wireless-networking mechanism the SIGMOBILE flagship rewards, and routing platform, sensing, broad-networking, security, or ubicomp misfits to MobiSys, SenSys, SIGCOMM/NSDI, WiSec, or IMWUT before a cycle is committed.

1k repo stars
▌
Mobicom Artifact Evaluation · brycewang-stanford
Use when packaging a MobiCom artifact for the evaluation committee — choosing among the three ACM badges as a calibration of what you can prove, building a hardware-optional reproduction path for evaluators without radios, writing the smoke run that establishes functionality, and making code, data, and traces available.

1k repo stars