Astropy
zLanqing/codex-claude-academic-skills
Comprehensive Python library for astronomy and astrophysics.
A skill your agent uses when responding to Nature Geoscience referee reports or editor decisions — point-by-point reply, resubmission, and the Nature Portfolio appeal route.
Install Ngeo Revision
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ngeo-revision -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ngeo-revision --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Nature-Geoscience-Skills/skills/ngeo-revision .claude/skills/ngeo-revision && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ngeo-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Nature-Geoscience-Skills/skills/ngeo-revision into .claude/skills/ngeo-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ngeo-revision", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Nature-Geoscience-Skills/skills/ngeo-revisionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ngeo-revision -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ngeo-revision --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Nature-Geoscience-Skills/skills/ngeo-revision .agents/skills/ngeo-revision && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ngeo-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Nature-Geoscience-Skills/skills/ngeo-revision into .agents/skills/ngeo-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ngeo-revision", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ngeo-revision -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ngeo-revision --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Nature-Geoscience-Skills/skills/ngeo-revision .cursor/skills/ngeo-revision && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ngeo-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Nature-Geoscience-Skills/skills/ngeo-revision into .cursor/skills/ngeo-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ngeo-revision", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Nature-Geoscience-Skills/skills/ngeo-revision--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ngeo-revision -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ngeo-revision --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Nature-Geoscience-Skills/skills/ngeo-revision .gemini/skills/ngeo-revision && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ngeo-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Nature-Geoscience-Skills/skills/ngeo-revision into .gemini/skills/ngeo-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ngeo-revision", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ngeo-revisionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ngeo-revision -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Nature-Geoscience-Skills/skills/ngeo-revision .github/skills/ngeo-revision && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ngeo-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Nature-Geoscience-Skills/skills/ngeo-revision into .github/skills/ngeo-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ngeo-revision", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ngeo-revision -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ngeo-revision --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Nature-Geoscience-Skills/skills/ngeo-revision .opencode/skills/ngeo-revision && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ngeo-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Nature-Geoscience-Skills/skills/ngeo-revision into .opencode/skills/ngeo-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ngeo-revision", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ngeo-revision- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 759 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when responding to Nature Geoscience referee reports or editor decisions — point-by-point reply, resubmission, and the Nature Portfolio appeal route.
- Works in 3 steps: Quote the comment verbatim (or… → Respond — agree and act, or disagree… → Point to the change — name the exact…
- Responding to Nature Geoscience referee reports
- SKILL.md covers When to trigger, Read the decision before…, Point-by-point response… and Worked micro-example: a…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ngeo Revision is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when responding to Nature Geoscience referee reports or editor decisions — point-by-point reply, resubmission, and the Nature Portfolio appeal route. Structures the response and revision; does not redraft the science from scratch.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Physical and earth sciences. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Responding to Nature Geoscience referee reports
- Editor decisions — point-by-point reply
- The Nature Portfolio appeal route
Example prompts
- “/ngeo-revision”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Quote the comment verbatim (or faithfully paraphrase).
- Respond — agree and act, or disagree with evidence.
- Point to the change — name the exact location ("revised Methods subsection ..., new Fig. 3, new Supplementary Fig. S5, added sentence in…
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ngeo Revision loads about 1.7k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 759 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 759 words, ~1,692 tokens.
Download SKILL.mdSave it as
.claude/skills/ngeo-revision/SKILL.md (or your agent's skills folder).- name
- ngeo-revision
- description
- Use when responding to Nature Geoscience referee reports or editor decisions — point-by-point reply, resubmission, and the Nature Portfolio appeal route. Structures the response and revision; does not redraft the science from scratch.
Nature Geoscience Revision (ngeo-revision)
When to trigger
- One or more Nature Geoscience referee reports have arrived
- You received an editor decision (revise / reject / reject-with-appeal-option / editorially rejected before review)
- You need to write a point-by-point response to referees
- You are weighing revision versus appeal versus retargeting to a community journal or Communications Earth & Environment
Read the decision before drafting
Nature Portfolio decisions vary; match your strategy to the decision:
| Decision | Strategy |
|---|---|
| Revise (major/minor) | Address every referee point; revise; resubmit with response |
| Reject but resubmission invited | Substantive new work/analysis + a response showing what changed |
| Editorial reject before review (interest) | Decide: strengthen breadth case + appeal, or retarget |
| Reject after review on significance (science sound) | Sharpen the broad-interest/mechanism case, appeal, or retarget |
| Reject on a technical flaw | Fix the science or retarget; do not appeal a valid flaw |
Point-by-point response structure
For each referee comment:
- Quote the comment verbatim (or faithfully paraphrase).
- Respond — agree and act, or disagree with evidence.
- Point to the change — name the exact location ("revised Methods subsection ..., new Fig. 3, new Supplementary Fig. S5, added sentence in para ...").
Conventions that work with Nature Portfolio referees:
- Be courteous and specific; never dismissive, even with a hostile report.
- Quote new manuscript text in the reply so the referee sees the change without hunting.
- Provide a marked-up manuscript alongside a clean version per current Nature practice.
- If you disagree, win on evidence and Earth-system reasoning — add an analysis, a validation, a dataset, or a citation, not tone.
- Respect the container: added material must re-balance via
ngeo-length-management(main text ≤ ~3,000 words; extras to Methods/SI). - Re-check data/code availability and the Reporting Summary if analyses changed.
Worked micro-example: a response entry
Referee: "The circulation inference could reflect the choice of age model rather than a real lead–lag."
Weak reply: "We are confident the age model is not driving the result."
Strong reply: "We agree this must be excluded. We repeated the analysis under three alternative age models (new Supplementary Fig. S5 and Supplementary Table S3): the X ± Y-year lead is preserved in all cases. The Methods 'Age model' subsection now states this, and the main text adds: 'The lead is robust to the choice of age model (Methods; Supplementary Fig. S5).'"
The strong reply concedes the concern, answers with a repeated analysis with uncertainty, and quotes the new sentence with its location — the pattern for every entry.
Resubmission packaging
A Nature Geoscience resubmission is judged as a package:
- Summary of changes — lead with the revision answering the editor's and referees' central concern (usually significance/breadth or grounding).
- One self-contained reply per referee — do not make Referee 2 hunt through answers to Referee 1.
- Container re-certification — added analyses count against the main-text limit and display-item ceiling; state that the revised Article still fits, or what moved to Methods/SI.
- Availability + Reporting Summary refresh — update data/code statements and the Reporting Summary for any new data or code.
- Timing — resubmit complete rather than fast; a revised manuscript typically returns to the same referees.
Show full SKILL.md (264 more words)Show less
Handling the interest/significance rejection specifically
This is the signature Nature Geoscience outcome. Options:
- Sharpen, don't inflate. Make the broad-interest case concrete (
ngeo-results-framing,ngeo-cover-letter) — a real cross-field consequence and firmer grounding, not louder adjectives. - Appeal through the Nature Portfolio appeal route only if you have a substantive point the editor/referee missed; appeals are slow and are not for re-arguing taste.
- Retarget to a community journal or Communications Earth & Environment / Nature Communications if the breadth case is genuinely weak — often the faster path to publication (
ngeo-scope-fit).
Checklist
- Every referee point has an explicit response
- Each response names the exact manuscript change location
- New text is quoted in the reply for the referee's convenience
- Disagreements are backed by evidence/Earth-system reasoning, not tone
- A marked-up and a clean manuscript are prepared
- Added material is re-balanced against the word/display-item limits
- Data/code availability and Reporting Summary updated for new analyses
- The main text still stands alone after revision
- If appealing, the appeal raises a substantive missed point, not taste
- If retargeting, the right venue is chosen via ngeo-scope-fit
Anti-patterns
- A defensive or curt tone toward a difficult referee
- Claiming to have addressed a point without actually changing the text
- Adding rebuttal material that pushes the Article over the word/display-item limits
- Appealing a sound technical rejection instead of fixing the science
- Re-arguing breadth with adjectives instead of a concrete consequence and firmer grounding
- Letting revisions make the main text depend on the SI
Output format
【Decision type】revise / resubmit-invited / interest-reject / technical-reject
【Point-by-point】N comments — all addressed with locations? yes / list gaps
【Tone】courteous + evidence-based? yes / fix
【Container re-balanced after additions】yes / fix
【Availability + Reporting Summary refreshed】yes / n/a
【Stands alone after revision】yes / fix
【Path】resubmit / appeal (substantive?) / retarget via ngeo-scope-fit
【Next】ngeo-submission (resubmit) or ngeo-scope-fit (retarget)Decision categories, appeal procedures, and markup expectations are durable in spirit; verify the current process on the official Nature Geoscience / Nature Portfolio author pages (Checked: 2026-07-16).
© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Nature-Geoscience-Skills/skills/ngeo-revision of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ngeo Revision next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ngeo Revision this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| AstropyzLanqing/codex-claude-academic-skills | 4.7k | 13 repos | ~2.9k | Automated safety check: Pass | BSD-3-Clause | |
| PymatgenzLanqing/codex-claude-academic-skills | 4.7k | 11 repos | ~5k | Automated safety check: Pass | MIT | |
| Cantera Ignition DelayK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Weathertrpc-group/trpc-agent-go | 1.9k | 8 repos | ~591 | Automated safety check: Pass | Apache-2.0 | |
| Pymol VisualizationChatMol/ChatMol | 373 | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Pymatgen
zLanqing/codex-claude-academic-skills
Materials science toolkit. An agent skill from zLanqing/codex-claude-academic-skills.
Cantera Ignition Delay
K-Dense-AI/scientific-agent-skills
Runs Cantera constant-volume or constant-pressure ignition simulations and reports temperature-based ignition delay with mechanism provenance and checks.
Weather
trpc-group/trpc-agent-go
Get current weather and forecasts via wttr.in or Open-Meteo.
Pymol Visualization
ChatMol/ChatMol
Generate publication-quality molecular visualization images using PyMOL.
Review
Muuuun/luxas
Write domain-authentic review articles that synthesize rather than stack.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Ngeo Revision
What does Ngeo Revision do?
A skill your agent uses when responding to Nature Geoscience referee reports or editor decisions — point-by-point reply, resubmission, and the Nature Portfolio appeal route. Ngeo Revision is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when responding to Nature Geoscience referee reports or editor decisions — point-by-point reply, resubmission, and the Nature Portfolio appeal route.
When should I use Ngeo Revision?
Ngeo Revision fits situations like: responding to Nature Geoscience referee reports; editor decisions — point-by-point reply; the Nature Portfolio appeal route.
How do I install Ngeo Revision in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ngeo-revision -a claude-code`. Or copy the skill folder (Nature-Geoscience-Skills/skills/ngeo-revision in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ngeo-revision in your project. Claude Code loads it when a task matches its description.
How do I install Ngeo Revision in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ngeo-revision -a codex`. Or copy the skill folder (Nature-Geoscience-Skills/skills/ngeo-revision in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ngeo-revision in your project. Codex loads it when a task matches its description.
Can I use Ngeo Revision in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ngeo-revision -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ngeo-revision, .gemini/skills/ngeo-revision, .github/skills/ngeo-revision and .opencode/skills/ngeo-revision in your project.
What does Ngeo Revision need to run?
SKILL.md names no scripts, command-line tools or credentials: Ngeo Revision is instructions for the agent only.
Does Ngeo Revision access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ngeo Revision safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ngeo Revision use?
Ngeo Revision is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ngeo Revision use?
About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ngeo Revision?
Skills that share tags, products or a category with Ngeo Revision: Astropy (zLanqing/codex-claude-academic-skills, 4.7k stars), Pymatgen (zLanqing/codex-claude-academic-skills, 4.7k stars), Cantera Ignition Delay (K-Dense-AI/scientific-agent-skills, 48k stars) and Weather (trpc-group/trpc-agent-go, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ngeo Revision?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.