nature-workflow
Skill585 starsChanged 3 months agoMITView on GitHub
Use when the user explicitly asks for Nature Skills, nature-skills, Nature style, Nature-style, Nature Communications, Nature-family, CNS, high-impact journal, or Springer Nature workflows, including Nature figure work, polishing, writing, reviewer critique, high-impact journal major revision response, Nature/CNS citations, Nature data-sharing workflows, paper readers, reviewer response, paper-to-PPT, submission checklist, or Nature-specific academic-search workflows.
In this repository47 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/scholaraio.mdcCursor rule
- academic-writingSkill
- arxivSkill
- auditSkill
- backupSkill
- bioinformaticsSkill
- citation-checkSkill
- citationsSkill
- documentSkill
- drawSkill
- enrichSkill
- exploreSkill
- exportSkill
- graphSkill
- gromacsSkill
- importSkill
- indexSkill
- ingestSkill
- insightsSkill
- lammpsSkill
- literature-reviewSkill
- metricsSkill
- openfoamSkill
- paper-guided-readingSkill
- paper-writingSkill
- patent-fetchSkill
- patent-searchSkill
- posterSkill
- publishSkill
- quantum-espressoSkill
- renameSkill
- research-gapSkill
- review-responseSkill
- scientific-runtimeSkill
- scientific-tool-onboardingSkill
- scrubSkill
- searchSkill
- setupSkill
- showSkill
- technical-reportSkill
- topicsSkill
- translateSkill
- workspaceSkill
- writing-polishSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Use the original upstream nature-* skill directly whenever it is available.
- Very specific: line 18
Do not copy only SKILL.md from upstream.
- Very specific: line 22
If the upstream skill is unavailable, say so, then use the ScholarAIO fallback route from references/upstream-skill-map.md.
- Very specific: line 50
ScholarAIO fallback: only if upstream cannot be used.
- Distinctive: line 78
When the original upstream skill is not available:
- Distinctive: line 89
Use fallbacks conservatively.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Nature Workflow Bridge
This skill is a bridge to the upstream nature-skills bundle, not a simplified
clone of it. Its job is to route the user's request to the right original
nature-* skill when that skill is installed or otherwise available, and to
fall back to ScholarAIO's existing skills only when the original upstream skill
cannot be used in the current host.
Direct-Use Policy
Use the original upstream nature-* skill directly whenever it is available. Do
not emulate, summarize, or partially rewrite upstream behavior from this bridge.
Do not copy only SKILL.md from upstream; direct use requires the whole skill
directory, including manifest.yaml, static/, references/, scripts, assets,
and skills/_shared when the upstream skill references it.
If the upstream skill is unavailable, say so, then use the ScholarAIO fallback
route from references/upstream-skill-map.md. Mark the output as a ScholarAIO
fallback, not as an upstream-equivalent Nature Skills result.
Reference Loading
Load only what the current request needs:
references/upstream-skill-map.md: load for routing decisions or when the request could match more than one upstream skill.references/bridge-policy.md: load when installation, direct-use behavior, upstream fidelity, or fallback limitations matter.references/upstream-install.md: load when the user needs the original upstreamnature-*skills installed or asks whether this bridge is a simplified local copy.references/quickstart.md: load when the user asks how to use the bridge or wants example prompts.
First Pass
Classify the request before doing work:
- Upstream target: one or more of
nature-figure,nature-polishing,nature-writing,nature-reviewer,nature-citation,nature-data,nature-reader,nature-response,nature-paper2ppt, ornature-academic-search. - Availability: original upstream skill available, installed through a plugin/local skill path, or unavailable.
- ScholarAIO fallback: only if upstream cannot be used.
- Evidence state: manuscript/text/PDF/figures/comments/data/references supplied, workspace available, or missing inputs.
State the upstream target and whether direct upstream use is available before doing substantial work.
Route Table
| User intent | Primary route |
| Nature/high-impact scientific figure, publication plot, manuscript figure, figures4papers-style output | nature-figure |
| Nature-style polishing, manuscript prose polish, Chinese-to-English academic polish | nature-polishing |
| Draft/rebuild abstract, introduction, methods, experiments, discussion, conclusion, title, or manuscript argument | nature-writing |
| Pre-submission reviewer critique, mock peer review, Nature-style reviewer report | nature-reviewer |
| Nature/CNS citation support, claim-to-reference mapping, reference-manager export | nature-citation |
| Data Availability, repository plan, FAIR metadata, accession/DOI/source-data/code availability | nature-data |
| Full-paper bilingual reader, source-grounded Markdown reader, paper translation/reading | nature-reader |
| Reviewer comments, rebuttal, point-by-point response letter, major/minor revision response | nature-response |
| Paper-to-PPT, Chinese journal-club PPTX, group meeting deck from a paper | nature-paper2ppt |
| Multi-source literature search, citation verification, MeSH/search strategy, citation-file management | nature-academic-search |
Submission package is only one scenario. Do not require a full submission package when the user asks only for polishing, figures, reading, PPT, citation support, reviewer critique, Data Availability, response, or search.
ScholarAIO Fallbacks
When the original upstream skill is not available:
- figure work ->
/draw - prose polish ->
/writing-polish - manuscript writing ->
/paper-writing - reviewer response ->
/review-response - citation/search/export ->
/search+/citation-check+/export - paper reading/translation ->
/show+/translate - paper-to-PPT or document packaging ->
/document - literature search ->
/search, plus host-native web search when current or external coverage is required
Use fallbacks conservatively. Preserve upstream-style guardrails such as non-invention, source grounding, explicit missing inputs, and final-output verification, but do not claim to have executed the original upstream workflow unless the original skill was actually used.
Output Shape
For routing tasks, return:
Upstream target:selectednature-*skill or skill sequence.Mode:direct upstream use or ScholarAIO fallback.Route:exact skill sequence.Immediate next action:file to inspect, command to run, or question to ask.Guardrails:only the relevant non-invention, source-grounding, or verification constraints for this request.
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.

