Menu

Individual skill

pnas-workflow

0upvotes

Use when deciding which pnas-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal for PNAS (Proceedings of the National Academy of Sciences). Routes — it does not replace — the specialized skills.

PNAS-Skills/skills/pnas-workflow/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,397
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# PNAS Workflow Router (pnas-workflow)

## Overview

This is the router. It does not replace any specialized skill. It tells you **which pnas-* skill to use at the current stage** of a manuscript aimed at *PNAS* (Proceedings of the National Academy of Sciences).

PNAS publishes across three broad divisions — **Biological Sciences, Physical Sciences, and Social Sciences** — and every research article is filed under one of them plus a minor subject area (`pnas-writing`). Two things make PNAS unlike Science or Nature and reshape the workflow: the **submission track** decision (Direct vs Contributed by an NAS member — `pnas-track`) and the mandatory **Significance Statement** (`pnas-significance`). Settle the track early; it changes how the paper is handled and reviewed.

## When to trigger

- "What should I do next with this draft?"
- A draft arrives and you must diagnose the current bottleneck.
- The user is unsure whether to use Direct or Contributed submission.
- Reviews arrive from PNAS and you need to switch into rebuttal mode.
Back to top