nature-figure
Skill14 starsChanged 5 months agoApache-2.0View on GitHub
Submission-grade Nature/high-impact journal figure workflow for Python or R. Use whenever the user asks to create, revise, audit, or polish manuscript figures, multi-panel scientific plots, figures4papers-style matplotlib plots, or journal-ready SVG/PDF/TIFF outputs, especially for Nature-family or other high-impact journals. Before plotting, define the figure's conclusion, evidence logic, export needs, and review risks. If the user has not chosen Python or R, ask "Python or R?" and stop. Use only the selected backend for figure generation, previewing, exporting, and QA. Supports matplotlib/seaborn and ggplot2/patchwork/ComplexHeatmap. Not for dashboards or Illustrator/Figma-first infographics. Also trigger on general academic-writing figure needs even without the word "Nature", such as making figures/plots for a paper, scientific/academic plotting, data visualization for a manuscript, and Chinese phrasings like 论文配图、学术写作配图、科研绘图、科研作图、画图、作图、出图、论文图表、可视化.
15 other projects use a version of this, 9 of them edited.
Adopted by
Most recently taken up by
- AfonsoZhang/auto-research-systemedited, first seen Nov 15, 2026
- denghuipan/nature-portfolio-skillsword for word, first seen Nov 15, 2026
- apattichis/agentic-research-toolkitedited, first seen Nov 8, 2026
- dragonadam/nature-skillsedited, first seen Oct 25, 2026
- Luooops/skillsedited, first seen Oct 13, 2026
- Boom5426/Nature-Paper-Skillsedited, first seen Oct 9, 2026
Used with
Projects with it also use nature-experiment-log, nature-shared and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Delagong950Skillnature-experiment-log
Standardized lab notebook with structured YAML-frontmatter experiment logs. Supports Obsidian vault integration, image/voice/text input, and batch/tracking systems.
Also in 5 projects that use this
Yuan1z0825Skillnature-shared
Internal shared-reference support package for installed Nature Skills, including nature-writing, nature-polishing, nature-response, nature-reader, and nature-paper2ppt. Do not invoke it as a standalone user workflow. Load only the specific core or journal-format file requested by another Nature skill.
Also in 5 projects that use this
vcis-wangchenxuSkillnature-downloader
Help legally obtain, organize, and archive academic papers, PDFs, BibTeX, supplementary files, code links, and benchmark documents for RL, MARL, LLM, and LLM Agent research. Do not bypass paywalls or access controls.
Also in 5 projects that use this
Delagong950Skillnature-ref-verifier
Multi-source cross-validation of academic references. Verify authors, title, year, volume, issue, and pages against PubMed, CrossRef, and publisher pages. Detect fabricated citations.
Also in 5 projects that use this
vcis-wangchenxuSkillnature-literature-pipeline
Build a repeatable literature discovery, scoring, reading, and archiving pipeline for RL, MARL, LLM, and LLM Agent research. Use for daily/weekly paper tracking, topic watchlists, benchmark monitoring, and research-note automation.
Also in 4 projects that use this
Other versions15 projects use a version of this.
Word for word · 1
- denghuipan/nature-portfolio-skills★ 2100% same
Edited · 9
- Yuan1z0825/nature-skills★ 54k18% same
- Boom5426/Nature-Paper-Skills★ 66139% same
- yjz211/MathModeling-AI-Solver-Skills★ 543% same
- dragonadam/nature-skills★ 499% same
- AfonsoZhang/auto-research-system★ 117% same
- apattichis/agentic-research-toolkit★ 118% same
- Luooops/skills★ 119% same
- zh123012/claude-skills★ 151% same
- szzjayson25-hub/nature-academic-skills★ 025% same
Wrote their own version · 5
- Chanw-research/claude-code-paper-writing★ 42same name
- Yang1Bai/nature-paper-hub★ 20same name
- Delagong950/nature-skills★ 4same name
- vcis-wangchenxu/agent_nature-skills★ 4same name
- Lling0000/nature-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- nature-academic-searchSkill
- nature-citationSkill
- nature-dataSkill
- nature-paper2pptSkill
- nature-paper-to-patentSkill
- nature-polishingSkill
- nature-readerSkill
- nature-responseSkill
- nature-reviewerSkill
- nature-writingSkill
- openclaw-medical-skillsSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Do not try to apply the figure logic from memory or from this router.
- Distinctive: line 20
Follow these five steps every time the skill is invoked.
- Very specific: line 24
Read manifest.yaml. It declares the backend axis, the allowed values, and the file paths each value maps to.
- Very specific: line 39
After the backend is resolved, Read the mapped fragment (static/fragments/backend/python.md or static/fragments/backend/r.md).
- Very specific: line 46
Default stance (core/stance.md) — archetype-first composition, hero panel, restrained palette, statistics/integrity as part of the figure.
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Nature Figure Making — Router
This skill is split into two layers:
- A static layer under
static/that holds versioned, reusable content fragments (the figure contract and default stance, plus a per-backend quick-start for Python and R). - A dynamic layer (this file plus
manifest.yaml) that detects the plotting backend and loads only the fragment needed for the current job. The large design, API, pattern, and QA material lives in on-demand references.
Do not try to apply the figure logic from memory or from this router. Always load fragments from disk as described below.
Routing protocol
Follow these five steps every time the skill is invoked.
1. Load the manifest and the core layer
Read manifest.yaml. It declares the backend axis, the allowed values, and the file paths each value maps to.
Also read every file listed under always_load (static/core/contract.md and static/core/stance.md). These hold the figure contract, the backend gate, the missing-runtime rule, the privacy rule, and the default operating stance that apply to every figure job.
2. Resolve the backend — a blocking gate
Backend selection blocks everything else. Decide the backend value only from an explicit user choice or a clearly language-specific input file/workflow:
python— matplotlib / seaborn.r— ggplot2 / patchwork / ComplexHeatmap.
If the user has not explicitly chosen, ask exactly one concise question — Python or R? — and stop. Do not default, guess, generate mock data, or write scripts before the answer. Only recommend a backend when the user explicitly asks you to choose; then use references/backend-selection.md, state the reason, and proceed. Once selected, the backend is exclusive for all drawing, previewing, exporting, and visual QA (see core/contract.md).
3. Load the matching backend fragment
After the backend is resolved, Read the mapped fragment (static/fragments/backend/python.md or static/fragments/backend/r.md). It carries the backend-only execution rule and the publication quick-start (rcParams/theme and export helper). Do not load the other backend's fragment.
4. Build the figure using the loaded material
Apply the loaded material in this order:
- Figure contract (
core/contract.md) — write the core conclusion, map the evidence chain, classify the archetype, set the journal/export contract, before any code. - Default stance (
core/stance.md) — archetype-first composition, hero panel, restrained palette, statistics/integrity as part of the figure. - Backend fragment — the exclusive Python or R quick-start and execution rule.
The chart serves the scientific logic; aesthetic polish is subordinate to making the core conclusion clear, defensible, and reviewable.
5. Reach for references only when needed
The files under references/ are deep references, not defaults. Open them on demand per the references.on_demand table in the manifest — for example references/figure-contract.md to build the contract, references/api.md for the Python palette and helpers, references/r-workflow.md for R, references/design-theory.md for color/typography/export rationale, references/common-patterns.md and references/chart-types.md for layout/chart recipes, references/nature-2026-observations.md for real Nature page archetypes, references/qa-contract.md before final delivery, and references/tutorials.md / references/demos.md for worked examples.
Why this split
- The static layer is versioned and reviewable. The backend gate is now explicit in the manifest rather than buried in prose.
- The dynamic layer keeps each invocation cheap: only the selected backend's quick-start enters context, and the 2,600+ lines of reference depth load only when a step needs them.
- The router itself is short on purpose. Update fragments and references, not this file, when adding scope.
- This structure mirrors
nature-writing,nature-polishing,nature-reader, andnature-paper2ppt.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

