Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Prl Referee Strategy

ASecurity

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.

1,052 stars
0 votes
0 copies
1 views
Added 6/6/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill prl-referee-strategy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prl Referee Strategy?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Prl Referee Strategy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-prl-referee-strategy/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-prl-referee-strategy)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: prl-referee-strategy
description: 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.
---

# 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-institution          |
| Constructive, not partisan         | Known for fair, rigorous reports — not for reflexive PRL gate-keeping |
| Likely to grasp the significance   | Will recognize why the result is broad, not just correct         |

Suggest a small set that *together* can vouch for both correctness and breadth. Avoid stacking your suggestions only with subfield insiders, since editors may read that as evading the breadth test.

## Choosing opposed referees

- Oppose only with a brief, **professional, factual** rationale (direct competitor with a conflict, a documented dispute). Editors discount emotional or vague objections.
- Do not over-oppose; a long opposed list signals defensiveness.

## Pre-empting the likely objections (do this in the manuscript, not just the letter)

Anticipate the standard PRL referee moves and disarm them in advance:

- **"Not broad enough / belongs in Phys. Rev. B."** → Strengthen the broad-interest framing in the opening and cover letter (`prl-results-framing`, `prl-cover-letter`).
- **"An obvious artifact could explain this."** → State the decisive control inline (`prl-methods`).
- **"Incremental over Ref. [X]."** → Make the qualitative advance explicit; cite and differentiate.
- **"Can't follow it without the SM."** → Ensure the Letter stands alone (`prl-supplementary`).
- **"Over-claimed."** → Calibrate claims to evidence (`prl-writing-style`).

## Checklist

- [ ] Suggested referees can judge both correctness and breadth
- [ ] At least one suggested referee represents the claimed neighboring audience
- [ ] No conflicts of interest among suggestions
- [ ] Opposed referees (if any) have a brief, factual, professional rationale
- [ ] The opposed list is short
- [ ] The manuscript already pre-empts the top 3 likely objections
- [ ] Cover-letter referee section is consistent with the submission form

## Anti-patterns

- Suggesting only close-network insiders (reads as breadth evasion)
- Opposing referees with emotional or unsubstantiated reasons
- A long opposed list that signals defensiveness
- Suggesting a recent collaborator (conflict) as an "independent" referee
- Ignoring the breadth objection and hoping the science alone carries it

## Output format

```
【Suggested referees】N — cover correctness + breadth?  yes / adjust
【Neighboring-field referee included】yes / add
【Conflicts checked】clean / fix
【Opposed referees】N (short) — factual rationale?  yes / fix
【Top objections pre-empted in manuscript】broad-fit / artifact / increment / stand-alone / over-claim
【Next】prl-submission (enter referees) → later prl-revision
```

> Referee count, suggestion limits, and form fields evolve — verify on the official APS / PRL author page.

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →