icassp-writing-style
Use when revising an ICASSP paper into the IEEE two-column four-page house style — leading with the signal-processing contribution and mechanism, naming the task-matched metric on the first page, compressing method and results into 4+1 pages without a reviewed appendix, and writing math-forward claims that survive a subfield-expert reviewer.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-writing-style --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 Writing Style Use this when revising the main paper. An ICASSP paper is a **four-page IEEE two-column object** that must state a precise signal-processing contribution, show its mechanism, and prove it with a task-matched number — all where a busy subfield reviewer will see it. There is no reviewed appendix to rescue a buried argument. ## Revision rules - Put the **signal-processing contribution and its mechanism** on the first page: the problem, why current methods break, what block of the signal chain you change, and the metric that proves it. - Name the **task-matched metric** early (WER, SI-SDR, EER, PSNR, BER, RMSE — whatever the task uses), not a generic "accuracy" or "performance." - Make the method **redrawable**: a reader should be able to reconstruct the block diagram or the estimator from the text alone. - Use the four content pages for the core argument; push extended derivations and extra conditions to a cited technical report, since ICASSP has no reviewed supplement. - Do not overclaim beyond the conditions tested; state the operating point (SNR, corpus, scene). ## First-page arc 1. **Problem** — the signal task, in its own vocabulary. 2. **Gap** — why the st
- Revision rules
- First-page arc
- Compression discipline for four pages
- Sentence-level rewrites
- Math-forward, but honest
- Vignette: compressing into four pages
- Revision stub
- Output format
What does the icassp-writing-style skill do?
Use when revising an ICASSP paper into the IEEE two-column four-page house style — leading with the signal-processing contribution and mechanism, naming the task-matched metric on the first page, compressing method and results into 4+1 pages without a reviewed appendix, and writing math-forward claims that survive a subfield-expert reviewer.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-writing-style --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.