Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
A skill your agent uses when reasoning about ICASSP peer review — the IEEE Signal Processing Society technical-committee pipeline, EDICS-based assignment, single-blind reviewing, the recently added…
Install Icassp Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icassp-review-process --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ICASSP-Skills/skills/icassp-review-process .claude/skills/icassp-review-process && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "icassp-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICASSP-Skills/skills/icassp-review-process into .claude/skills/icassp-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icassp-review-process", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICASSP-Skills/skills/icassp-review-processType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icassp-review-process --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ICASSP-Skills/skills/icassp-review-process .agents/skills/icassp-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "icassp-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICASSP-Skills/skills/icassp-review-process into .agents/skills/icassp-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icassp-review-process", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icassp-review-process --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ICASSP-Skills/skills/icassp-review-process .cursor/skills/icassp-review-process && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "icassp-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICASSP-Skills/skills/icassp-review-process into .cursor/skills/icassp-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icassp-review-process", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path ICASSP-Skills/skills/icassp-review-process--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icassp-review-process --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ICASSP-Skills/skills/icassp-review-process .gemini/skills/icassp-review-process && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "icassp-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICASSP-Skills/skills/icassp-review-process into .gemini/skills/icassp-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icassp-review-process", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icassp-review-processInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-review-process -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ICASSP-Skills/skills/icassp-review-process .github/skills/icassp-review-process && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "icassp-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICASSP-Skills/skills/icassp-review-process into .github/skills/icassp-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icassp-review-process", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-review-process -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icassp-review-process --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ICASSP-Skills/skills/icassp-review-process .opencode/skills/icassp-review-process && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "icassp-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICASSP-Skills/skills/icassp-review-process into .opencode/skills/icassp-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icassp-review-process", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
icassp-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 526 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about ICASSP peer review — the IEEE Signal Processing Society technical-committee pipeline, EDICS-based assignment, single-blind reviewing, the recently added…
- Reasoning about ICASSP peer review — the IEEE Signal Processing Society technical-committee pipeline
- SKILL.md covers Process model, Who reviews here, Scoring leverage table and Stage-by-stage realism, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- EDICS-based assignment
What it does
Icassp Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Peer review. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Reasoning about ICASSP peer review — the IEEE Signal Processing Society technical-committee pipeline
- EDICS-based assignment
- Single-blind reviewing
- The recently added short rebuttal
Example prompts
- “/icassp-review-process”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Icassp Review Process loads about 1.2k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 526 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 526 words, ~1,151 tokens.
Download SKILL.mdSave it as
.claude/skills/icassp-review-process/SKILL.md (or your agent's skills folder).- name
- icassp-review-process
- description
- 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.
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 and academics clustered by technical committee, so a paper is judged by people fluent in its exact task's baselines and metrics.
- Reviewers expect the field-standard metric and a current strong baseline; a novel metric or a stale baseline is caught quickly because the reviewers work in that subfield.
- Because the paper is four pages, reviewers reward a claim they can verify quickly and penalize one that hides its operating point or its comparison.
Scoring leverage table
| Review dimension | What raises it | What sinks it |
|---|---|---|
| Correctness | A clearly specified mechanism with the right signal model | Hand-waved DSP steps; undefined front-end |
| Significance | A result the subfield lacked, stated in its own terms | A generic-ML result with no signal insight |
| Evidence | Task-matched metric, strong baseline, condition sweep | Accuracy where SI-SDR belongs; one-SNR result |
| Clarity | One claim, redrawable architecture, legible figures | Four pages overloaded past legibility |
| Reproducibility | Scoring ruler and split shipped or precisely cited | Metric with no ruler, no split, no seeds |
Show full SKILL.md (203 more words)Show less
Stage-by-stage realism
- Assignment: your EDICS choice decides your reviewer pool; a mis-routed paper meets reviewers
who do not value its contribution (see
icassp-topic-selection). - Reviews: read them for what the committee will weigh, not for tone; a terse review from an expert can carry more decision weight than a long one from a mismatched reviewer.
- Rebuttal (if it runs): short and text-only; move the one decision-critical objection, do not
relitigate everything (see
icassp-author-response). - Decision: ICASSP acceptance rates have historically sat near half — competitive but not NeurIPS-scarce; a clean, correct, well-measured four pages is a strong candidate.
Decoding a decision letter
- "Interesting but incremental" usually means the delta versus a named baseline was not made explicit enough — a positioning fix, not necessarily a new experiment.
- "Insufficient evaluation" usually means a missing condition sweep or a non-standard metric, not a demand for a bigger model.
- A borderline reject on a correct paper often traces to a routing or metric-fit miss that the next cycle can repair.
Output format
[Current stage] submitted / reviews / rebuttal / decision / camera-ready
[Routing] EDICS category and whether it matched the claim
[Decision actors] technical committee / area organizers
[Likely leverage] correctness / significance / evidence / clarity / reproducibility
[Rebuttal move] <one decision-critical point, if a window exists>
[Next action] <one step>Currency note
Single-blind review, EDICS routing, the recent rebuttal, and the roughly-even acceptance rate
were checked 2026-07-09 against ICASSP 2026 renderings and SPS guidelines (see
../../resources/official-source-map.md). Any of these can change by cycle — re-verify before
relying on them.
© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in ICASSP-Skills/skills/icassp-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icassp Review Process next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Icassp Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Scholar Evaluationspacering-net/codeg | 3.9k | 11 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Academic Paper ReviewerImbad0202/academic-research-skills | 51k | — | ~11k | Automated safety check: Pass | Custom licence | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT |
Similar skills
Scholar Evaluation
spacering-net/codeg
Systematically evaluate scholarly work using the ScholarEval framework, providing structured assessment across research quality dimensions including problem formulation, methodology, analysis, and…
Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Academic Paper Reviewer
Imbad0202/academic-research-skills
Simulates a journal peer review of a manuscript with a five-seat reviewer panel, an editorial synthesizer and several review modes.
Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
Academic Research Pipeline
Imbad0202/academic-research-skills
Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Icassp Review Process
What does Icassp Review Process do?
A skill your agent uses when reasoning about ICASSP peer review — the IEEE Signal Processing Society technical-committee pipeline, EDICS-based assignment, single-blind reviewing, the recently added…. Icassp Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Icassp Review Process?
Icassp Review Process fits situations like: reasoning about ICASSP peer review — the IEEE Signal Processing Society technical-committee pipeline; EDICS-based assignment; single-blind reviewing; the recently added short rebuttal.
How do I install Icassp Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-review-process -a claude-code`. Or copy the skill folder (ICASSP-Skills/skills/icassp-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icassp-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Icassp Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-review-process -a codex`. Or copy the skill folder (ICASSP-Skills/skills/icassp-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icassp-review-process in your project. Codex loads it when a task matches its description.
Can I use Icassp Review Process in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/icassp-review-process, .gemini/skills/icassp-review-process, .github/skills/icassp-review-process and .opencode/skills/icassp-review-process in your project.
What does Icassp Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Icassp Review Process is instructions for the agent only.
Does Icassp Review Process access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Icassp Review Process safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Icassp Review Process use?
Icassp Review Process is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Icassp Review Process use?
About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Icassp Review Process?
Skills that share tags, products or a category with Icassp Review Process: Peer Review (spacering-net/codeg, 3.9k stars), Scholar Evaluation (spacering-net/codeg, 3.9k stars), Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars) and Academic Paper Reviewer (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icassp Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.