nature-shared
Skill0 starsChanged 2 months agoMITView on GitHub
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.
3 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- apattichis/agentic-research-toolkitedited, first seen Nov 8, 2026
- Luooops/skillsedited, first seen Oct 13, 2026
- Yuan1z0825/nature-skillsedited, first seen Aug 31, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- Yuan1z0825/nature-skills★ 53k97% same
- apattichis/agentic-research-toolkit★ 197% same
- Luooops/skills★ 197% same
Wrote their own version · 0
None found.
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 repository21 other files it gives its agents.
- journal-style-learnSkill
- nature-academic-searchSkill
- nature-citationSkill
- nature-dataSkill
- nature-downloaderSkill
- nature-experiment-logSkill
- nature-figure-prompt-onlySkill
- nature-figureSkill
- nature-image2pptSkill
- nature-literature-pipelineSkill
- nature-paper2pptSkill
- nature-paper-cardSkill
- nature-paper-to-patentSkill
- nature-polishingSkill
- researchwriteSkill
- nature-readerSkill
- nature-ref-verifierSkill
- nature-responseSkill
- nature-reviewerSkill
- nature-statisticsSkill
- nature-writingSkill
The file
We split this skill into the rules it gives an agent
9 rules. 1 is common, 0 are distinctive, and 8 are very specific to this project.
1
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 8
Use this package only as a dependency of another installed Nature skill.
- Very specific: line 11
Treat core/ and journal-formats/ as shared references, not standalone workflows.
- Very specific: line 12
Use journal-formats/nature.md only for the flagship journal Nature and core/research-compliance.md only when its specialist applicability …
- Very specific: line 15
Use journal-formats/nature-machine-intelligence.md for exact NMI article types, limits, initial-submission files, data/code duties and …
- Very specific: line 18
Use core/main-text-discipline.md for result placement, main-text compression, revision accretion, caption/SI allocation, and …
- Very specific: line 20
Use core/nature-results-discussion.md for corpus-derived Nature-style Results claim escalation, evidence-bound local interpretation, and …
- Very specific: line 23
Use core/discussion-argument-language.md for journal-general Discussion function sequencing, reverse-funnel control, evidence-calibrated …
- Very specific: line 26
Use core/nature-introduction.md for corpus-derived Nature-style problem funnels, exact knowledge gaps, literature tension, question-first …
- Very specific: line 33
Use journal-formats/eswa.md for Expert Systems with Applications (ESWA) requirements.
“Common” is measured: kept by at least 6 in 10 of the 3 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 Shared References
Use this package only as a dependency of another installed Nature skill.
- Load the exact referenced file; do not preload the whole package.
- Treat
core/andjournal-formats/as shared references, not standalone workflows. - Use
journal-formats/nature.mdonly for the flagship journal Nature andcore/research-compliance.mdonly when its specialist applicability gate is triggered. - Use
journal-formats/nature-machine-intelligence.mdfor exact NMI article types, limits, initial-submission files, data/code duties and production requirements; do not import flagship Nature or Nature Communications limits. - Use
core/main-text-discipline.mdfor result placement, main-text compression, revision accretion, caption/SI allocation, and claim-repetition checks. - Use
core/nature-results-discussion.mdfor corpus-derived Nature-style Results claim escalation, evidence-bound local interpretation, and Discussion synthesis; do not present it as official journal policy. - Use
core/discussion-argument-language.mdfor journal-general Discussion function sequencing, reverse-funnel control, evidence-calibrated modality, claim-specific limitations, and uncertainty-driven future work. - Use
core/nature-introduction.mdfor corpus-derived Nature-style problem funnels, exact knowledge gaps, literature tension, question-first novelty, and Introduction–Results alignment; do not present it as official journal policy. - Use
core/nature-abstract.mdfor corpus-derived Nature-style discovery-centred abstract compression, claim hierarchy, selective numeric support, and field-level payoff; do not present it as official journal policy. - Use
journal-formats/eswa.mdfor Expert Systems with Applications (ESWA) requirements. For chapter-specific drafting or polishing, use the colocated writing references at../nature-writing/references/article-architecture-eswa.mdand only its relevant section files. They are local ML/RUL corpus guidance, not official rules. Keepcore/eswa-ml-rul-style.mdfor existing visual/reviewer callers needing a compact corpus overview. Neither imports Nature or NMI submission rules. - Return to the requesting skill for task logic, output format, and final QA.
- Resolve other configured journal aliases through
journal-formats/index.md; read only the selected journal contract or writing-owned chapter profile. English references are canonical;-zh.mdcompanions are reading translations.
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.

