A skill your agent uses when drafting an ICSE author response or executing a Major Revision, covering criterion-targeted replies to research-track reviews, the September response window, the…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-author-response .claude/skills/icse-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 "icse-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-author-response into .claude/skills/icse-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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/ICSE-Skills/skills/icse-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 icse-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-author-response .agents/skills/icse-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 "icse-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-author-response into .agents/skills/icse-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-author-response .cursor/skills/icse-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 "icse-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-author-response into .cursor/skills/icse-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 ICSE-Skills/skills/icse-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 icse-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-author-response .gemini/skills/icse-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 "icse-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-author-response into .gemini/skills/icse-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-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 icse-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/ICSE-Skills/skills/icse-author-response .github/skills/icse-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 "icse-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-author-response into .github/skills/icse-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-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 icse-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/ICSE-Skills/skills/icse-author-response .opencode/skills/icse-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 "icse-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-author-response into .opencode/skills/icse-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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.
icse-author-responseA skill your agent uses when drafting an ICSE author response or executing a Major Revision, covering criterion-targeted replies to research-track reviews, the September response window, the…
Icse Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting an ICSE author response or executing a Major Revision, covering criterion-targeted replies to research-track reviews, the September response window, the four-week revision sprint to the November deadline, response-letter structure, and change tracking that survives PC re-review.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Icse Author Response loads about 1.6k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 718 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.
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.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 718 words, ~1,553 tokens.
.claude/skills/icse-author-response/SKILL.md (or your agent's skills folder).ICSE gives authors two distinct speaking turns, and they demand different documents. The author response (September in the 2027 cycle, checked 2026-07-08) answers reviews before first decisions; the Major Revision response letter (revision due November 17, 2026; final decision December 18) accompanies a changed paper re-read by the same reviewers. Do not write the first as if it were the second.
You are writing for the PC discussion, not for your own catharsis. Three moves earn their space:
Map every reply to the criterion it defends. ICSE reviews are structured around novelty, rigor, relevance, and verifiability/transparency — a response that answers a rigor objection with a relevance argument reads as evasion.
| Objection pattern | Criterion under attack | Response that works |
|---|---|---|
| "Delta over [X] unclear" | Novelty | One-paragraph contrast: what X cannot do, with citation and evidence pointer |
| "Only N subjects / projects" | Rigor | Justify N against comparable published studies; show per-subject variance |
| "Why would practitioners care?" | Relevance | Concrete failure cost, practitioner quote, or deployment context from the paper |
| "Cannot tell how the tool works" | Verifiability | Point to artifact + name the exact section/README that answers it |
| "Threats section is boilerplate" | Rigor | Name the one threat that genuinely worries you and the mitigation you ran |
Response mechanics for the current cycle (length cap, structured forms, whether revised PDFs are allowed) were not published at check time — 待核实 on the HotCRP site when the window opens. Draft to fit the tightest historical norm: short, numbered, no new-contribution smuggling.
A Major Revision at ICSE is an itemized contract. The meta-review or reviews enumerate required changes; December's decision largely reduces to whether each item is verifiably addressed. The four-week window (Oct 20 notification → Nov 17 revision in 2027) sets the feasibility bar for what you promise.
Structure the response letter as a ledger:
# Response to Reviews — Submission #NNN (Major Revision)
## Summary of changes
Three sentences: the big moves, in reviewer language.
## R1.1 (rigor) — "No baseline against static analysis tools."
**Change:** Added SpotBugs and Infer as baselines; new §5.3, Table 6.
**Where:** pp. 6–7, marked in blue.
## R1.2 (verifiability) — "Prompt templates not disclosed."
**Change:** Full templates now in the replication package (`prompts/`),
summarized in §4.2.
## R3.4 — "Compare on industrial code."
**Declined, with reason:** licensing prevents redistribution; we instead added
two large OSS systems (§5.1) and state the limit in Threats (§7).Rules of the ledger: every numbered reviewer point appears, including the ones you decline; every change names its section and page; declined items get a reason, never silence. Submit a diff-marked PDF if the instructions allow one — reviewers granted four weeks of their own time deserve not to hunt.
With four weeks, order work by decision impact per day:
The register that works is technical-neutral: no wounded pride, no flattery, no lawyering. Compare:
Concede real weaknesses precisely (it buys credibility for the pushbacks); push back on real errors respectfully (silence reads as agreement).
[Turn] author response / major revision
[Ledger] N reviewer points -> addressed / declined-with-reason / needs decision
[Feasibility] promised work vs days remaining to Nov 17
[Risk items] points where the December decision could still go against you© 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
Just SKILL.md in ICSE-Skills/skills/icse-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Icse 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 |
|---|---|---|---|---|---|---|
| Icse Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Executing Nist Rmf Authorization To Operatemukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT | |
| Executealirezarezvani/claude-skills | 28k | — | ~831 | Automated safety check: Pass | MIT | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Hermes Agent Skill AuthoringNousResearch/hermes-agent | 252k | — | ~3.6k | Automated safety check: Pass | MIT |
mukul975/Anthropic-Cybersecurity-Skills
Drive a federal system through the NIST Risk Management Framework (SP 800-37 Rev 2) to an Authorization to Operate (ATO): Prepare, Categorize (FIPS 199), Select a control baseline (FIPS 200 / SP…
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
alirezarezvani/claude-skills
/cs:execute <decision — Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision.
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
NousResearch/hermes-agent
Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting ACM CoNEXT author responses, covering the initial-review rebuttal and — distinctively — the one-shot "major" revision response letter that must stay…
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…
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…
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…
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…
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…
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…
A skill your agent uses when drafting an ICSE author response or executing a Major Revision, covering criterion-targeted replies to research-track reviews, the September response window, the…. Icse Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting an ICSE author response or executing a Major Revision, covering criterion-targeted replies to research-track reviews, the September response window, the four-week revision sprint to the November deadline, response-letter structure, and change tracking that survives PC re-review.
Icse Author Response fits situations like: drafting an ICSE author response; executing a Major Revision; covering criterion-targeted replies to research-track reviews; the September response window.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-author-response -a claude-code`. Or copy the skill folder (ICSE-Skills/skills/icse-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icse-author-response in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-author-response -a codex`. Or copy the skill folder (ICSE-Skills/skills/icse-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icse-author-response in your project. Codex loads it when a task matches its description.
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 icse-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/icse-author-response, .gemini/skills/icse-author-response, .github/skills/icse-author-response and .opencode/skills/icse-author-response in your project.
SKILL.md names no scripts, command-line tools or credentials: Icse Author Response is instructions for the agent only.
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.
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.
Icse 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.
About 1.6k 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.
Skills that share tags, products or a category with Icse Author Response: Executing Nist Rmf Authorization To Operate (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Execute (alirezarezvani/claude-skills, 28k stars) and Debugging Executions (n8n-io/n8n, 207k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.
