Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when planning an ICASSP project timeline — the annual clock from venue fit through the September paper deadline, single-blind review, the short winter rebuttal, spring…
Install Icassp Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icassp-workflow --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-workflow .claude/skills/icassp-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICASSP-Skills/skills/icassp-workflow into .claude/skills/icassp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icassp-workflow", 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-workflowType 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-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icassp-workflow --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-workflow .agents/skills/icassp-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICASSP-Skills/skills/icassp-workflow into .agents/skills/icassp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icassp-workflow", 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-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icassp-workflow --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-workflow .cursor/skills/icassp-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICASSP-Skills/skills/icassp-workflow into .cursor/skills/icassp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icassp-workflow", 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-workflow--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-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icassp-workflow --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-workflow .gemini/skills/icassp-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICASSP-Skills/skills/icassp-workflow into .gemini/skills/icassp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icassp-workflow", 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-workflowInstalls 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-workflow -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-workflow .github/skills/icassp-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICASSP-Skills/skills/icassp-workflow into .github/skills/icassp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icassp-workflow", 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-workflow -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-workflow --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-workflow .opencode/skills/icassp-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICASSP-Skills/skills/icassp-workflow into .opencode/skills/icassp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icassp-workflow", 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-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 500 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an ICASSP project timeline — the annual clock from venue fit through the September paper deadline, single-blind review, the short winter rebuttal, spring…
- Planning an ICASSP project timeline — the annual clock from venue fit through the September paper deadline
- SKILL.md covers The annual clock (2026-cycle…, Milestones, Backward plan from the… and Track decision (decide before…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Single-blind review
What it does
Icassp Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ICASSP project timeline — the annual clock from venue fit through the September paper deadline, single-blind review, the short winter rebuttal, spring notification, IEEE Xplore camera-ready, and the May conference — with backward-planning offsets and the choice among standard, OJSP-ICASSP, and grand-challenge tracks.
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. 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
- Planning an ICASSP project timeline — the annual clock from venue fit through the September paper deadline
- Single-blind review
- The short winter rebuttal
- Spring notification
Example prompts
- “/icassp-workflow”
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 Workflow loads about 1.2k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 500 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). 500 words, ~1,206 tokens.
Download SKILL.mdSave it as
.claude/skills/icassp-workflow/SKILL.md (or your agent's skills folder).- name
- icassp-workflow
- description
- Use when planning an ICASSP project timeline — the annual clock from venue fit through the September paper deadline, single-blind review, the short winter rebuttal, spring notification, IEEE Xplore camera-ready, and the May conference — with backward-planning offsets and the choice among standard, OJSP-ICASSP, and grand-challenge tracks.
ICASSP Workflow
Use this as the project-management skill for an ICASSP submission. Replace every date with the current official timetable and work backward from the paper deadline. ICASSP is an IEEE Signal Processing Society conference, rebuilt by a new local committee each year; it has no standing editor-in-chief, and the cost model is registration, with the proceedings paper published in IEEE Xplore.
The annual clock (2026-cycle shape, verify each year)
- September — full-paper deadline on the CMS portal (ICASSP 2026: 17 Sep 2025; ICASSP 2027 reported ~16 Sep 2026, the next major gate as of 2026-07-09).
- Autumn/early winter — single-blind technical-committee review.
- December — short rebuttal/author-response window (2026 cycle: reported to ~22 Dec 2025), if the cycle runs one.
- Late winter — notification; accepted-paper revision window (2026: to ~28 Jan 2026).
- Spring — IEEE Xplore camera-ready (PDF eXpress + IEEE copyright form), registration.
- May — the conference; in-person oral or poster presentation (ICASSP 2026 Barcelona, 4-8 May; ICASSP 2027 Toronto, 16-21 May).
Milestones
- Venue fit — confirm the contribution is genuinely signal-processing and ICASSP-routed, not a
generic-ML paper or a speech paper better suited to Interspeech (see
icassp-topic-selection). - Evidence lock — freeze the mechanism, the task-matched metric, the standard baseline, the condition sweep, and seeds.
- Paper deadline — upload the 4+1 PDF with the author list (single-blind), EDICS, and the ethical-standards statement through CMS.
- Rebuttal — if it runs, reply early and move the one decision-critical objection.
- Notification and camera-ready — integrate reviewer fixes within the accepted claim, pass PDF eXpress, sign the copyright form, register.
- Conference — present in person; ship the public artifact.
Backward plan from the September deadline
| Weeks out (heuristic) | Milestone |
|---|---|
| 8+ | Mechanism frozen; standard corpus and scorer chosen |
| 6 | Baseline reproduced on the same corpus/split/scorer |
| 4 | Condition sweep and ablation complete, seeds logged |
| 3 | Full draft sitting in the IEEE 4+1 two-column template |
| 2 | Internal mock review by a subfield-fluent colleague |
| 1 | PDF eXpress pass, author-block/ethics check, figure legibility |
| 0 | Upload via CMS; download and re-read the stored PDF |
These offsets are planning heuristics — anchor each to the current official timetable, never to a past cycle.
Show full SKILL.md (162 more words)Show less
Track decision (decide before the deadline)
Standard 4+1 -> TPC review, IEEE Xplore proceedings, in-person present
OJSP-ICASSP 8+1 -> OJSP editorial review, open-access journal, present (not in proceedings),
earlier pre-registration deadline
SPS-journal present -> already-accepted SPS-journal paper, not re-reviewed, not in proceedings
Grand Challenge -> short paper via the challenge, present, may appear in proceedingsFailure modes by stage
- Choosing the corpus or metric late forces a scramble that a subfield reviewer sees through.
- Leaving format conversion to the final week surfaces four-page overflow too late; IEEE two-column is tighter than a working draft.
- Skipping the mock review forfeits the one chance to hear "that is the wrong metric for this task" from a friend rather than a reviewer.
- Missing a track's separate earlier deadline (OJSP pre-registration, grand challenge) forecloses the best-fit path.
Coordination notes
- Assign one named owner for the CMS submission (format, EDICS, metadata) and another for the reproducibility package; shared ownership is how both slip.
- Archive the exact submitted PDF, since a rebuttal must quote it precisely.
Output format
[Current stage] idea / experiments / writing / submission / rebuttal / accepted / camera-ready
[Next official deadline] <date and source, or unknown>
[Track] standard / OJSP-ICASSP / journal-present / grand-challenge
[Critical path] <three tasks that determine readiness>
[Owner map] <task -> person or role>Currency note
The 2026-cycle dates and the ICASSP 2027 September gate were checked 2026-07-09 (see
../../resources/official-source-map.md); the 2027 exact deadline is 待核实 until its CFP is
readable directly. Nothing carries from Barcelona to Toronto automatically — re-open the current
call.
© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icassp Workflow 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 Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
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 Workflow
What does Icassp Workflow do?
A skill your agent uses when planning an ICASSP project timeline — the annual clock from venue fit through the September paper deadline, single-blind review, the short winter rebuttal, spring…. Icassp Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ICASSP project timeline — the annual clock from venue fit through the September paper deadline, single-blind review, the short winter rebuttal, spring notification, IEEE Xplore camera-ready, and the May conference — with backward-planning offsets and the choice among standard, OJSP-ICASSP, and grand-challenge tracks.
When should I use Icassp Workflow?
Icassp Workflow fits situations like: planning an ICASSP project timeline — the annual clock from venue fit through the September paper deadline; single-blind review; the short winter rebuttal; spring notification.
How do I install Icassp Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-workflow -a claude-code`. Or copy the skill folder (ICASSP-Skills/skills/icassp-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icassp-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Icassp Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-workflow -a codex`. Or copy the skill folder (ICASSP-Skills/skills/icassp-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icassp-workflow in your project. Codex loads it when a task matches its description.
Can I use Icassp Workflow 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-workflow -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-workflow, .gemini/skills/icassp-workflow, .github/skills/icassp-workflow and .opencode/skills/icassp-workflow in your project.
What does Icassp Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Icassp Workflow is instructions for the agent only.
Does Icassp Workflow 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 Workflow 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 Workflow use?
Icassp Workflow 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 Workflow use?
About 1.2k tokens (SKILL.md is roughly 4.8k 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 Workflow?
Skills that share tags, products or a category with Icassp Workflow: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icassp Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.