icsme-camera-ready
Use when preparing an accepted IEEE ICSME paper for its IEEE Xplore camera-ready, covering de-anonymization, the IEEEtran two-column format and page budget, the IEEE eCopyright form, integrating the reviewer-required and author-response changes without scope creep, permanentizing data-availability links, and the ROSE-Festival artifact handoff.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-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.
# ICSME Camera Ready Use this after acceptance. ICSME research papers publish in **IEEE Xplore**, so the camera-ready is an IEEE production step. There is **no revision round**, so the camera-ready is where you fold in the changes the reviews and your author response committed to — faithfully, without strengthening claims the PC did not evaluate. Reopen the current IEEE author instructions, the decision email, and the ROSE-Festival and registration pages before advising. ## Camera-ready audit - **De-anonymize completely:** restore the author block, affiliations, acknowledgements, funding, the real tool and repository names, and the real subject-system names that double-anonymity forced you to hide or genericize. - **Apply the final format:** the IEEEtran two-column conference template, within the page budget (2026: 10 + 2 references), with any camera-ready allowance the acceptance letter states. - **Complete IEEE metadata and rights:** title/abstract, author order and affiliations, the IEEE copyright / eCopyright form, and the correct IEEE copyright notice on the first page. Add ORCID and index terms/keywords as the template requires. - **Integrate reviewer-required and author-resp
- Camera-ready audit
- De-anonymization sweep
- IEEE Xplore production checks
- Worked example: folding in an author-response commitment
- Artifact / ROSE handoff
- Hedged logistics
- Output format
What does the icsme-camera-ready skill do?
Use when preparing an accepted IEEE ICSME paper for its IEEE Xplore camera-ready, covering de-anonymization, the IEEEtran two-column format and page budget, the IEEE eCopyright form, integrating the reviewer-required and author-response changes without scope creep, permanentizing data-availability links, and the ROSE-Festival artifact handoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-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.