Agent skill

pnas-rebuttal

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

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnas-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: 6 KB
Bundled scripts: none
Path: PNAS-Skills/skills/pnas-rebuttal/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 984 · +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 (pnas-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. ## Step 0: read the editor's letter first The **editor's** framing outranks individual reviewers. For Direct Submissions this is the PNAS-assigned editor; for Contributed Submissions the member who communicated the paper relays the reviews. Either way, 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. ## Triage every comment into 4 buckets | Bucket | Action | |--------------------|------------------------------------------------------------------| | **Do** (fair, feasible) | Make the change; show it; quote the new text/figure. | | **Do-partial** | D

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

Use after PNAS reviews arrive to triage the decision, prioritize experiments, and draft a point-by-point response that is respectful, evidence-led, and honest about limits. 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 pnas-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 984 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