Agent skill

pnasnexus-rebuttal

Use after PNAS Nexus reviews arrive to triage the decision, prioritize experiments, and draft a point-by-point response that is respectful, evidence-led, and honest about limits. Covers the case where reviews were carried over from a PNAS transfer. Do not run before the main text is actually revised.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-rebuttal --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: PNAS-Nexus-Skills/skills/pnasnexus-rebuttal/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Reviewer Rebuttal (pnasnexus-rebuttal) ## When to trigger - A decision letter arrives (reject / major or minor revision / accept-with-revisions). - You have reviewer comments and need a strategy before writing. - A revision is drafted and you need the point-by-point response letter. - The reviews include **transferred PNAS reviews** plus new PNAS Nexus reviews. ## Step 0: read the editor's letter first The **handling editor's** framing outranks individual reviewers. At PNAS Nexus the paper was assigned to an Editorial Board member and then a handling/guest editor; that editor's letter tells you what is load-bearing. Identify: - The decision type and whether a new review round is implied. - Which concerns the editor **emphasizes** (these are load-bearing — address fully). - Any **deal-breaker** the editor names (e.g., "the central claim needs independent validation"). > A "reject but would consider a new submission" is an invitation gated on the deal-breaker. Don't treat it as a flat reject, but don't under-deliver either. ## Special case: reviews carried over from a PNAS transfer If the paper was **transferred from flagship PNAS**, prior PNAS reviews travel with it. When respondi

What's inside
Steps it walks through
  1. When to trigger
  2. Step 0: read the editor's letter first
  3. Special case: reviews carried over from a PNAS transfer
  4. Triage every comment into 4 buckets
  5. Prioritize the experiments
  6. Response-letter format
  7. Tone rules
  8. Claim-integrity / over-claiming watch
  9. PNAS Nexus revision ledger
  10. Output format
  11. Anti-patterns
More from Awesome-Journal-Skills
All skills →
About this skill
What does the pnasnexus-rebuttal skill do?

Use after PNAS Nexus reviews arrive to triage the decision, prioritize experiments, and draft a point-by-point response that is respectful, evidence-led, and honest about limits. Covers the case where reviews were carried over from a PNAS transfer. Do not run before the main text is actually revised.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-rebuttal --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.

Keep going