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 Cover Letter

ASecurity

Use when writing the cover letter for a Physical Review Letters submission, which must justify to APS editors why the work meets PRL's importance-and-broad-interest criteria. Drafts the editorial case; does not edit the manuscript itself.

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

Works with

cli

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Prl Cover Letter?

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

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

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

Download with Pro
Files
SKILL.md
---
name: prl-cover-letter
description: Use when writing the cover letter for a Physical Review Letters submission, which must justify to APS editors why the work meets PRL's importance-and-broad-interest criteria. Drafts the editorial case; does not edit the manuscript itself.
---

# PRL Cover Letter (prl-cover-letter)

## When to trigger

- You are about to submit and need the cover letter
- The editors will triage primarily on importance + broad interest, and you must make that case
- A prior submission was declined on importance/breadth grounds and you are reframing
- You need to suggest/oppose referees within the cover letter (coordinate with `prl-referee-strategy`)

## Purpose of the PRL cover letter

The cover letter's central job is to convince an APS editor — who may not be a specialist in your exact subfield — that the Letter **clears the importance + broad-interest gate** and merits review at PRL rather than at a specialized Physical Review journal. It is the breadth argument that the editor uses to decide whether to send the paper out for review at all.

It is not an abstract, not a summary, and not a place to oversell. It is a concise, specific, editor-facing case.

## Structure (concise, ~3–5 short paragraphs)

1. **Submission line** — title, that it is submitted as a Letter to PRL, and the appropriate subject area / editor track.
2. **The central result** — one or two sentences stating the single headline claim plainly, with the key number or qualitative surprise.
3. **Why it is important** — what is new: a new effect, a decisive measurement, a resolved open question, an unlocked regime. Tie it to a prior belief it changes.
4. **Why it is of broad interest** — name the communities beyond your subfield who will care and *why*. This is the paragraph editors weigh most for PRL.
5. **Housekeeping** — originality / not under consideration elsewhere; relation to any prior arXiv or conference version; suggested and opposed referees (per `prl-referee-strategy`); any special handling.

## The broad-interest paragraph (the load-bearing one)

- Be **specific**: "This result bears on [neighboring field] because [concrete mechanism/transfer]," not "this is of broad interest to physics."
- Anchor importance to a **change in understanding**, not to novelty alone.
- If borderline, pre-empt the "why not Phys. Rev. B?" reaction by stating explicitly what makes this cross-cutting.
- Keep it honest — editors discount inflated breadth claims and it can backfire.

## Checklist

- [ ] States it is submitted as a Letter to PRL, with the right subject area
- [ ] Central claim stated in one or two sentences
- [ ] Importance tied to a concrete change in understanding (not just novelty)
- [ ] Broad-interest paragraph names specific out-of-subfield audiences and why
- [ ] Pre-empts the "specialized PR journal" reaction if borderline
- [ ] Originality / concurrent-submission statement included
- [ ] Prior arXiv/conference version disclosed if applicable
- [ ] Suggested / opposed referees included (coordinate with prl-referee-strategy)
- [ ] Tone is specific and measured, not promotional

## Anti-patterns

- A cover letter that just restates the abstract
- Asserting "broad interest to the physics community" with no concrete audience
- Overselling significance the manuscript does not support
- Omitting the breadth argument entirely (the single most common miss)
- Hiding a prior arXiv/long version that the editor will find anyway
- Generic referee suggestions with no opposed-referee rationale

## Output format

```
【Submission line】Letter to PRL, subject area: ...
【Central claim】one sentence
【Importance】new effect / decisive measurement / unlocked regime + belief changed
【Broad interest】named audiences + concrete reason (the key paragraph)
【Housekeeping】originality / prior version / referees
【Tone】specific & measured?  yes / fix
【Next】prl-referee-strategy then prl-submission
```

> Cover-letter expectations and editor-track structure are durable, but subject categories 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', ...

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 →