Writing Style (gcb-writing-style)

SkillDev tools

Use when drafting or polishing the prose of a Global Change Biology (GCB) manuscript so it reads for a broad ecology / biogeochemistry / Earth-system audience within the journal's length and abstract limits. GCB rewards a clear mechanism, quantified results, and global-change significance. Guides style; it does not ghost-write the science.

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Then ask your AI: use the Writing Style (gcb-writing-style) skill

What this skill tells your AI

The instructions your AI receives, as published by brycewang-stanford/awesome-journal-skills in Global-Change-Biology-Skills/skills/gcb-writing-style/SKILL.md and read by ahel’s review.

A GCB paper must read for a broad global-change audience — ecologists, biogeochemists, and Earth-system scientists who are not specialists in your system. Lead with the mechanism and the global-change significance, quantify everything, and stay within the length and abstract limits. Verify exact caps on the live guidelines page before submission.

When to trigger

  • Drafting the abstract, introduction, or discussion
  • Cutting an over-length manuscript to the word ceiling
  • Making system-specific work legible to a general GCB reader
  • Final language polish before submission

What GCB rewards

  1. Mechanism up front. State the driver, the response, and the mechanism in the abstract and the first paragraphs — not buried in the discussion.
  2. Global-change significance early. Say why this matters for understanding biological responses to global change, beyond a single site/species.
  3. Quantified claims. Effect sizes with intervals and units in the abstract and results; avoid vague "increased significantly" without magnitude.
  4. Structured, disciplined abstract. 300-word limit; state aim, approach, key quantitative result, and conclusion; 6–10 keywords.
  5. Honest scope. Be explicit about the system, scale, and extrapolation limits — generality claimed only as far as the evidence reaches.
  6. Plain, active prose. Define jargon; expand acronyms on first use; write for a reader outside your subfield.

Length & structure

  • Respect the article-type word ceiling; Research Articles currently route to an up to 8,000-word cap. Cut method minutiae to supporting information.
  • Standard IMRaD for Primary Research Articles; argument-led structure for Opinions/Perspectives.

Sentence-level rewrites for a global-change audience

GCB prose fails most often at the sentence, not the structure. This table pairs the broad-readership weakness with the rewrite a general ecologist/biogeochemist can parse.

Weak sentenceWhy it fails at GCBRewrite
"Warming significantly increased flux."No magnitude, no mechanism"Warming raised CO2 efflux by 28% (95% CI 19–37%) via faster microbial turnover."
"Results have broad implications."Significance asserted, not shown"The feedback weakens the land carbon sink across temperate grasslands."
"We used GLMMs on the NPP data."Undefined acronym for a non-specialist"We fitted mixed models to net primary productivity (NPP)."
"This is the first record for our site."Local novelty, not advance"This resolves why prior syntheses disagreed on the response."

Worked micro-example (illustrative)

An abstract opens: "Climate change is a major threat to ecosystems. We sampled a grassland and analysed the data." It states no driver magnitude, no mechanism, no result — a general GCB reader learns nothing. Rewritten to GCB style: "Experimental warming of +2.4 C accelerated soil CO2 efflux by 28% (95% CI 19–37%; illustrative), driven by faster microbial substrate turnover, weakening the soil-carbon sink across temperate grasslands." Aim, approach, quantified result, mechanism, and global-change significance now sit in the first lines, inside the abstract cap. Numbers illustrative.

Reviewer pushback on prose and the fix

  • "Significance buried" → move the global-change consequence into the abstract and the opening paragraph.
  • "No magnitude" → attach an effect size, interval, and unit to every key claim.
  • "Too specialist to follow" → define jargon, expand acronyms on first use, and write for a reader outside your subfield.

Anti-patterns

  • An abstract that describes methods but never states the quantitative result or mechanism
  • Burying the global-change significance until the last paragraph
  • "Significant" with no effect size, interval, or unit
  • Subfield jargon and undefined acronyms that a general GCB reader cannot follow
  • Overclaiming generality beyond the evidence's scale/system

Output format

【Mechanism stated early】driver → response in abstract + intro? [Y/N]
【Significance early】global-change relevance up front? [Y/N]
【Quantified】effect sizes + intervals + units in abstract/results? [Y/N]
【Abstract】word count (300-word limit) + 6–10 keywords
【Length】within article-type ceiling? [Y/N]
【Accessible】jargon/acronyms defined for general reader? [Y/N]
【Next】gcb-cover-letter

Supplementary resources

Signals

GitHub stars
1k
Forks
155
Last commit
Sep 2026
Advanced
Item type
skill
Key
gcb-writing-style
Source
github.com/brycewang-stanford/awesome-journal-skills