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 Revision

ASecurity

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.

1,052 stars
0 votes
0 copies
0 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-revision --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prl Revision?

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

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

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

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

# 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 disagree with evidence.
3. **Point to the change** — name the exact location ("revised Sec. ..., new Fig. S3, added sentence in para ...").

Conventions that work with APS referees:

- Be **courteous and specific**; never dismissive, even with a hostile report.
- Quote new manuscript text in the reply so the referee sees the change without hunting.
- Mark changes in the manuscript (color or a marked-up version) per current APS practice.
- If you disagree, win on **evidence and physics**, not tone — add a control, a calculation, or a citation.
- Respect the length limit: revisions that add material must re-balance via `prl-length-management` and `prl-supplementary`.

## Handling the breadth/importance rejection specifically

This is the signature PRL outcome. Options:

- **Sharpen, don't inflate.** Make the broad-interest case concrete (`prl-results-framing`, `prl-cover-letter`) — a real cross-field consequence, not louder adjectives.
- **Appeal** through the defined APS route only if you have a substantive argument the editor/referee missed; appeals are not for re-arguing taste.
- **Retarget** to Phys. Rev. A–E / PR Research if the breadth case is genuinely weak — often the faster path to publication (`prl-scope-fit`).

## Checklist

- [ ] Every referee point has an explicit response
- [ ] Each response names the exact manuscript change location
- [ ] New text is quoted in the reply for the referee's convenience
- [ ] Disagreements are backed by evidence/physics, not tone
- [ ] A marked-up / change-highlighted manuscript is prepared
- [ ] Added material is re-balanced against the length limit
- [ ] The Letter still stands alone after revision
- [ ] If appealing, the appeal raises a substantive missed point, not taste
- [ ] If retargeting, the right PR journal is chosen via prl-scope-fit

## Anti-patterns

- A defensive or curt tone toward a difficult referee
- Claiming to have addressed a point without actually changing the text
- Adding rebuttal material that pushes the Letter over the length limit
- Appealing a sound technical rejection instead of fixing the science
- Re-arguing breadth with adjectives instead of a concrete consequence
- Letting revisions make the Letter depend on the SM

## Output format

```
【Decision type】revise / resubmit-encouraged / breadth-reject / correctness-reject
【Point-by-point】N comments — all addressed with locations?  yes / list gaps
【Tone】courteous + evidence-based?  yes / fix
【Length re-balanced after additions】yes / fix
【Stands alone after revision】yes / fix
【Path】resubmit / appeal (substantive?) / retarget via prl-scope-fit
【Next】prl-submission (resubmit) or prl-scope-fit (retarget)
```

> Decision categories, appeal procedures, and markup expectations are durable in spirit; verify the current process 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', ...

693161 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 →