Agent skill

revise

R&R cycle — classify referee comments and route to appropriate agents. Replaces /respond-to-referee.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codecan modify filesNOASSERTION
Install
npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill revise --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 2 KB
Bundled scripts: none
Allowed tools: ReadGrepGlobWriteEditTask
Path: skills/16-hsantanna88-clo-author/dot-claude/skills/revise/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 3,244
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Revise Structure point-by-point referee responses with classification, agent routing per revision protocol, and diplomatic drafting. **Input:** `$ARGUMENTS` — path to referee report file(s), optionally followed by paper path. --- ## Workflow ### Step 1: Parse Inputs 1. Read referee report(s) from `$ARGUMENTS` 2. Read the paper (paper/main.tex or specified path) 3. Read revision protocol from rules 4. Read existing scripts to know what analyses already exist ### Step 2: Classify Every Comment | Class | Routing | Action | |-------|---------|--------| | **NEW ANALYSIS** | → Coder agent | Flag for user, create analysis task | | **CLARIFICATION** | → Writer agent | Draft rewritten section | | **REWRITE** | → Writer agent | Draft structural revision | | **DISAGREE** | → User (mandatory) | Draft diplomatic pushback, flag for review | | **MINOR** | → Writer agent | Draft fix directly | ### Step 3: Build Tracking Document Save to `quality_reports/referee_response_tracker.md` with: - Summary counts per referee - Action items by priority (HIGH: new analysis, MEDIUM: clarification, FLAGGED: disagreements, LOW: minor) ### Step 4: Dispatch Agents - CLARIFICATION/REWRITE → dispatch Writer with

What's inside
Steps it walks through
  1. Workflow
  2. Step 1: Parse Inputs
  3. Step 2: Classify Every Comment
  4. Step 3: Build Tracking Document
  5. Step 4: Dispatch Agents
  6. Step 5: Draft Response Letter
  7. Step 6: Diplomatic Disagreement Protocol
  8. Step 7: Save Outputs
  9. Principles
More from Auto-Empirical-Research-Skills
All skills →
About this skill
What does the revise skill do?

R&R cycle — classify referee comments and route to appropriate agents. Replaces /respond-to-referee.

How do I install it?

Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill revise --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Auto-Empirical-Research-Skills, a repository with 3,244 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going