icassp-camera-ready
Use when preparing an accepted ICASSP paper for IEEE Xplore publication, covering the final 4+1 PDF, IEEE PDF eXpress validation, the IEEE electronic copyright form, integrating reviewer-requested fixes without changing the accepted claim, registration and in-person presentation, and choosing open-access options for the proceedings paper.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-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.
# ICASSP Camera Ready Use this after acceptance. Reopen the current ICASSP camera-ready instructions, the IEEE author kit, PDF eXpress, the copyright-form flow, and the registration and presentation pages before advising authors. Because ICASSP is single-blind, there is **no de-anonymization step** — the work is mostly compliance and polishing, not identity restoration. ## Camera-ready audit - Apply the final format. ICASSP stays at the **4+1** shape for camera-ready in recent cycles; confirm the current page rule rather than assuming an extra page appeared. - Run the final PDF through **IEEE PDF eXpress** to produce an Xplore-compatible file with fonts embedded; the portal rejects non-conforming PDFs. - Complete the **IEEE electronic copyright form (eCF)**; without it the paper cannot enter Xplore. - Fold in reviewer and committee fixes **without changing the accepted contribution** beyond normal clarification — camera-ready is not a place to add a new claim the reviewers never saw. - Confirm the title, author list, affiliations, and metadata exactly match what registration and Xplore will index. ## What changes from submission to camera-ready | Element | Submission | Camera-ready
- Camera-ready audit
- What changes from submission to camera-ready
- Integrating a reviewer fix (worked example)
- Registration and presentation
- Open-access and publication path
- Final checklist
- Currency note
What does the icassp-camera-ready skill do?
Use when preparing an accepted ICASSP paper for IEEE Xplore publication, covering the final 4+1 PDF, IEEE PDF eXpress validation, the IEEE electronic copyright form, integrating reviewer-requested fixes without changing the accepted claim, registration and in-person presentation, and choosing open-access options for the proceedings paper.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-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.