mobicom-camera-ready
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-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.
# 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
- De-anonymize deliberately
- Discharge every review promise
- Format holds at 12 double-column pages
- ACM rights, metadata, and badges
- Plan the in-person talk
- Final checklist
- Output format
What does the mobicom-camera-ready skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-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.