How do I install the Rt Response To Referees skill?

Run npx skillmds add thedixitjain/rt-response-to-referees in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rt Response To Referees safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rt Response To Referees?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rt Response To Referees free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rt Response To Referees?

thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rt Response To Referees by thedixitjain

Name: Rt Response To Referees
Rating: 4.2 (5 reviews)
Author: thedixitjain

Rt Response To Referees

Use after an R&R (or the simulated rehearsal) to turn a referee report into a point-by-point response letter plus a revision plan — editor first, every comment answered, each empirical fix backed by a real re-run via the target pack's skill and the execution bridge. Defers the venue's response format to the pack + source-map.

thedixitjain 5c1c2d2 2.6 KB Updated Sep 8, 2026 2 repo stars

File contents

Response-to-Referees (rt-response-to-referees)

Draft the reply that decides the second round. Full method: shared-resources/submission-readiness/response-to-referees.md.

When to trigger

An R&R letter has arrived and needs a point-by-point response + revision.
You want to convert rt-simulated-referee output into a rehearsed reply.

What it does

Inventory every comment (per referee + AE), tag major/minor, substantive/clarification.
Editor first — lead with the AE's decisive concerns.
Classify each response honestly: concede & fix / address partially / push back with evidence (rarely, and only when right).
Back substantive fixes with a real re-run — map each empirical comment to the pack skill + rt-execution-bridge; the number in the reply must be one you actually computed.
Write the letter — quote each comment, respond beneath it, point to the exact change.
Summarize the changes in a scannable table.

Hard rules

Editor first, then referees.
Every claimed fix corresponds to a real change/re-run; empirical claims cite a number produced via the execution bridge.
Answer every comment — none silently dropped.
Venue response format from the pack + source-map (some cap length / want a structure).
It drafts a reply; the author owns final scientific sign-off.

Output format

【Cover note to editor】how the decisive concerns were addressed
【Referee 1】R1.1 (quote) → concede&fix / partial / push-back · what changed · where · new number
【Referee 2】… 【AE】(decisive points first)
【Summary of changes】comment → change → location
【Open/declined】comments not fully addressed, with the honest reason

Anti-patterns

Silent omission; defensive tone / blanket push-back; "we addressed this" with no real edit; burying the AE's load-bearing concern.

Next: regenerate affected outputs in rt-replication-package so the package matches the revision.

Source: brycewang-stanford/Awesome-Journal-Skills → Research-Toolkit-Skills/skills/rt-response-to-referees/SKILL.md

---name: rt-response-to-refereesdescription: Use after an R&R (or the simulated rehearsal) to turn a referee report into a point-by-point response letter plus a revision plan — editor first, every comment answered, each empirical fix backed by a real re-run via the target pack's skill and the execution bridge. Defers the venue's response format to the pack + source-map.---# Response-to-Referees (rt-response-to-referees)Draft the reply that decides the second round. Full method:[`shared-resources/submission-readiness/response-to-referees.md`](../../../shared-resources/submission-readiness/response-to-referees.md).## When to trigger- An R&R letter has arrived and needs a point-by-point response + revision.- You want to convert `rt-simulated-referee` output into a rehearsed reply.## What it does1. **Inventory every comment** (per referee + AE), tag major/minor, substantive/clarification.2. **Editor first** — lead with the AE's decisive concerns.3. **Classify each response** honestly: concede & fix / address partially / push back with evidence (rarely, and only when right).4. **Back substantive fixes with a real re-run** — map each empirical comment to the pack skill + `rt-execution-bridge`; the number in the reply must be one you actually computed.5. **Write the letter** — quote each comment, respond beneath it, point to the exact change.6. **Summarize the changes** in a scannable table.## Hard rules1. **Editor first**, then referees.2. **Every claimed fix corresponds to a real change/re-run**; empirical claims cite a number produced via the execution bridge.3. **Answer every comment** — none silently dropped.4. **Venue response format from the pack + source-map** (some cap length / want a structure).5. It drafts a *reply*; the author owns final scientific sign-off.## Output format```【Cover note to editor】how the decisive concerns were addressed【Referee 1】R1.1 (quote) → concede&fix / partial / push-back · what changed · where · new number【Referee 2】… 【AE】(decisive points first)【Summary of changes】comment → change → location【Open/declined】comments not fully addressed, with the honest reason```## Anti-patterns- Silent omission; defensive tone / blanket push-back; "we addressed this" with no real edit; burying the AE's load-bearing concern.Next: regenerate affected outputs in `rt-replication-package` so the package matches the revision.---**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `Research-Toolkit-Skills/skills/rt-response-to-referees/SKILL.md`

Frequently asked questions