response-to-referee

Parse reviewer comments and manuscript content to generate point-by-point LaTeX rebuttals.

71|18|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/Science-Discovery/Aether --skill response-to-referee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: response-to-referee
Source: https://github.com/Science-Discovery/Aether/tree/main/.opencode/skills/response-to-referee
Command: npx skills add https://github.com/Science-Discovery/Aether --skill response-to-referee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate professional point-by-point responses to academic peer review comments and revise the manuscript accordingly. Use when the user needs to respond to referee/reviewer comments on a journal submission, conference paper, or any peer-reviewed manuscript. Combines the original paper content with reviewer feedback to produce polite, objective, evidence-based responses. Supports two-gate user approval: first for the response document, then for paper modifications. Outputs a LaTeX file using the three-part structure (The referee wrote / Our reply / Changes).

Core Features & Use Cases

  • Role: You are a Senior Reviewer Turned Author with deep familiarity with the peer review process and academic writing. You craft responses that are respectful, evidence-based, and effective.
  • Constraints: Only respond to issues the reviewer explicitly raises; never modify the paper without explicit consent; trace every claim to paper content or cited literature.
  • Workflow: Collect input, analyze reviewer points, draft point-by-point replies, and generate LaTeX outputs for changes. Two-gate approval ensures authors sign off before changes are made.

Quick Start

Input the reviewer comments and manuscript details, then generate a LaTeX reply file outlining responses and required changes.

Frequently Asked Questions about response-to-referee

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a point-by-point response to peer review comments for a journal submission?▼

To write a point-by-point response to peer review comments, parse reviewer feedback and manuscript content to generate evidence-based rebuttals. This produces a LaTeX reply file using a three-part structure: the referee wrote, our reply, and changes, aligned with journal conventions.

Can I generate a LaTeX rebuttal letter that documents manuscript changes for reviewers?▼

Yes, you can generate a LaTeX rebuttal letter that documents manuscript changes by structuring responses into a formatted file. It traces claims to paper content or citations and references precise locations for planned modifications within a changes section.

What is the best way to ensure my reviewer response only addresses explicitly raised issues?▼

The best way to ensure your reviewer response only addresses explicitly raised issues is to use a constrained workflow that restricts replies to reviewer points. It traces every justification back to manuscript content and never modifies the paper without explicit consent.

How does the two-gate approval workflow work for manuscript revision?▼

The two-gate approval workflow for manuscript revision requires author sign-off at two stages: first for the drafted response document, and second for the proposed paper modifications. This ensures authors maintain control over all changes before the final LaTeX output is generated.

Do I need to provide my full manuscript text to get evidence-based replies to referee comments?▼

Yes, you need to provide your full manuscript text alongside the reviewer comments to generate evidence-based replies. The system uses the manuscript content to justify responses with citations and document the exact locations of planned changes.

When should I not use an automated reviewer response generator for my academic paper?▼

You should not use an automated reviewer response generator when you need to introduce new arguments outside the reviewer's explicit scope, or when your response format requires a non-LaTeX output. It only responds to raised issues and produces LaTeX formatted files.