- Home
- Skills
- Technical Documentation
- Reply to Reviewers
Works with the AI Agents you already use
Reply to Reviewers
Write a response letter that reviewers can check in seconds: every comment quoted word for word, every answer tied to an exact line of the manuscript.
Free
Reply to Reviewers
Example session with this skill installed
My paper got a minor revision (demo_decision.txt). Reviewer 2 says the text at line 32 still appears separately from the Figure 1 legend. Write the response for this comment and check the line numbers against my final PDF (demo_manuscript_revised.pdf). My previous letter is demo_previous_letter.docx.
- Read your context and instructions
- Compiled the reply to reviewers
Reviewer 2, comment 2.1: response drafted and checked against the final PDF
Summary: the response is ready and its line numbers and quote are verified. Two things must be fixed before you send it: the merged legend now contains two statements that the image does not show, and two promises of your previous letter are no longer true in the new version.
1. Comments of the decision (verbatim, one row per request)
| Reviewer | Comment | Status in demo_manuscript_revised.docx |
|---|---|---|
| R1.1 | "Please cite the software used to tabulate the gene counts (Tool A, line 18)." | Not finished: only a placeholder "[ZOTERO: Tool A]" (lines 17–18), no real citation yet |
| R2.1 | "In their previous response, the authors state that the sentence on the dashed line was moved to the Figure 1 legend. The text at line 32 still appears separately from the Figure 1 legend. This needs to be edited." | Done: the sentence is now inside the legend (lines 29–32) |
| R2.2 | "Thank you for adding the units. Please make sure that every average in the next version keeps its unit (per genome)." | Not respected: line 24 "(5.6 versus 3.0)" has no unit |
2. Previous letter: promises checked against the manuscripts
| Previous letter said | Submitted version | New version | Verdict |
|---|---|---|---|
| "moved to the Figure 1 legend (lines 30–31)" | still a separate paragraph, line 32 | merged, lines 29–32 | Promise was not kept: acknowledge it |
| Section 2.3 titled "Data processing" (line 21) | "2.3. Data processing" | "2.3. Data handling" (line 20) | Contradiction: restore the title the reviewer was promised |
| "Each average is now given per genome, with the number of genomes (lines 25–26)" | yes | lost at line 24 | Contradiction, and against R2.2 |
3. Draft response
Comment 2.1. "In their previous response, the authors state that the sentence on the dashed line was moved to the Figure 1 legend. The text at line 32 still appears separately from the Figure 1 legend. This needs to be edited."
Response. We thank the reviewer for this careful check and apologise for the oversight: our previous response stated that the sentence had been moved, but it had remained a separate paragraph below the legend. It is now part of the Figure 1 legend (lines 29–32): "The dashed line marks the mean over all 20 genomes (4.2 chitinase genes per genome)."
4. Line check on the final PDF (check_letter_references.py, output unedited)
=== Line references ===
[ignored] lines 32-32 (old version)
>>> letter: …ph below the legend. It is now part of the Figure 1 legend (lines 29–32): “The da…
line 29: Figure 1. Mean number of chitinase genes per genome for each genus, drawn with Tool C
line 30: [4]. Bar color indicates the site: red bars, Site A; green bars, Site B. Error bars show the
line 31: standard deviation. The dashed line marks the mean over all 20 genomes (4.2 chitinase genes
line 32: per genome).
=== Quoted sentences ===
(the reviewers' comments quoted in the letter will appear as MISSING: this is normal; only the MANUSCRIPT sentences quoted in your answers must be OK)
MISSING: In their previous response, the authors state that the sentence on the dashed line was moved to the
OK : The dashed line marks the mean over all 20 genomes (4.2 chitinase genes per genome).
Re-read each pair: the text found must match what the letter says.
"MISSING" is the reviewer's own comment, which is expected. The manuscript sentence quoted in the answer is found word for word. Reading the four lines of the range also shows lines 30–31, where the merged legend makes two claims that the figure does not support (next section).
5. Before sending (blocking)
- The merged legend says "green bars, Site B" (line 30), but the bars are
blue. It also says "Error bars show the standard deviation", but the image has
no error bars. Correct the legend first: the letter must describe a legend that matches the figure.
- Restore "2.3. Data processing" and the unit "per genome" (with n) at line 24, then answer R1.1 with a real Zotero citation.
Next steps: apply these corrections, regenerate the PDF, re-run the line check (lines shift after each change), then write the answers to R1.1 and R2.2 the same way.
Connects securely to your tools. The creator never sees your data.
About this skill
What it does
Turns an editorial decision into a verifiable response letter.
- Lists every reviewer comment verbatim, one row per request
- Recovers what your previous letter promised and checks it against the manuscript
- Drafts humble answers: thanks, what changed, where (section + lines), the new sentence quoted exactly
- Adds an "Additional corrections" paragraph that only describes changes really present
Included
pdf_lines.py: rebuilds numbered lines from your final PDFcheck_letter_references.py: checks every "line N-M" and every quoted sentence of the letterletter_template.md: ready-to-copy letter skeleton with humble phrasing
Field-tested on a real, successful research project.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.
Requires a final PDF with line numbering. Scripts assume standard academic margin-based numbering. Manual verification of line references is still required.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 8 days ago
- Free with an Agensi account
- Software
- Python 3.9+; python-docx; pymupdf
Python