agentleFS
szzjayson25-hubszzjayson25-hub/nature-academic-skills/nature-shared/SKILL.md

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

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
  1. Common:

    Use this package only as a dependency of another installed Nature skill.

    line 8
  2. Very specific:

    Treat core/ and journal-formats/ as shared references, not standalone workflows.

    line 11
  3. Very specific:

    Use journal-formats/nature.md only for the flagship journal Nature and core/research-compliance.md only when its specialist applicability …

    line 12
  4. Very specific:

    Use journal-formats/nature-machine-intelligence.md for exact NMI article types, limits, initial-submission files, data/code duties and …

    line 15
  5. Very specific:

    Use core/main-text-discipline.md for result placement, main-text compression, revision accretion, caption/SI allocation, and …

    line 18
  6. Very specific:

    Use core/nature-results-discussion.md for corpus-derived Nature-style Results claim escalation, evidence-bound local interpretation, and …

    line 20
  7. Very specific:

    Use core/discussion-argument-language.md for journal-general Discussion function sequencing, reverse-funnel control, evidence-calibrated …

    line 23
  8. Very specific:

    Use core/nature-introduction.md for corpus-derived Nature-style problem funnels, exact knowledge gaps, literature tension, question-first …

    line 26
  9. Very specific:

    Use journal-formats/eswa.md for Expert Systems with Applications (ESWA) requirements.

    line 33

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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/ and journal-formats/ as shared references, not standalone workflows.
  • Use journal-formats/nature.md only for the flagship journal Nature and core/research-compliance.md only when its specialist applicability gate is triggered.
  • Use journal-formats/nature-machine-intelligence.md for 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.md for result placement, main-text compression, revision accretion, caption/SI allocation, and claim-repetition checks.
  • Use core/nature-results-discussion.md for 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.md for journal-general Discussion function sequencing, reverse-funnel control, evidence-calibrated modality, claim-specific limitations, and uncertainty-driven future work.
  • Use core/nature-introduction.md for 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.md for 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.md for Expert Systems with Applications (ESWA) requirements. For chapter-specific drafting or polishing, use the colocated writing references at ../nature-writing/references/article-architecture-eswa.md and only its relevant section files. They are local ML/RUL corpus guidance, not official rules. Keep core/eswa-ml-rul-style.md for 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.md companions are reading translations.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.