Agent skill · Code Review & Quality

prl-referee-strategy

Use when choosing suggested and opposed referees for a Physical Review Letters submission and pre-empting the objections APS referees are likely to raise. Plans referee handling; does not write the manuscript or the rebuttal.

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

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

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: Physical-Review-Letters-Skills/skills/prl-referee-strategy/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 Referee Strategy (prl-referee-strategy) ## When to trigger - The submission form asks for suggested / opposed referees - You want to anticipate the objections a PRL referee will raise and address them in advance - A prior Letter was bounced and you are rethinking who reviews it - You are coordinating the cover-letter referee section (see `prl-cover-letter`) ## How PRL review works (durable shape) PRL is **selective**. APS editors triage on importance + breadth, then send promising Letters to referees (commonly two or more). A referee can recommend rejection on **importance/breadth grounds even when the work is correct** — so your strategy must defend both the science *and* the venue fit. There are defined resubmission and appeal routes if you disagree (handled in `prl-revision`). ## Choosing suggested referees | Principle | Practice | |------------------------------------|------------------------------------------------------------------| | Competent on the method | Can actually judge your systematics/derivation | | Spans the breadth claim | Include someone from the neighboring field you claim to reach | | No conflict of interest | Not recent collaborators, advisors, or same-

What's inside
Steps it walks through
  1. When to trigger
  2. How PRL review works (durable shape)
  3. Choosing suggested referees
  4. Choosing opposed referees
  5. Worked example: a referee slate
  6. Reading the editor's use of your list
  7. Checklist
  8. Anti-patterns
  9. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the prl-referee-strategy skill do?

Use when choosing suggested and opposed referees for a Physical Review Letters submission and pre-empting the objections APS referees are likely to raise. Plans referee handling; does not write the manuscript or the rebuttal.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill prl-referee-strategy --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