gcb-cover-letter — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited gcb-cover-letter (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
The cover letter is the editor's first filter at a high-desk-rejection journal. In a short letter it must establish scope fit, the global-change mechanism and advance, and broad relevance — enough for the editor to send it out rather than desk-reject. Keep it honest; reviewers will check.
biological response/feedback, and say plainly why this is a GCB paper (mechanism + broad relevance), not a local report.
or the method — and why it matters beyond your system.
Opinion/Perspective (note that GCB Reviews are by invitation).
elsewhere; suggested/excluded reviewers if invited; any conflicts; confirmation that data and code will be archived per policy.
Para 1 — Driver → response + why it fits GCB's scope (mechanism, broad relevance)
Para 2 — The advance + headline quantified result + article type
Para 3 — Declarations (originality, exclusivity, data/code archiving, conflicts, reviewers)GCB's handling editors triage from the letter before opening the PDF. Map your opening lines to what that first scan rewards versus what tips it toward a desk reject.
| Editor reads | Send-out signal | Desk-reject signal |
|---|---|---|
| First sentence | A named driver acting on a named biological response | "Climate change threatens biodiversity" with no specific mechanism |
| Scale of claim | Plot/site result with a credible scaling argument and stated limits | A single-plot result framed as a global conclusion |
| Relevance hook | Generality across systems or biomes asserted with evidence | Relevance asserted only for one region or one taxon |
| Article-type line | A type that exists and is open for submission | An unsolicited "GCB Review" (those are commissioned) |
| Data/code line | A commitment to DOI archiving | Silence on archiving, or "available on request" |
A team measured soil-respiration response to five years of experimental warming across twelve grassland plots and combined it with a 90-site warming-experiment synthesis. Two openings, same study:
region." No driver magnitude, no mechanism, no scale — a likely desk reject on scope.
illustrative 28% (95% CI 19–37%), and our 90-site synthesis shows the response weakens where substrate is depleted — a mechanism that reconciles divergent prior estimates of the soil-carbon feedback to warming." Driver, magnitude, mechanism, synthesis, and a feedback of global relevance are all in the first two sentences. Numbers are illustrative; use your own.
the field site.
abstract.
than letting the editor infer overclaim.
【Scope fit】driver → response named; why GCB (not regional/conservation)? [Y/N]
【Advance】what is new + headline quantified result
【Article type】Primary Research / Technical Advance / Research Review / Opinion / Perspective
【Declarations】originality + exclusivity + data/code archiving + conflicts? [Y/N]
【Length】focused (1–2 paragraphs)? [Y/N]
【Next】gcb-review-process../../resources/official-source-map.md — scope, article types, and data policy referenced in the letter~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.