Agent skill · Code Review & Quality

prl-revision

Use when responding to Physical Review Letters referee reports or editor decisions — point-by-point reply, resubmission, and the APS appeal route. Structures the response and revision; does not redraft the science from scratch.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill prl-revision --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Physical-Review-Letters-Skills/skills/prl-revision/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
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

# PRL Revision (prl-revision) ## When to trigger - One or more APS referee reports have arrived - You received an editor decision (revise / reject / reject-with-appeal-option) - You need to write a point-by-point response letter - You are weighing resubmission versus appeal versus retargeting to a PR journal ## Read the decision before drafting APS decisions vary: invitation to revise, rejection that invites resubmission, or rejection on importance/breadth. Match your strategy to the decision: | Decision | Strategy | |-------------------------------------------------------|----------------------------------------------------------------| | Revise / minor | Address every point; revise manuscript; resubmit promptly | | Reject but resubmission encouraged | Substantive revision + a response showing what changed | | Reject on importance/breadth (science sound) | Decide: strengthen breadth case + appeal, or retarget PR journal| | Reject on correctness | Fix the science or retarget; do not appeal a valid technical flaw| ## Point-by-point response structure For **each** referee comment: 1. **Quote** the comment verbatim (or faithfully paraphrase). 2. **Respond** — agree and act, or disagre

What's inside
Steps it walks through
  1. When to trigger
  2. Read the decision before drafting
  3. Point-by-point response structure
  4. Worked micro-example: a response entry
  5. Resubmission packaging
  6. Handling the breadth/importance rejection specifically
  7. Checklist
  8. Anti-patterns
  9. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the prl-revision skill do?

Use when responding to Physical Review Letters referee reports or editor decisions — point-by-point reply, resubmission, and the APS appeal route. Structures the response and revision; does not redraft the science from scratch.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill prl-revision --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/Awesome-Journal-Skills, a repository with 909 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