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.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-camera-ready --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Mobicom Camera Ready?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-mobicom-camera-ready)More formats (shields.io, HTML) on the badges page.
---
name: mobicom-camera-ready
description: 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.
---
# MobiCom Camera-Ready
Acceptance turns the paper from an anonymous 12-page argument into a published,
attributed ACM record. Camera-ready is where the double-blind wrapper comes off, where every
promise made during review comes due, and where ACM's publishing machinery — rights,
metadata, badges — has to be completed on a fixed clock. Treat it as an audit, not a
formatting pass.
## De-anonymize deliberately
The final version restores what the submission hid:
| Item | Action |
|---|---|
| Author names and affiliations | add in the ACM double-column author block |
| Acknowledgments and funding | restore, with correct grant numbers |
| Self-citations | convert third-person ("prior work [12]") back to first person where appropriate |
| Repository / dataset URLs | make real (they were anonymized or withheld at submission) |
| PDF metadata | set author/title fields correctly |
Do a reverse of the blindness sweep (`mobicom-submission`): confirm nothing that *should* now
be attributed is still anonymized, and nothing that should be a working link is still a
placeholder.
## Discharge every review promise
Continuing reviewers and readers hold you to the record. Before finalizing:
- Fold in every change committed in the **rebuttal** and every required item from a **one-shot
revision** (`mobicom-author-response`); a promise that silently vanishes is a credibility
loss the community remembers.
- Re-check that headline numbers in the abstract and introduction still match the final
experiments after any revision re-runs (`mobicom-experiments`).
- Keep the strongest result in the body — camera-ready is not the moment to demote it to an
appendix to make room.
## Format holds at 12 double-column pages
The final paper keeps the **double-column geometry** and the page discipline (the exact final
page allowance and any extra-page option are 待核实 — confirm on the acceptance instructions).
Figures still count; references and appendices remain outside the body cap
(`mobicom-supplementary`). Do not let de-anonymization (a longer author block, added
acknowledgments) silently push the body over.
## ACM rights, metadata, and badges
```text
Publication checklist (dates on the acceptance instructions, 待核实 per cycle):
[ ] ACM eRights form completed; correct copyright/licensing selected
[ ] title, authors, affiliations, abstract entered to match the PDF exactly
[ ] ACM classification / keywords set
[ ] artifact badges coordinated: AEC outcome reflected on the paper (Available /
Functional / Reproduced) per the artifact timeline (`mobicom-artifact-evaluation`)
[ ] camera-ready PDF passes the publisher's format validation
```
The artifact-badge timeline may run separately from the paper deadline; confirm both clocks
so a badge you earned actually appears on the published version.
## Plan the in-person talk
MobiCom 2026 is in **Austin, October 26-30, 2026**; accepted papers are presented in person
(exact presenter and registration requirements are 待核实 — read the author instructions).
Plan early:
- Designate the presenter and confirm travel and registration against the program dates.
- Build the talk around the **mechanism and its measured evidence**, the same arc as the
paper's first page (`mobicom-writing-style`) — a demo or a short over-the-air video often
lands harder than a results table.
- Prepare for the wireless-specific questions reviewers raised: channel conditions,
mobility realism, energy boundary.
## Final checklist
- [ ] De-anonymized fully; reverse blindness sweep passed.
- [ ] Every rebuttal/revision promise folded in and consistent.
- [ ] Headline numbers match final experiments.
- [ ] Double-column format holds; body within the page allowance.
- [ ] ACM rights + metadata complete; badges coordinated.
- [ ] Presenter designated; talk built on the mechanism→evidence arc.
## Output format
```text
[De-anon] author block / ack / links / metadata restored — gaps flagged
[Promises] rebuttal + revision commitments discharged? each listed
[Format] page/column check after de-anon
[Publishing] rights / metadata / badge status
[Talk] presenter + registration + demo plan
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!