Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
A skill your agent uses when handling reviewer feedback for an ACM/IEEE Design Automation Conference (DAC) Research Manuscript — writing a concise, evidence-first rebuttal IF the cycle runs an…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-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/DAC-Skills/skills/dac-author-response .claude/skills/dac-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 "dac-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-author-response into .claude/skills/dac-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-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/DAC-Skills/skills/dac-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 dac-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-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/DAC-Skills/skills/dac-author-response .agents/skills/dac-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 "dac-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-author-response into .agents/skills/dac-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-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 dac-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-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/DAC-Skills/skills/dac-author-response .cursor/skills/dac-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 "dac-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-author-response into .cursor/skills/dac-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-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 DAC-Skills/skills/dac-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 dac-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-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/DAC-Skills/skills/dac-author-response .gemini/skills/dac-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 "dac-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-author-response into .gemini/skills/dac-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-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 dac-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 dac-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/DAC-Skills/skills/dac-author-response .github/skills/dac-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 "dac-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-author-response into .github/skills/dac-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-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 dac-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 dac-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/DAC-Skills/skills/dac-author-response .opencode/skills/dac-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 "dac-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-author-response into .opencode/skills/dac-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-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.
dac-author-responseA skill your agent uses when handling reviewer feedback for an ACM/IEEE Design Automation Conference (DAC) Research Manuscript — writing a concise, evidence-first rebuttal IF the cycle runs an…
Dac Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when handling reviewer feedback for an ACM/IEEE Design Automation Conference (DAC) Research Manuscript — writing a concise, evidence-first rebuttal IF the cycle runs an author-response period (verify; DAC has historically not), and otherwise converting DAC reviews into a targeted response-to-reviewers when rerouting a rejected paper to ICCAD, DATE, ASP-DAC, or a journal.
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.
4 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.
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.
Dac Author Response loads about 1.2k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 531 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). 531 words, ~1,152 tokens.
.claude/skills/dac-author-response/SKILL.md (or your agent's skills folder).Handle reviews with DAC's process in mind. The single most important fact: DAC's Research-Manuscript
review has historically been TPC-driven without an author rebuttal period, and whether the
current cycle runs one is 待核实 (resources/official-source-map.md). So this skill covers two
situations, and the second is the common one.
If — and only if — the live DAC cycle offers an author response, treat it as a short, factual correction channel, not a debate. EDA reviewers reject mostly on baseline fairness, benchmark credibility, and scalability; a response moves a borderline paper when it supplies a number or corrects a factual misreading, and moves nothing when it argues taste.
Priorities for a tight EDA rebuttal (assume a strict word budget):
Do not promise experiments you cannot run before camera-ready, and do not introduce author-revealing information — the response is still within double-blind.
[Reviewer 2] "No comparison to [SOTA router]."
Response: We compare against [SOTA router] in Table 2 (columns 4-6); on the full ISPD set we reduce
overflow by X% at equal wirelength. We will make this comparison more prominent.With no response channel, the review packet arrives with the decision. The productive use of DAC reviews is then to repair the paper and reroute it well. DAC, ICCAD, DATE, and ASP-DAC share reviewer pools and criteria, so a DAC reviewer's objection is very likely to resurface at the next venue — answer it in the paper, not in a letter no one will read.
Turn the reviews into a fix list:
| DAC review objection | Fix before resubmitting elsewhere |
|---|---|
| Weak/untuned baseline | Add the strongest SOTA tool, tuned to equal effort, before ICCAD/DATE |
| Private benchmarks only | Re-run on ISPD/EPFL/ISCAS/ITC/TAU so the QoR is comparable |
| Scalability doubted | Add million-cell-scale results and runtime |
| Gain not isolated | Add the ablation the reviewer implicitly asked for |
| Incremental novelty | Extend the mechanism, or reframe honestly for a journal (TCAD/TODAES) |
Journals do run revise-and-resubmit with a point-by-point response. There, write the letter DAC
never asked for: map every reviewer point to a tracked change, quote the review, state the change,
and give the new number. That is where the discipline of ../dac-experiments pays off — a rejected
DAC paper with a strong QoR story often becomes a clean journal accept.
[Response mode] rebuttal (cycle confirmed) / no-rebuttal reroute / journal response letter
[Decision driver] baseline | benchmark | scalability | novelty | clarity
[Point map] each review point -> factual correction | evidence | conceded | reframe
[If rerouting] target venue (ICCAD/DATE/ASP-DAC/TCAD) + the top fix to make first
[Anonymity] response (if any) free of author-revealing info? yes/no© 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 DAC-Skills/skills/dac-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Dac 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 |
|---|---|---|---|---|---|---|
| Dac Author Response 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 |
spacering-net/codeg
Structured manuscript/grant review with checklist-based 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…
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.
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.
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
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.
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…
Categories
A skill your agent uses when handling reviewer feedback for an ACM/IEEE Design Automation Conference (DAC) Research Manuscript — writing a concise, evidence-first rebuttal IF the cycle runs an…. Dac Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when handling reviewer feedback for an ACM/IEEE Design Automation Conference (DAC) Research Manuscript — writing a concise, evidence-first rebuttal IF the cycle runs an author-response period (verify; DAC has historically not), and otherwise converting DAC reviews into a targeted response-to-reviewers when rerouting a rejected paper to ICCAD, DATE, ASP-DAC, or a journal.
Dac Author Response fits situations like: handling reviewer feedback for an ACM/IEEE Design Automation Conference (DAC) Research Manuscript — writing a concise; evidence-first rebuttal IF the cycle runs an author-response period (verify; DAC has historically not); otherwise converting DAC reviews into a targeted response-to-reviewers when rerouting a rejected paper to ICCAD.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-author-response -a claude-code`. Or copy the skill folder (DAC-Skills/skills/dac-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/dac-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 dac-author-response -a codex`. Or copy the skill folder (DAC-Skills/skills/dac-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/dac-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 dac-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/dac-author-response, .gemini/skills/dac-author-response, .github/skills/dac-author-response and .opencode/skills/dac-author-response in your project.
SKILL.md names no scripts, command-line tools or credentials: Dac 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.
Dac 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.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.
Skills that share tags, products or a category with Dac 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.
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.