mobicom-submission
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-submission --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.
# MobiCom Submission Work this list from the mistakes you cannot take back toward the ones you can: pick the wrong round and the paper is simply gone; a format or blindness slip is recoverable only before upload. The numbers are the MobiCom 2026 cycle as rendered on 2026-07-09; whatever the live HotCRP `/deadlines` page says for your round wins over anything printed here. ## Step 1: right site, right round, right clock MobiCom runs a **per-edition HotCRP site** (`mobicom<yy>.hotcrp.com`) with **two rounds a year**, and the rounds feed different editions. Before anything, confirm three things on the `/deadlines` page: - **Which round** is open (winter/spring or summer/fall) and **which edition it feeds** — the summer round after MobiCom 2026 competes for MobiCom 2027, not the 2026 program. - The **abstract-registration** date, which precedes the paper upload by about a week. - The **paper** cutoff and that it is **AoE**. MobiCom's winter round printed 7:59 am EDT for an 11:59 pm AoE deadline — the clock on the page is not your local midnight. Compute each coauthor's local time from the page. The abstract step gates the paper step: miss the earlier date and HotCRP will not let you up
- Step 1: right site, right round, right clock
- Step 2: format
- Step 3: blindness
- Step 4: policy
- HotCRP form fields deserve the same audit as the PDF
- Final sequence
- Output format
Mechanical pass on the exact upload candidate pdftotext final.pdf - | grep -nEi '(acknowledg|funded by|grant|@[a-z]+\.(com|edu))' | head pdfinfo final.pdf | grep -Ei 'author|creator' # PDF metadata identity grep -rnEi '(github\.com/[a-z0-9-]+|/home/|/Users/)' *.tex figures/ | head wireless giveaways: named testbed, building, deployment site, IRB/site IDs pdftotext final.pdf - | grep -niE '(our (building|campus|testbed)|room [0-9]|IRB #?[0-9])' | head
What does the mobicom-submission skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-submission --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.