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 Methods

ASecurity

Use when deciding what methodological detail belongs in a Physical Review Letters body versus Supplemental Material, so a physicist can trust the result without the Letter becoming a long paper. Partitions methods; does not design figures or run analysis.

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-methods --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prl Methods?

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

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

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

Download with Pro
Files
SKILL.md
---
name: prl-methods
description: Use when deciding what methodological detail belongs in a Physical Review Letters body versus Supplemental Material, so a physicist can trust the result without the Letter becoming a long paper. Partitions methods; does not design figures or run analysis.
---

# PRL Methods (prl-methods)

## When to trigger

- Your Methods text is several paragraphs of apparatus, sample, or derivation detail
- You cannot tell what a reader *needs* versus what is reassuring completeness
- Reviewers of a prior draft asked for more rigor, and you are tempted to add bulk
- The Letter is over length and methods are a prime trimming target
- You are unsure which derivation steps to keep inline versus move to SM

## The trust-minimum principle

In a Letter, methods exist to let a competent physicist **believe the central claim** — not to enable full replication inline. Full replication detail lives in Supplemental Material. Keep in the body only what is load-bearing for trust:

- The essential experimental configuration or theoretical setup (one compact description).
- The key control(s) that rule out the obvious alternative explanation.
- The decisive statistical/systematic statement (uncertainties, significance) for the headline number.
- The one or two equations that define the quantity being claimed.

Everything else — calibration procedures, sample growth, full Hamiltonians, lengthy derivations, parameter sweeps, additional checks — goes to SM and is cited inline ("see Supplemental Material [ref]").

## Partition table

| Detail type                                  | Body (trust-minimum)              | Supplemental Material            |
|----------------------------------------------|-----------------------------------|----------------------------------|
| Core setup / model definition                | one compact paragraph             | full apparatus / full Hamiltonian|
| Defining equations                           | 1–2 that define the claim         | full derivation chain            |
| Key control ruling out the obvious artifact  | yes, stated explicitly            | secondary controls               |
| Uncertainty on the headline result           | yes (stat + dominant syst)        | full error budget                |
| Sample / material preparation                | one-line provenance               | growth, characterization data    |
| Numerical convergence / mesh                  | one-line assurance                | convergence study                |
| Reproducibility info (code/data location)    | pointer                           | data-availability detail         |

## Rigor without bulk

PRL referees in physics are sharp about systematics and alternative explanations. Pre-empt the obvious objection **in the body**, briefly, and point to the SM for the exhaustive version. A single sentence ruling out the leading artifact is worth more than a paragraph of generic robustness language.

- State uncertainties as numbers, separating statistical and dominant systematic.
- Name the alternative explanation and the control that excludes it.
- For theory: state assumptions explicitly; relegate algebra to SM but keep the physical logic inline.

## Checklist

- [ ] Body methods are the minimum needed to trust the central claim
- [ ] The leading alternative explanation is named and addressed inline
- [ ] Headline result carries stated statistical + dominant systematic uncertainty
- [ ] Only claim-defining equations are inline; derivations are in SM
- [ ] Every "see SM" pointer resolves to actual SM content
- [ ] Data / code availability has a concrete pointer
- [ ] No replication-completeness padding in the body

## Anti-patterns

- Treating the Letter like a full PR article and inlining the whole method
- Generic robustness boilerplate instead of the one decisive control
- Quoting a headline number with no uncertainty, or merged stat+syst
- Equations with undefined symbols (define on first use)
- "Details available on request" instead of a data-availability statement

## Output format

```
【Trust-minimum kept inline】setup / key control / uncertainty / defining eqs
【Moved to SM】list
【Leading alternative explanation】named + control inline?  yes / fix
【Headline uncertainty】stat + syst stated?  yes / fix
【Data availability】pointer present?  yes / fix
【Next】prl-figures (lead figure) or prl-supplementary (SM partition)
```

> Data-availability and reproducibility expectations evolve — verify current APS policy 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 →