paper-response-to-reviewers

paper-response-to-reviewers is a skill for Claude Code, Codex from yujie-jason-zhang/polish_skill. It costs 124 tokens per session (1,563 once invoked), scanned A, original, MIT.

A guide for responding to journal or conference reviewer comments in a formal, point-by-point letter. It is aimed especially at technical papers in areas such as control, robotics, automation, aerospace, and intelligent systems.

In plain words
What is it for?
Use it to plan revisions, diagnose reviewer concerns, revise the paper, and draft or check the final response letter.
Why use it?
It helps turn reviewer feedback into specific manuscript changes and evidence-based replies. It also helps handle conflicting comments, judge how serious each concern is, and check whether revisions are sufficient.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to plan revisions, diagnose reviewer concerns, revise the paper, and draft or check the final response letter.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yujie-jason-zhang/polish_skill/paper-response-to-reviewers
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add yujie-jason-zhang/polish_skill --skill paper-response-to-reviewers
Clone the repo
git clone --depth 1 https://github.com/yujie-jason-zhang/polish_skill

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for paper-response-to-reviewers

README.md
[![agentmods](https://agentmods.dev/badge/skills/yujie-jason-zhang/polish_skill/paper-response-to-reviewers/github.svg)](https://agentmods.dev/skills/yujie-jason-zhang/polish_skill/paper-response-to-reviewers)
Your own site
<a href="https://agentmods.dev/skills/yujie-jason-zhang/polish_skill/paper-response-to-reviewers"><img src="https://agentmods.dev/badge/skills/yujie-jason-zhang/polish_skill/paper-response-to-reviewers/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for paper-response-to-reviewers

Your own site · 80×15
<a href="https://agentmods.dev/skills/yujie-jason-zhang/polish_skill/paper-response-to-reviewers"><img src="https://agentmods.dev/badge/skills/yujie-jason-zhang/polish_skill/paper-response-to-reviewers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,563 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00124 $0.01563
Opus 5 $0.00062 $0.00781
Sonnet 5 $0.00025 $0.00313
Haiku 4.5 $0.00012 $0.00156

Measured 12d ago against content hash 1fbe9f8927a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

paper-response-to-reviewers scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

paper-response-to-reviewers/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Paper Response to Reviewers

Scope

For handling journal or conference reviewer comments, especially IEEE Transactions and control, robotics, automation, aerospace, and intelligent-systems venues.

This is not a "generate the reply letter directly" template. It is a full revision loop:

understand the paper and the comments -> design the reply strategy -> revise the manuscript -> assess whether the revision suffices -> write the formal response letter -> verify locations and marked text

This skill produces the revision plan and the response letter. Editing the manuscript itself is higher-risk: have the user confirm manuscript edits, route structural rewrites to paper-argument-reconstructor, and final language to paper-polisher.

See references/response_letter_guide.md for the full severity/evidence grading, decision gates, conflicting-reviewer and multi-round handling, reply templates, and checklist. For a short reply, the core principles and rules below are enough.

Use another skill when the task is primarily:

  • the short cover letter accompanying the submission (not the detailed replies): use paper-cover-letter (if available);
  • restructuring an argument or section a reviewer attacked: use paper-argument-reconstructor (if available), then report the change here;
  • final TeX-safe polishing of the reply text: use paper-polisher (if available).

Verification Mode

This skill has two modes. By default it plans and writes the response as described above. When the input is a response letter another tool or skill has already drafted, switch to verification mode instead of regenerating:

  • do not overwrite the other tool's wording;
  • check it against this skill's rules: promised-change-to-manuscript consistency, evidence-based (not bluffed) rebuttals, softened overstatements, no S3/S4 concern answered with future work alone, and mutually consistent replies across reviewers;
  • report only the deviations and their locations; fix one in place only if it breaks a hard rule.

Read the full file on GitHub · 87 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 87 lines · 124 tokens per session scan A 1fbe9f8927a1

Subscribe to this mod's changes

paper-response-to-reviewers is a skill published in the GitHub repository yujie-jason-zhang/polish_skill (18 stars, last pushed 1mo ago), licensed MIT. It adds 124 tokens to every session and 1,563 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

academic-plotting

Generates publication-quality figures for ML papers from research context. Given a paper section or description, extracts system components and relationships to generate architecture diagrams via Gemini. Given experiment results or data, auto-selects chart type and generates data-driven figures via matplotlib/seaborn.…

Orchestra-Research/AI-Research-SKILLs · 68 tokens

systems-paper-writing

Comprehensive guide for writing systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Provides paragraph-level structural blueprints, writing patterns, venue-specific checklists, reviewer guidelines, LaTeX templates, and conference deadlines. Use this skill for all systems conference paper writing.

Orchestra-Research/AI-Research-SKILLs · 66 tokens

academic-plotting

Generates publication-quality figures for ML papers from research context. Given a paper section or description, extracts system components and relationships to generate architecture diagrams via Gemini. Given experiment results or data, auto-selects chart type and generates data-driven figures via matplotlib/seaborn.…

brycewang-stanford/Auto-Empirical-Research-Skills · 68 tokens

academic-paper-writer

Draft economics papers with proper structure and academic style.

brycewang-stanford/Auto-Empirical-Research-Skills · 14 tokens

ml-paper-writing

Write publication-ready ML/AI/Systems papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM, OSDI, NSDI, ASPLOS, SOSP. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification…

brycewang-stanford/Auto-Empirical-Research-Skills · 80 tokens

ml-paper-writing

Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.

OpenLAIR/dr-claw · 65 tokens