mobisys-camera-ready
Use when preparing an accepted MobiSys paper for the ACM Digital Library camera-ready — de-anonymization, the ACM double-column final layout and 12-page budget, ACM rights and CCS metadata, delivering any results promised in the rebuttal, coordinating the three artifact badges, registration, and the June in-person talk and demo in Cambridge.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-camera-ready --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 Camera Ready Use this after acceptance. Reopen the current camera-ready instructions, the ACM rights form, the registration page, and the decision email before advising authors — dates and forms are cycle-specific. ## Camera-ready audit - Convert the anonymous submission to the public ACM version: author names, affiliations, acknowledgements, funding, and de-anonymized code/data links. - Apply the current ACM double-column template and page budget. MobiSys 2026 kept a **12-page body including figures and tables**; references and appendices sit outside the cap — confirm the final-version rule against the current instructions. - Deliver every result **promised in the rebuttal**; a promised camera-ready experiment that never appears is a credibility failure the AC may notice. - Complete ACM rights, the CCS concepts/keywords metadata, title/abstract/author-order metadata, and the bibliography. - Coordinate the three artifact badges so passing badges are printed on the paper and recorded in the ACM DL (`mobisys-artifact-evaluation`). - Confirm registration and the June in-person obligation; MobiSys expects at least one author to present. ## What changes between the reviewed an
- Camera-ready audit
- What changes between the reviewed and final version
- De-anonymization sweep
- ACM double-column reflow
- Worked example: integrating a promised result
- Camera-ready readiness
- Hedged logistics
- Output format
What does the mobisys-camera-ready skill do?
Use when preparing an accepted MobiSys paper for the ACM Digital Library camera-ready — de-anonymization, the ACM double-column final layout and 12-page budget, ACM rights and CCS metadata, delivering any results promised in the rebuttal, coordinating the three artifact badges, registration, and the June in-person talk and demo in Cambridge.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-camera-ready --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.