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 Workflow

ASecurity

Use when deciding which prl-* sub-skill to invoke next, or when sequencing manuscript work from scope-fit through revision for a Physical Review Letters (PRL) manuscript. Routes — does not replace — the specialized skills.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Prl Workflow?

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

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

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

Download with Pro
Files
SKILL.md
---
name: prl-workflow
description: Use when deciding which prl-* sub-skill to invoke next, or when sequencing manuscript work from scope-fit through revision for a Physical Review Letters (PRL) manuscript. Routes — does not replace — the specialized skills.
---

# Physical Review Letters Workflow (prl-workflow)

## Overview

This is the router. It does not replace any specialized skill; it tells you **which prl-* skill to use at your current stage**.

Default assumption: unless the user says otherwise, the target is **Physical Review Letters (PRL)** — a short, high-impact Letter that must clear the *importance + broad interest* gate and fit the strict deductible length limit, with detail pushed to Supplemental Material. If the work is a solid but incremental or specialist advance, the right home is **Physical Review A–E** or **Physical Review Research**, and `prl-scope-fit` will say so.

## When to trigger

- User asks "what should I do next?" on a physics Letter
- User drops a draft and needs the current bottleneck diagnosed
- User is unsure whether the result is "PRL-worthy" or belongs in a specialized PR journal
- The Letter is over the length limit and detail must be re-partitioned
- User received an APS referee report and needs to switch into response mode

## Routing table

| Current symptom                                                       | Next skill              |
|-----------------------------------------------------------------------|-------------------------|
| Unsure if the result is important / broad enough for PRL              | `prl-scope-fit`         |
| Result is real but the "why it matters to all physicists" is unclear  | `prl-results-framing`   |
| Methods sprawl into the Letter; can't tell what to keep vs. move      | `prl-methods`           |
| Figures too dense / lead figure doesn't show the central result       | `prl-figures`           |
| Letter doesn't stand alone; reader needs the SM to follow it          | `prl-supplementary`     |
| Prose is wordy, hedged, jargon-heavy, or not APS house style          | `prl-writing-style`     |
| Over the length / figure / equation / reference limit                 | `prl-length-management` |
| Need a cover letter that justifies importance + broad interest        | `prl-cover-letter`      |
| Ready to submit; need format / file / metadata preflight              | `prl-submission`        |
| Choosing suggested/opposed referees; anticipating objections          | `prl-referee-strategy`  |
| Received a referee report or editor decision; need to respond         | `prl-revision`          |

## Default order

1. `prl-scope-fit` — settle the importance + broad-interest gate first; redirect to PR A–E / PR Research if it fails
2. `prl-results-framing` — lock the single central claim and its broad significance
3. `prl-methods` — keep only what a physicist needs to trust the result; the rest goes to SM
4. `prl-figures` — design the lead figure to convey the central result at a glance
5. `prl-supplementary` — partition derivations / extended data into SM; the Letter must stand alone
6. `prl-writing-style` — APS house style, concision, defined notation
7. `prl-length-management` — fit the deductible limit; trim ruthlessly (do this AFTER content is stable)
8. `prl-cover-letter` — argue the importance + broad-interest case to the editors
9. `prl-submission` — final preflight (format, files, classification, metadata)
10. `prl-referee-strategy` — suggested / opposed referees; pre-empt likely objections
11. `prl-revision` — after the referee reports arrive

> `prl-writing-style` and `prl-length-management` are **late polish stages**. Do not trim to the limit before the central claim and figures are stable, or you will cut the wrong material.

## Decision heuristics

- "Reviewer 2 will say 'why not Phys. Rev. B?'" → `prl-scope-fit`
- "I can state the result but not why anyone outside my subfield cares" → `prl-results-framing`
- "My Methods section is three paragraphs of apparatus detail" → `prl-methods`
- "My lead figure has six panels and a 9-line caption" → `prl-figures`
- "You can't understand Fig. 2 without reading the SM" → `prl-supplementary`
- "I'm 600 words over and figures count against me" → `prl-length-management`
- "The editor needs to be told why this is broad-interest" → `prl-cover-letter`
- "Submitting tonight" → `prl-submission`
- "Who should I suggest as a referee?" → `prl-referee-strategy`
- "Three referee reports just landed" → `prl-revision`

## Differences vs. specialized Physical Review journals

PRL and Phys. Rev. A–E / PR Research share APS production and rigor standards but differ on the **gate**:

- **PRL**: importance + broad interest, communicated concisely. A correct-but-incremental result is rejected on breadth grounds even if flawless.
- **PR A–E / PR Research**: thorough, archival, specialist-appropriate; length is generous and full methods belong in the body.

If `prl-scope-fit` returns a "specialist" verdict, retarget to the appropriate PR journal rather than fighting the breadth gate.

## Anti-patterns

- **Do not** skip `prl-scope-fit` — editors triage on importance/breadth first; a wrong-venue Letter wastes a submission cycle
- **Do not** run `prl-length-management` before content is stable — you will cut load-bearing material
- **Do not** let `prl-supplementary` become a dumping ground that the Letter silently depends on
- **Do not** draft `prl-revision` responses before you have actually changed the manuscript

> Durable norms only. Verify current word/figure/reference limits, formats, and policies 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 →