icassp-related-work
Use when positioning an ICASSP submission across the signal-processing literature — IEEE SPS journals (TSP, TASLP, SPL, TIP and siblings), sibling conferences (Interspeech, ICIP, EUSIPCO, WASPAA), and ML venues, citing normally under single-blind review, and sharpening the technical delta against the nearest current-cycle work in four pages.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-related-work --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 Related Work Use this to audit novelty and positioning. ICASSP is single-blind, so you **cite normally** — no anonymized references, no hiding your own prior work. Reopen the current call only for dual-submission and prior-publication rules. The four-page limit makes related work a precision instrument, not a survey. ## Positioning checks - Separate the **signal-processing novelty** (a new estimator, transform, representation, objective, architecture, or resource) from an engineering improvement. - Compare against both the **IEEE SPS journal** literature and the **conference** literature; a reviewer from the relevant technical committee knows both. - Position against the **nearest current-cycle work**, not a five-year-old baseline; ICASSP reviewers work in the subfield and notice a stale comparison immediately. - Because review is single-blind, cite your own prior work in normal first person and make the incremental delta explicit rather than obscuring it. ## Literature lanes table | Lane | Typical venues | What ICASSP reviewers check | |---|---|---| | SPS journals | IEEE TSP, TASLP, SPL, TIP, TIFS, TMM, TCI, TSIPN, JSTSP, OJSP | Whether the closest journal result is ackno
- Positioning checks
- Literature lanes table
- The sibling-venue attribution trap
- Positioning vignette
- Concurrent-work judgment
- Output format
What does the icassp-related-work skill do?
Use when positioning an ICASSP submission across the signal-processing literature — IEEE SPS journals (TSP, TASLP, SPL, TIP and siblings), sibling conferences (Interspeech, ICIP, EUSIPCO, WASPAA), and ML venues, citing normally under single-blind review, and sharpening the technical delta against the nearest current-cycle work in four pages.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-related-work --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.