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

Pnas Track

ASecurity

Use to choose the PNAS submission track — Direct Submission (standard, editor-assigned, peer reviewed) vs Contributed Submission (an NAS member communicates their own paper). Covers eligibility, the editor/member role, the discontinued and legacy tracks, and how to pick. Unique to PNAS.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Pnas Track?

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

Security grade badge for Pnas Track
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-pnas-track/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-pnas-track)

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

Download with Pro
Files
SKILL.md
---
name: pnas-track
description: Use to choose the PNAS submission track — Direct Submission (standard, editor-assigned, peer reviewed) vs Contributed Submission (an NAS member communicates their own paper). Covers eligibility, the editor/member role, the discontinued and legacy tracks, and how to pick. Unique to PNAS.
---

# Submission Track Selection (pnas-track)

## Why this skill exists

The **submission track** is PNAS's signature feature and has **no equivalent at Science or Nature**. The track determines who handles the paper, who picks reviewers, and how the published article is labeled. Pick it early — it shapes the entire handling path. Do this right after `pnas-fit`.

## When to trigger

- You are about to start a PNAS submission and must choose a track.
- A co-author or collaborator who is a **member of the U.S. National Academy of Sciences (NAS)** offers to "communicate" or "contribute" the paper.
- You read "Contributed by …" or "Edited by …" on a PNAS paper and need to know what it means for yours.
- You are unsure whether the legacy "Communicated" or "Prearranged Editor" options still apply.

## The tracks

### (a) Direct Submission — the default for most authors

- **Standard route.** Anyone may submit. The manuscript is **assigned to an editorial board member / editor by PNAS**, who oversees independent peer review.
- No NAS member required. This is what most authors use and what `pnas-submission` defaults to.
- You may suggest editors and reviewers in the cover letter (`pnas-submission`), but the journal assigns the handling editor.

### (b) Contributed Submission — only via an NAS member

- An **NAS member** may **"contribute"** a paper they are an author on. The member acts as the communicating editor: they **arrange the review themselves**, typically securing **at least two qualified, independent reviewers**, and submit the reviews and the authors' responses along with the paper.
- **Strict limit:** an NAS member may contribute only a **small number of papers per year** (historically about **2 per member per year** — confirm the current cap in PNAS author guidelines).
- The member must be an author and is responsible for the integrity of the review they arrange; reviewers must be genuinely independent (no recent collaborators, no conflicts).
- Published articles are labeled **"Contributed by [Member]."**

### (c) Legacy / discontinued options

- **Prearranged Editor (PE):** historically, a non-member author could ask an NAS member to agree in advance to be the editor before submission, after which the paper went through PNAS's standard review. Availability has changed over time — **confirm whether this option currently exists** before relying on it.
- **"Communicated" submissions (third-party member relays a non-member's paper):** this older track was **discontinued** — do not plan around it.

## How to pick

| Situation | Track |
|-----------|-------|
| No NAS member among the authors | **Direct Submission** |
| An NAS-member author wants standard PNAS-run review | **Direct Submission** (member is just an author) |
| An NAS-member author wants to communicate and has not used up their annual quota, and can secure ≥2 independent reviewers | **Contributed Submission** (eligible) |
| You want the fastest/most controlled handling but have no eligible member | **Direct Submission** (Contributed is not available to you) |
| You are tempted by a legacy track | confirm it still exists; default to **Direct** |

> Contributed is a privilege of the member, bounded by the annual quota and by the independence requirement. It is **not** a way to dodge peer review — the reviews still happen and are submitted with the paper. If reviewer independence is in any doubt, use Direct Submission.

## What the label means to readers

The published article carries its track in the header — "Edited by …" for a Direct Submission handled by the assigned editor, or "Contributed by [Member]" for a Contributed paper. Reviewers, journalists, and downstream readers can see the route. A Contributed paper with weak member-arranged review attracts scrutiny; Direct Submission with PNAS-run review is the conservative default and carries no such overhead.

## Timing implications

- **Direct:** PNAS assigns the editor and manages review; timeline is standard for the journal and outside your control.
- **Contributed:** the member front-loads the work (securing reviewers, collecting reviews, bundling responses) *before* the paper reaches PNAS, which can shorten the journal-side timeline — but only if the member actually has time to manage it. Do not choose Contributed for speed if the member cannot commit the effort.

## Eligibility & integrity checklist

- [ ] Is any author a current NAS member? (If no → Direct.)
- [ ] If Contributed: has the member used their annual contribution quota? (Confirm current cap.)
- [ ] If Contributed: can the member secure **≥2 independent** reviewers (no conflicts/recent collaboration)?
- [ ] If Contributed: are the reviews and author responses ready to submit **with** the paper?
- [ ] Cover letter states the chosen track and, for Direct, suggested editors/reviewers (`pnas-submission`).

## Output format

```
【NAS member among authors?】 yes/no (who)
【Track chosen】 Direct / Contributed / (legacy — confirm)
【If Contributed】 member: ___ | within annual quota? yes/no | ≥2 independent reviewers secured? yes/no
【Reviewer-independence check】 ok / risk → if risk, switch to Direct
【Why this track】 one line
【Next】 pnas-writing
```

## Anti-patterns

- **Do not** use Contributed Submission to avoid genuine independent review — reviews are still required and submitted.
- **Do not** assume a member can contribute unlimited papers — the annual quota is real (≈2/year; confirm).
- **Do not** plan around the discontinued "Communicated" track.
- **Do not** let a member contribute when reviewers are recent collaborators — use Direct instead.
- **Do not** leave the track decision to the final submission step; it shapes editor handling.

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 →