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 Writing Style

ASecurity

Use when polishing the prose of a Physical Review Letters manuscript for APS house style, concision, precise notation, and out-of-subfield readability. Polishes language; does not restructure the result or manage length budget.

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-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prl Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: prl-writing-style
description: Use when polishing the prose of a Physical Review Letters manuscript for APS house style, concision, precise notation, and out-of-subfield readability. Polishes language; does not restructure the result or manage length budget.
---

# PRL Writing Style (prl-writing-style)

## When to trigger

- Prose is wordy, hedged, or jargon-dense
- Notation is inconsistent or symbols are undefined on first use
- An out-of-subfield physicist would stumble on the opening
- The draft uses long subordinate clauses where a Letter wants directness
- You are in late polish, after the result, figures, and SM are stable

## APS house-style essentials

- **Concision is a feature, not a constraint.** A Letter says what it must and stops. Every sentence should advance the central claim.
- **Active, direct voice** where it sharpens meaning; "We measure ..." / "The data show ..." beats passive circumlocution.
- **Define every symbol on first use**; keep notation consistent across Letter, figures, and SM.
- **Spell out acronyms on first use**; avoid undefined subfield jargon in the abstract and opening.
- **SI units**, consistent significant figures, and proper math typesetting.
- **Reference style** follows the current APS format; cite the prior work that establishes importance and the work the reader needs to trust the result.

## Concision moves

| Wordy pattern                                  | Tightened                                  |
|------------------------------------------------|--------------------------------------------|
| "It is important to note that X"               | "X"                                        |
| "In order to"                                  | "To"                                       |
| "We have performed measurements of"            | "We measure"                               |
| "Due to the fact that"                         | "Because"                                  |
| Three hedges in one sentence                   | one calibrated qualifier                   |
| Background paragraph before the result          | one-sentence context, then the result      |
| Restating the figure in prose                  | interpret the figure, don't transcribe it   |

## Readability for a broad audience

PRL's broad-interest gate is also a *writing* requirement: a condensed-matter referee may read an AMO Letter. So:

- Open with physics a non-specialist understands before introducing subfield notation.
- Gloss specialized concepts in one clause rather than assuming them.
- Put the physical interpretation next to every key equation or number.
- Avoid acronym soup; prefer the spelled-out concept when space allows.

## Precision discipline

- State claims at the strength the evidence supports — neither over- nor under-claiming.
- "Significantly" should mean statistically significant, not "a lot."
- Quote uncertainties with every headline number.
- Match tense conventions: present for established facts, past for what you did.

## Checklist

- [ ] Every sentence advances the central claim; no padding
- [ ] All symbols defined on first use; notation consistent throughout
- [ ] Acronyms spelled out on first use; abstract is jargon-light
- [ ] Opening readable by an out-of-subfield physicist
- [ ] Physical interpretation accompanies key equations/numbers
- [ ] Claims calibrated to the evidence (no over/under-claiming)
- [ ] SI units and consistent significant figures
- [ ] References follow current APS format

## Anti-patterns

- "Letterese" that is dense and unreadable rather than crisp
- Undefined symbols or acronyms, especially in the abstract
- Hedging stacks ("may possibly suggest that perhaps ...")
- Prose that transcribes a figure instead of interpreting it
- Subfield jargon in the opening that excludes the broad audience
- Overclaiming significance the data do not support

## Output format

```
【Concision pass】padding removed?  yes / list
【Notation】all symbols defined, consistent?  yes / fix
【Broad readability】opening accessible out-of-subfield?  yes / fix
【Interpretation by every key number】yes / fix
【Claim calibration】matched to evidence?  yes / fix
【Next】prl-length-management (fit limit) or prl-cover-letter
```

> Reference and typesetting conventions evolve — verify current APS style on the official 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 →