Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
A skill your agent uses when drafting the SODA (ACM-SIAM Symposium on Discrete Algorithms) rebuttal — the roughly three-day window between review release in early September and the response…
Install Soda Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soda-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soda-author-response --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/SODA-Skills/skills/soda-author-response .claude/skills/soda-author-response && 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 "soda-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-author-response into .claude/skills/soda-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-author-response", 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/SODA-Skills/skills/soda-author-responseType 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 soda-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soda-author-response --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/SODA-Skills/skills/soda-author-response .agents/skills/soda-author-response && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "soda-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-author-response into .agents/skills/soda-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-author-response", 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 soda-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soda-author-response --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/SODA-Skills/skills/soda-author-response .cursor/skills/soda-author-response && 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 "soda-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-author-response into .cursor/skills/soda-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-author-response", 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 SODA-Skills/skills/soda-author-response--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 soda-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soda-author-response --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/SODA-Skills/skills/soda-author-response .gemini/skills/soda-author-response && 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 "soda-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-author-response into .gemini/skills/soda-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-author-response", 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 soda-author-responseInstalls 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 soda-author-response -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/SODA-Skills/skills/soda-author-response .github/skills/soda-author-response && 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 "soda-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-author-response into .github/skills/soda-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-author-response", 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 soda-author-response -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 soda-author-response --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/SODA-Skills/skills/soda-author-response .opencode/skills/soda-author-response && 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 "soda-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-author-response into .opencode/skills/soda-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-author-response", 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
soda-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 702 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting the SODA (ACM-SIAM Symposium on Discrete Algorithms) rebuttal — the roughly three-day window between review release in early September and the response…
- Triaging referee misreadings versus real gaps
- SKILL.md covers What three days buys — and…, Preparation happens in August, Writing discipline and Response skeleton, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Writing terse theorem-anchored replies inside HotCRP without breaking lightweight double-blind rules
What it does
Soda Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting the SODA (ACM-SIAM Symposium on Discrete Algorithms) rebuttal — the roughly three-day window between review release in early September and the response deadline, triaging referee misreadings versus real gaps, and writing terse theorem-anchored replies inside HotCRP without breaking lightweight double-blind rules.
Its SKILL.md is about 1.5k 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
- Triaging referee misreadings versus real gaps
- Writing terse theorem-anchored replies inside HotCRP without breaking lightweight double-blind rules
Example prompts
- “/soda-author-response”
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
Soda Author Response loads about 1.5k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 702 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). 702 words, ~1,546 tokens.
Download SKILL.mdSave it as
.claude/skills/soda-author-response/SKILL.md (or your agent's skills folder).- name
- soda-author-response
- description
- Use when drafting the SODA (ACM-SIAM Symposium on Discrete Algorithms) rebuttal — the roughly three-day window between review release in early September and the response deadline, triaging referee misreadings versus real gaps, and writing terse theorem-anchored replies inside HotCRP without breaking lightweight double-blind rules.
SODA Author Response
SODA runs a short rebuttal, and short is the operative word. For the 2027 cycle, initial reviews reach authors by September 1, 2026 and responses are due September 4, 2026 (checked 2026-07-08 via the SIAM SODA27 submission page, read through search rendering). SODA 2026's rebuttal phase opened September 8, 2025, in a record-submission year — the window is a house institution now, not an experiment, but its exact dates, length caps, and mechanics are reset per cycle (caps for 2027: 待核实 on the HotCRP response form when it opens).
What three days buys — and what it cannot
A SODA response is not a negotiation channel. It exists so the PC can distinguish "the referee missed Lemma 4.2" from "Lemma 4.2 is actually broken" before the October decision meeting. Budget accordingly:
| Review problem | Response leverage | Play |
|---|---|---|
| Referee misread a definition or bound | High | Quote the exact line and page; one sentence of correction |
| Referee missed a proof in the back matter | High | Point to the section; the full version was submitted, so it is on record |
| "Improvement too incremental" | Low-medium | One paragraph: name the barrier the prior bound sat at and who tried |
| "Why not compare to [paper]?" | Medium | State the relationship in two sentences; concede if the comparison is due |
| Genuine bug found by the referee | Honest disclosure only | Say whether it is patchable; a false "easily fixed" burns the community's memory |
| Taste objection ("not exciting") | Near zero | Skip it; spend words where facts decide |
Preparation happens in August
Three days is enough to assemble a response only if the material already exists. Between the July submission and September 1:
- Keep a claims ledger: every theorem, its exact statement, and the page where each ingredient is proved. Misreading corrections then take minutes, not hours.
- Pre-draft the two paragraphs you can predict: the significance defense (which prior bound, which barrier) and the closest-related-paper comparison.
- Ensure all coauthors are reachable in the September 1-4 window across time zones. A rebuttal blocked on a sleeping coauthor is a self-inflicted loss.
Writing discipline
- Numbered points, referee by referee. PC members skim; a wall of prose loses the one correction that mattered.
- Anchor every reply to a line in the submitted PDF. "See Section 5.3, Lemma 5.7, page 31" is the strongest sentence a theory rebuttal can contain.
- No new theorems. A result proved after the deadline is not part of the submission; at most, note that a referee's suggested extension appears to follow and will be included in the full version.
- Stay anonymous. The lightweight double-blind rules still apply: no names, no "in our previous paper," no links to identifiable repositories.
- Concede cleanly. One honest "the referee is right; the fix is X and costs a constant factor" earns more trust than three defensive paragraphs.
Show full SKILL.md (239 more words)Show less
Response skeleton
We thank the referees. We address the substantive points.
Reviewer A
A1 (main theorem "only" improves the exponent): The previous bound of
O(n^{3/2}) [Ref 12] stood since 2015 and was stated as an open problem
in [Ref 3]. Our O(n^{4/3}) crosses the barrier identified in [Ref 12, §6].
A2 (correctness of Lemma 4.2): The referee reads d as the maximum degree;
it is the average degree (defined p.7, l.4). The claimed counterexample
has average degree 3 and satisfies the lemma.
Reviewer B
B1 (missing comparison to [X]): [X] solves the unweighted case; our
Section 2.1 reduction does not preserve weights. We will state this
explicitly in Section 1.
B2 (typo in recurrence, p.19): Correct; the exponent should read k-1.
The solution of the recurrence and all downstream bounds are unchanged.The 72-hour schedule that actually works
Multi-author rebuttals fail on coordination, not content. A schedule that has survived real September windows:
| Hour (from review release) | Action | Owner |
|---|---|---|
| 0-4 | Full read; classify each point F/L/S/C (soda-review-process) | Lead author |
| 4-12 | Claims-ledger lookups for every F and C point | Whole group, split by section |
| 12-24 | First draft, worst review first | Lead author |
| 24-36 | Technical check of every page/lemma reference against the submitted PDF | The coauthor who did blind proof-checking |
| 36-48 | Tone pass: cut defensiveness, cut anything answering an S point at length | Most senior author |
| 48-60 | Freeze; sleep on it | — |
| 60-70 | Final read against the length cap and anonymity rules; submit | Lead author |
| 70-72 | Buffer for HotCRP form surprises | Lead author |
Two structural rules: the person who verifies references must not be the person who wrote the draft, and the submission happens hours before the deadline, not minutes — the response form's mechanics (length caps, formatting) are 待核实 until the form opens, and surprises cost exactly the buffer you kept.
After the response
There is no discussion phase with referees. Decisions and final-version
instructions arrive from the PC in October (2027 cycle). If the outcome is
rejection, fold the reviews into the resubmission plan — the natural next
deadlines from a September/October SODA rejection are ITCS (if the contribution is
conceptual), STOC in early November if the fixes are fast, or ESA/ICALP in the
new year (soda-workflow has the calendar).
Output format
[Response plan] <points to answer, points to skip, concessions>
[Evidence anchors] <PDF page/lemma reference for each reply>
[Risk flags] <any reply that adds unproved claims or breaks anonymity>
[Coauthor sign-off] <who reviews the draft before the September deadline>© 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 SODA-Skills/skills/soda-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Soda Author Response 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 |
|---|---|---|---|---|---|---|
| Soda Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | 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 Soda Author Response
What does Soda Author Response do?
A skill your agent uses when drafting the SODA (ACM-SIAM Symposium on Discrete Algorithms) rebuttal — the roughly three-day window between review release in early September and the response…. Soda Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting the SODA (ACM-SIAM Symposium on Discrete Algorithms) rebuttal — the roughly three-day window between review release in early September and the response deadline, triaging referee misreadings versus real gaps, and writing terse theorem-anchored replies inside HotCRP without breaking lightweight double-blind rules.
When should I use Soda Author Response?
Soda Author Response fits situations like: triaging referee misreadings versus real gaps; writing terse theorem-anchored replies inside HotCRP without breaking lightweight double-blind rules.
How do I install Soda Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soda-author-response -a claude-code`. Or copy the skill folder (SODA-Skills/skills/soda-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/soda-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Soda Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soda-author-response -a codex`. Or copy the skill folder (SODA-Skills/skills/soda-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/soda-author-response in your project. Codex loads it when a task matches its description.
Can I use Soda Author Response 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 soda-author-response -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/soda-author-response, .gemini/skills/soda-author-response, .github/skills/soda-author-response and .opencode/skills/soda-author-response in your project.
What does Soda Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Soda Author Response is instructions for the agent only.
Does Soda Author Response 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 Soda Author Response 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 Soda Author Response use?
Soda Author Response 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 Soda Author Response use?
About 1.5k tokens (SKILL.md is roughly 6.2k 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 Soda Author Response?
Skills that share tags, products or a category with Soda Author Response: 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 Soda Author Response?
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.