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

Gcb Revision And Rebuttal

ASecurity

Use when writing the response to a Global Change Biology (GCB) revise decision. A revision must address every reviewer point with evidence, defend the global-change mechanism and uncertainty treatment, and keep the archived data/code in sync. Structures the response letter; it does not fabricate new results.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill gcb-revision-and-rebuttal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gcb Revision And Rebuttal?

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

Security grade badge for Gcb Revision And Rebuttal
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-gcb-revision-and-rebuttal/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-gcb-revision-and-rebuttal)

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

Download with Pro
Files
SKILL.md
---
name: gcb-revision-and-rebuttal
description: Use when writing the response to a Global Change Biology (GCB) revise decision. A revision must address every reviewer point with evidence, defend the global-change mechanism and uncertainty treatment, and keep the archived data/code in sync. Structures the response letter; it does not fabricate new results.
---

# Revision & Rebuttal (gcb-revision-and-rebuttal)

A GCB **major/minor revision** is a real chance — but expert reviewers will check whether you actually
addressed mechanism, scale, uncertainty, and reproducibility. The response letter must convert each
reviewer with evidence while protecting the global-change contribution, and the revised manuscript must
stay consistent with the **archived data and code**.

## When to trigger

- A revise decision arrived and you are planning the revision + response letter
- Reviewers disagree and you must reconcile their demands
- A reviewer requests analyses that would change the paper's claims
- Updating the manuscript while keeping the data/code archive in sync

## Strategy

1. **Treat the handling editor's letter as the global-change rubric.** It flags which concerns are
   decisive — usually the strength of the driver-to-response mechanism, the scale of inference, or the
   uncertainty treatment. Resolve those before the smaller comments.
2. **Answer every reviewer point in a single numbered table.** Reproduce each comment, then give your
   response beneath it; an unanswered comment reads as evasion to expert ecological reviewers.
3. **For each comment, either revise or argue back with evidence.** Where you complied, cite the new
   figure/panel/equation/line; where you disagree, ground the pushback in the mechanism, the experimental
   or modelling design, or the data — a defensible biogeochemical argument lands better than a reflexive
   concession that erodes the result.
4. **Defend mechanism, scale, and uncertainty head-on.** GCB referees routinely press on extrapolation
   from plot to ecosystem/biome, on confounding and pseudoreplication, and on whether uncertainty was
   propagated — meet each with a new robustness, sensitivity, or ensemble analysis rather than prose.
5. **Surface reviewer disagreements rather than papering over them.** When two referees pull in opposite
   directions, name the conflict, pick the path the evidence supports, and explain the tradeoff to the
   editor.
6. **Re-sync the deposited archive.** Refresh the **data and code (DOI)** deposit so every new table and
   figure reproduces, and revise the data availability statement to match (see
   `gcb-reporting-and-data-policy`).

## Response-letter format

Per comment, keep the quote-then-answer structure expert referees expect:

```
> [Reviewer comment, verbatim]

Reply: [the revision made, or the mechanism/design/data reason for disagreeing].
Where: [figure / panel / equation / line number in the revised manuscript].
```

Lead with a brief editor-facing digest of the headline changes (new mechanism evidence, scale
qualifications, added uncertainty analyses); organize by referee; close each item with the exact
location so the editor can spot-check quickly.

## Anti-patterns

- Folding a comment into the revision silently, with no traceable reply
- Caving to a request that severs the driver-to-response logic just to placate a referee
- A combative or dismissive register toward reviewers
- "We thank the reviewer" attached to no concrete edit or reasoned rebuttal
- Slipping in analyses that undercut the original claim without flagging the shift
- Revised figures whose numbers no longer match the archived data and code

## Output format

```
【Editor's decisive points】addressed first? [list]
【Coverage】every reviewer comment answered? [Y/N]
【Concede vs rebut】each tagged with evidence + change location
【Mechanism/scale/uncertainty】defended with added analyses? [Y/N]
【Reviewer conflicts】reconciled and explained to editor? [Y/N]
【Archive updated】data/code DOI + availability statement in sync? [Y/N]
【Next】resubmit via ScholarOne
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — decision categories, review model, and data policy
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — robustness/uncertainty and archiving tooling

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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.

691 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 →