icassp-submission
Use when auditing an ICASSP submission before the CMS portal deadline — the IEEE 4+1 page format, the single-blind rule that the author list must appear, EDICS subject selection, the Compliance-with-Ethical-Standards statement, PDF eXpress validation, the 9-papers-per-author cap, dual-submission policy, and desk-reject triggers.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-submission --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 Submission Run this audit against the live ICASSP paper kit on the current-year CMS portal (`cmsworkshops.com/ICASSP<year>/papers.php`), not against memory. ICASSP reissues its kit each cycle, and because the whole review pipeline assumes a uniform IEEE two-column object, the format is checked mechanically at upload. The next major gate as of 2026-07-09 is the **ICASSP 2027 full-paper deadline, reported ~16 September 2026** — verify on the live 2027 call. ## The format contract: 4 + 1 An ICASSP regular paper is **4 pages** of technical content — text, figures, and references all count — with an **optional 5th page** that may hold **only** references, funding acknowledgements, and the Compliance-with-Ethical-Standards statement. Consequences to internalize: - There is **no reviewed appendix or supplement** that decides acceptance. Whatever a reviewer must see to accept the paper lives on the four content pages. - References compete with content on pages 1-4 unless they spill to page 5; plan the reference budget early. - Use the official IEEE two-column template from the paper kit with fonts, margins, and column measure untouched, and confirm the PDF passes **IEEE PDF eXpres
- The format contract: 4 + 1
- Single-blind: the inverted anonymity rule
- Portal and metadata (CMS, not CMT)
- Desk-reject and triage table
- Final 72 hours, in order
- Track choice before you submit
- Output format
- Currency note
What does the icassp-submission skill do?
Use when auditing an ICASSP submission before the CMS portal deadline — the IEEE 4+1 page format, the single-blind rule that the author list must appear, EDICS subject selection, the Compliance-with-Ethical-Standards statement, PDF eXpress validation, the 9-papers-per-author cap, dual-submission policy, and desk-reject triggers.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-submission --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.