Individual skill

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.

ICASSP-Skills/skills/icassp-writing-style/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,411
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top