icassp-review-process
Use when reasoning about ICASSP peer review — the IEEE Signal Processing Society technical-committee pipeline, EDICS-based assignment, single-blind reviewing, the recently added short rebuttal, oral-versus-poster allocation, the roughly-even acceptance rate, and how a signal-processing decision is actually made and should be decoded.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-review-process --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 Review Process Use this to reason about review-stage strategy. Reopen the current call, paper kit, and IEEE SPS editorial and reviewer guidelines before making process claims, because the mechanics shift by cycle and are governed by the Signal Processing Society, not by a standing program. ## Process model - ICASSP review is organized by the **IEEE Signal Processing Society** through its **technical committees**; papers are routed by the **EDICS** subject category you select at submission. - Review is **single-blind**: reviewers see author identities; authors do not see reviewers. - Reviewers assess technical correctness, novelty and significance to the signal-processing community, experimental soundness with task-appropriate metrics, clarity in four pages, and reproducibility. - A **short rebuttal/author-response stage** exists in recent cycles (a recent change from ICASSP's older no-rebuttal tradition); confirm it runs this year. - Accepted papers are published in **IEEE Xplore** and presented in person, as **oral or poster**; both are full proceedings papers, and poster is not a second-class outcome. ## Who reviews here - The pool is **signal-processing practitioners an
- Process model
- Who reviews here
- Scoring leverage table
- Stage-by-stage realism
- Decoding a decision letter
- Output format
- Currency note
What does the icassp-review-process skill do?
Use when reasoning about ICASSP peer review — the IEEE Signal Processing Society technical-committee pipeline, EDICS-based assignment, single-blind reviewing, the recently added short rebuttal, oral-versus-poster allocation, the roughly-even acceptance rate, and how a signal-processing decision is actually made and should be decoded.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-review-process --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.