prl-workflow
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill prl-workflow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Overview
- When to trigger
- Routing table
- Default order
- Decision heuristics
- Letter status board
- Differences vs. specialized Physical Review journals
- Anti-patterns
What does the prl-workflow skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill prl-workflow --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.