Nature Skills: Reusable Research Skills for AI Scholars

License Install Skills Language

Website · Install · Quick Start · Skill Index · Other Install · Contributing · 中文

--- `nature-skills` collects reusable research skills for AI scholars worldwide, with an emphasis on real problem solving, verifiable workflows, and research outputs that can be used directly. ## Table of Contents - [1. Project Founder and Operations](#1-project-founder-and-operations) - [2. Nature Skills Core Developers](#2-nature-skills-core-developers) - [3. Project Philosophy and Community](#3-project-philosophy-and-community) - [4. Quick Start](#4-quick-start) - [5. Installation](#5-installation) - [5.1 `npx skills` Installation](#51-npx-skills-installation) - [5.2 Claude Code Installation](#52-claude-code-installation) - [5.3 Codex Installation](#53-codex-installation) - [5.4 Other Agent Scenarios](#54-other-agent-scenarios) - [6. Skill Index](#6-skill-index) - [7. Contribution and Development](#7-contribution-and-development) - [8. Star History](#8-star-history) ## 1. Project Founder and Operations ### 1.1 Founder Introduction Hello, I am Yizhe Yuan, the founder of `nature-skills`. Thank you for following this project. We have published many video tutorials on Douyin; search by topic name to find them, and I sincerely hope they help with real research work. ### 1.2 Knowledge Planet Knowledge Planet name: **Nature Skills and the Philosophy Behind It**. Nature Skills Knowledge Planet ### 1.3 Repository Store - **Services**: ChatGPT Plus/Pro top-ups and ready-made accounts, with official invoices and optional warranty coverage at checkout. - **Service page**: [https://apiciyuan.top/cat/3](https://apiciyuan.top/cat/3) - **Customer-service WeChat**: `naturegpt888` (consultation / invoices) ChatGPT Plus and Pro services ## 2. Nature Skills Core Developers | Developer | Project Role | Main Focus and Contributions | Profiles and Contact | |---|---|---|---| | **Yizhe Yuan** | Founder / Maintainer | Project initiation, skill-system design, and community operations | — | | **Xin-Rui Ma** | Core Developer | Day-to-day skills maintenance | [Gmail](mailto:travisma2233@gmail.com) | | **Bin Hu** | Major Contributor | Agentic agents and AI for Science | [GitHub](https://github.com/Flyme886) · [Email](mailto:mhoang12205@gmail.com) | ## 3. Project Philosophy and Community ### 3.1 Some Personal Views - Recently, I noticed that the Nature Skills design has drawn attention from Google DeepMind and has been referenced by them. They drew on its citation system, script ideas, and skill-design philosophy to launch Science Skills. To be honest, this makes me pleased: when leading international AI institutions begin to draw inspiration from our work, it means original ideas from Chinese developers are being seen by the world. This is not a feeling of loss from being copied, but a sign of Chinese strength taking root in open source and naturally growing outward. - The focus of our skill design has never been to require every user to fully master the whole philosophy. The point is that the philosophy itself can be understood and reused by machines. If you want to create a new skill or adapt this system to your own field, you can give the Nature Skills GitHub repository to Codex and let it learn the design pattern, then help you create or modify a skill. This is how ideas become operational rather than remaining oral explanations. - The real value of Nature Skills may not be limited to any individual module. It may be that the project has quietly opened a new door: many people realize for the first time that Codex or other agents can operate a local computer for research. I have been fortunate to witness and accompany many people through this shift in research workflow. When they say, "so research can be done this way," that break in understanding and liberation of thought matters more to me than the skills themselves. This is not merely the success of a tool, but the beginning of a new way of thinking spreading among people. - In practice, almost every useful tool can be distilled into a standardized process, and standardized processes can be packaged as reusable skills. ### 3.2 Tutorials and Community
Follow Douyin for video tutorials
Douyin tutorials 		Agent Research Community
Agent Research Community 		Yuan's personal WeChat
personal WeChat
## 4. Quick Start After installation, you can give the agent a paper, paragraph, reviewer letter, or task description directly. These prompts are ready to copy: | Goal | Prompt | | --- | --- | | Read a paper / bilingual reader | `Turn this PDF into a figure-aware Chinese-English Markdown reader.` | | Generate a paper presentation | `Create a Chinese journal-club PPT from this paper, keeping key figures and source labels.` | | Polish or translate a manuscript paragraph | `Rewrite this Chinese paragraph into Nature-style academic English without changing the meaning.` | | Draft an abstract, introduction, or discussion | `Using these results and figures, draft a Nature-style abstract and introduction.` | | Simulate pre-submission review | `Evaluate this manuscript from a Nature reviewer perspective and produce three reviewer reports.` | | Respond to reviewer comments | `Use this revision email to draft point-by-point replies, a cover letter, and redline locations for the revised manuscript.` | | Search literature, strict citations, and citer profiles | `Create a table with this paper's citation count, strict external citation count, DOI, and whether major scholars or Fellows cited it.` | | Create scientific figures or schematics | `Use this method and result description to draft a publication-ready scientific figure or manuscript schematic.` | If you are unsure which skill to use, describe the task naturally. If you already know the skill name, explicitly say "use `nature-reader`" or "use `nature-response`" in the prompt. ## 5. Installation `nature-skills` is a collection of reusable skill packages organized around `SKILL.md`. Each top-level skill directory under `skills/` is an installable unit, such as `nature-*`; `nature-shared` is an installable support package read by other skills. ### 5.1 `npx skills` Installation Install [Node.js 18 or later](https://nodejs.org/) first. The CLI does not need to be installed globally. List the skill names available in this repository: ```bash npx skills add Yuan1z0825/nature-skills --list ``` Install every skill globally for Codex. The complete selection includes `nature-shared`, so skills that use the common references remain functional: ```bash npx skills add Yuan1z0825/nature-skills --global --agent codex --skill '*' --yes --copy ``` Omit `--global` to install one independent skill in the current project: ```bash npx skills add Yuan1z0825/nature-skills --agent codex --skill nature-figure --yes --copy ``` When installing `nature-reader`, `nature-paper2ppt`, `nature-polishing`, or `nature-writing` alone, select the shared support package as well: ```bash npx skills add Yuan1z0825/nature-skills --global --agent codex \ --skill nature-reader --skill nature-shared --yes --copy ``` Install all skills for every agent supported by the CLI: ```bash npx skills add Yuan1z0825/nature-skills --all ``` Verify the global Codex installation and update it later: ```bash npx skills list --global --agent codex --json npx skills update --global --yes ``` Update one skill, or update only the current project's skills: ```bash npx skills update nature-reader --global --yes npx skills update --project --yes ``` Pass the frontmatter name displayed by `--list` to `--skill`; for example, the `nature-proposal-writer` directory is currently listed as `researchwrite`. `npx skills` manages skill files only. Optional Python, R, browser, and MCP runtime dependencies still need the separate setup described below. ### 5.2 Claude Code Installation Claude Code cannot use `scripts/update-codex-skills.sh` directly because that script only syncs skills into Codex's `~/.codex/skills/`. For Claude Code, keep a stable local clone and create a subagent or slash command wrapper that points to the real `skills/*/SKILL.md`. This preserves the skill directory structure and lets the workflow keep using `references/`, `static/`, `manifest.yaml`, scripts, assets, and `skills/nature-shared/`. If Claude Code is not installed yet: ```bash npm install -g @anthropic-ai/claude-code claude ``` Clone the repository to a stable path: ```bash mkdir -p ~/ai-skills cd ~/ai-skills git clone https://github.com/Yuan1z0825/nature-skills.git ``` Recommended method: create a Claude Code subagent wrapper for the skills you use often. Example for `nature-reader`: ```bash mkdir -p ~/.claude/agents cat > ~/.claude/agents/nature-reader.md <<'EOF' --- name: nature-reader description: Use for Chinese-English paper reading, figure-aware translation, and source-grounded paper notes. --- When invoked, first read `~/ai-skills/nature-skills/skills/nature-reader/SKILL.md` and follow it as the governing workflow. Read supporting files from `~/ai-skills/nature-skills/skills/nature-reader/` and `~/ai-skills/nature-skills/skills/nature-shared/` only when needed. Do not replace this skill with a generic paper-reading response. EOF ``` Then start a new Claude Code session and ask for the subagent explicitly: ```text Use the nature-reader subagent to turn this paper into a Chinese-English Markdown reader. ``` If you prefer a slash command, create a command wrapper instead: ```bash mkdir -p ~/.claude/commands cat > ~/.claude/commands/nature-reader.md <<'EOF' Read `~/ai-skills/nature-skills/skills/nature-reader/SKILL.md` first and follow it strictly. Read directly needed supporting files from `~/ai-skills/nature-skills/skills/nature-reader/` and `~/ai-skills/nature-skills/skills/nature-shared/`. $ARGUMENTS EOF ``` Use it inside Claude Code: ```text /nature-reader Turn this paper into a full Chinese-English side-by-side Markdown reader. ``` To install other skills, replace `nature-reader` with the target directory name, such as `nature-polishing`, `nature-writing`, `nature-reviewer`, `nature-response`, or `nature-figure`. To update later: ```bash cd ~/ai-skills/nature-skills git pull ``` As long as the wrapper still points to this stable clone path, no repeated file copy is needed. **Auto-Update (Optional)** If you want Claude Code to pull upstream updates automatically on every session start, use `scripts/autoupdate-skills.sh` together with a `SessionStart` hook. This approach **copies** the skills straight into `~/.claude/skills/` (Claude Code auto-discovers that directory and loads each skill by its directory name) instead of using the wrappers above. Pick whichever one you prefer. Keep a **dedicated** stable clone (used only to sync skills — don't make dev commits inside it): ```bash mkdir -p ~/ai-skills git clone https://github.com/Yuan1z0825/nature-skills.git ~/ai-skills/nature-skills ``` Install once, copying the skills into Claude Code's skills directory: ```bash ~/ai-skills/nature-skills/scripts/autoupdate-skills.sh --force ``` Then add a `SessionStart` hook to `~/.claude/settings.json` (merge this entry into an existing `hooks` block rather than replacing it): ```json { "hooks": { "SessionStart": [ { "hooks": [ { "type": "command", "command": "$HOME/ai-skills/nature-skills/scripts/autoupdate-skills.sh", "async": true, "timeout": 120 } ] } ] } } ``` `async: true` runs it in the background so it never blocks startup. The script is safe to run constantly: it skips the network if it already checked within the last 6 hours, silently skips when offline or the pull fails (`exit 0`, never stalling a session), re-syncs only when the upstream HEAD actually changed, and refuses to fast-forward a clone that has uncommitted changes. New skills take effect on the **next** session (the current one already loaded its skills). Logs go to `~/.local/state/nature-skills/autoupdate.log`. The destination and check interval are both configurable: ```bash # Defaults to ~/.claude/skills; use --dest for another location, e.g. Codex: ~/ai-skills/nature-skills/scripts/autoupdate-skills.sh --dest ~/.codex/skills # Check at most once per hour: ~/ai-skills/nature-skills/scripts/autoupdate-skills.sh --throttle 3600 ``` ### 5.3 Codex Installation Use the repository script to install or update Codex skills. It syncs every top-level skill directory under `skills/` and verifies the copied contents with `diff`. It does not overwrite unrelated Codex skills. ```bash git clone https://github.com/Yuan1z0825/nature-skills.git cd nature-skills scripts/update-codex-skills.sh --pull ``` If you already have a clone: ```bash cd nature-skills scripts/update-codex-skills.sh --pull ``` Verify that the current Codex installation matches this checkout: ```bash scripts/update-codex-skills.sh --check ``` If you use this script for long-term updates and want to remove directories that were previously managed by this installer but no longer exist upstream: ```bash scripts/update-codex-skills.sh --pull --prune ``` `--prune` only removes directories recorded by this installer. It will not guess or delete unrelated skills. You can also ask Codex to install the repository for you: ```text Install Codex skills from this repository: https://github.com/Yuan1z0825/nature-skills.git Clone the repository, run scripts/update-codex-skills.sh --pull, and then run scripts/update-codex-skills.sh --check to verify the installation. Keep complete skill directories under skills/; do not copy only SKILL.md. ``` To install only one skill, specify the skill name: ```text Install only nature-reader from this repository: https://github.com/Yuan1z0825/nature-skills.git If the skill needs shared files, install skills/nature-shared as well. ``` Key rule: keep the full directory structure. Many skills depend on `references/`, `static/`, `manifest.yaml`, scripts, assets, or shared files. The installer does not install Python dependencies automatically. Install them only when you need the corresponding scripts or MCP services: ```bash python -m pip install -r skills/nature-paper-to-patent/requirements.txt python -m pip install -r skills/nature-paper-to-patent/scripts/disclosure/requirements-cnipa.txt # optional CNIPA published-patent search python -m pip install -r skills/nature-academic-search/mcp-server/requirements.txt ``` If you enable `nature-paper-to-patent` CNIPA published-patent search, also run `python -m playwright install chromium`. `nature-academic-search` also requires `PUBMED_EMAIL`. Optional Scopus, ScienceDirect, and other provider credentials should be configured locally and must not be committed to the repository. After installation, start a new Codex session and describe your task naturally, for example: ```text Turn this paper into a full Chinese-English side-by-side Markdown reader. ``` ```text Create a Chinese PPT deck from this paper. ``` For OpenClaw, OpenCode, Hermes, and other open-source agent frameworks, see the [OpenClaw / OpenCode / Hermes integration guide](docs/open-source-agent-frameworks_EN.md). **Auto-Update (Optional)** Codex supports a global `SessionStart` hook. With a dedicated clone, it can check for updates whenever a Codex session starts or resumes and sync new versions into `~/.codex/skills/`. Create the dedicated clone and perform the initial sync: ```bash mkdir -p ~/.codex git clone https://github.com/Yuan1z0825/nature-skills.git ~/.codex/.nature-skills-src ~/.codex/.nature-skills-src/scripts/autoupdate-skills.sh \ --dest ~/.codex/skills --force ``` Then create or merge `~/.codex/hooks.json`: ```json { "hooks": { "SessionStart": [ { "matcher": "startup|resume", "hooks": [ { "type": "command", "command": "/bin/bash \"$HOME/.codex/.nature-skills-src/scripts/autoupdate-skills.sh\" --dest \"$HOME/.codex/skills\"", "timeout": 75, "statusMessage": "Checking Nature Skills updates" } ] } ] } } ``` If `hooks.json` already contains other hooks, merge the `SessionStart` entry instead of replacing the file. After enabling or changing the hook, run `/hooks` in Codex to review and trust it. Codex currently runs command hooks synchronously, so this setup relies on the script's built-in 6-hour throttle, 60-second network guard, and offline-safe exit to avoid repeated network checks or blocking startup when an update cannot be fetched. Logs are written to `~/.local/state/nature-skills/autoupdate.log`. Newly fetched skills normally take full effect in the next session. ### 5.4 Other Agent Scenarios For OpenClaw, OpenCode, and Hermes, see the dedicated [integration guide](docs/open-source-agent-frameworks_EN.md). For other agents, keep a stable repository clone and create a lightweight subagent, slash command, or custom prompt wrapper that points to the real `skills/*/SKILL.md` files. Preserve `skills/nature-shared/`. For manual or other-agent use: 1. Copy complete skill directories into your prompt library or project. 2. Preserve `SKILL.md`, `manifest.yaml`, `static/`, `references/`, scripts, assets, and required `skills/nature-shared/` files. 3. If the target agent has its own format requirements, adjust the frontmatter and body structure. ## 6. Skill Index The current `skills/` directory contains the following triggerable skills. `skills/nature-shared/` is shared content and is not counted in the skill index. Click a skill name or the "Details" link to open its dedicated documentation page. | Skill | Status | Purpose | Example Triggers | Details | |---|---|---|---|---| | [`nature-figure`](skills/nature-figure/README_EN.md) | Stable | Submission-grade Python or R scientific figure workflow for Nature / high-impact journals, with a figures4papers-style demo and OpenRouter GPT Image 2 schematic-draft generation | "Nature figure", "submission-grade figure", "publication plot", "scientific figure", "figures4papers", "paper schematic", "GPT Image 2" | [Details](skills/nature-figure/README_EN.md) | | [`nature-polishing`](skills/nature-polishing/README_EN.md) | Stable | Polish, restructure, or translate academic prose into Nature-style English | "Nature style", "polishing", "academic writing", "English manuscript" | [Details](skills/nature-polishing/README_EN.md) | | [`nature-writing`](skills/nature-writing/README_EN.md) | Draft | Draft Nature-style manuscript sections and rebuild a paper argument | "Nature writing", "write an abstract", "write introduction", "manuscript draft", "paper writing" | [Details](skills/nature-writing/README_EN.md) | | [`nature-reviewer`](skills/nature-reviewer/README_EN.md) | Draft | Simulate Nature-style reviewer assessment from the reviewer perspective, returning three reviewer reports and a synthesis | "Nature reviewer", "pre-submission review", "reviewer report", "reviewer-perspective assessment" | [Details](skills/nature-reviewer/README_EN.md) | | [`nature-citation`](skills/nature-citation/README_EN.md) | Beta | Search support literature strictly within Nature / CNS families and export ENW, RIS, or Zotero RDF | "Nature citation", "CNS citation", "segmented citation", "supporting references", "Zotero RDF" | [Details](skills/nature-citation/README_EN.md) | | [`nature-data`](skills/nature-data/README_EN.md) | Draft | Prepare Data Availability statements, data repository plans, and FAIR checks | "Data Availability", "data availability", "repository", "FAIR metadata" | [Details](skills/nature-data/README_EN.md) | | [`nature-statistics`](skills/nature-statistics/README_EN.md) | Draft | Audit, revise, or draft statistical reporting for Nature / high-impact journal manuscripts, covering sample size, independent units, replicates, p values, multiple comparisons, effect sizes, confidence intervals, figure statistics, and reviewer comments | "Nature statistics", "statistical analysis", "p value", "sample size", "replicates", "multiple comparisons", "figure statistics", "statistics review" | [Details](skills/nature-statistics/README_EN.md) | | [`nature-reader`](skills/nature-reader/README_EN.md) | Beta | Generate full-paper Markdown readers with source anchors, figure-text alignment, and Chinese-English side-by-side translation | "nature reader", "full Markdown", "source-aligned text", "figure-text alignment", "full translation" | [Details](skills/nature-reader/README_EN.md) | | [`nature-response`](skills/nature-response/README_EN.md) | Beta | Parse revision emails; draft, audit, and revise revision cover letters, point-by-point response letters, red-marked manuscripts, and LaTeX templates | "response to reviewers", "rebuttal letter", "cover letter", "major revision", "revision email", "reviewer-comment response", "LaTeX template" | [Details](skills/nature-response/README_EN.md) | | [`nature-paper2ppt`](skills/nature-paper2ppt/README_EN.md) | Beta | Generate Chinese PPTX journal-club or paper-presentation decks from research papers | "paper PPT", "journal club", "paper to slides", "paper presentation" | [Details](skills/nature-paper2ppt/README_EN.md) | | [`nature-paper-to-patent`](skills/nature-paper-to-patent/README_EN.md) | Beta | Generate evidence-constrained Chinese invention patent drafts and support patent-point mining, prior-art search, and iterative technical disclosure drafting | "paper to patent", "Chinese patent", "paper-to-patent", "claims drafting", "technical disclosure", "patent points" | [Details](skills/nature-paper-to-patent/README_EN.md) | | [`nature-ref-verifier`](skills/nature-ref-verifier/README_EN.md) | Beta | Cross-check references across multiple sources and flag author, title, year, volume, issue, and page inconsistencies | "verify refs", "check references", "reference verification", "ref check" | [Details](skills/nature-ref-verifier/README_EN.md) | | [`nature-academic-search`](skills/nature-academic-search/README_EN.md) | Beta | Multi-source literature search, citation verification, strict other-citation audits, article-level citation metric tables, influential citer profiling, and reference management | "search papers", "find articles", "literature search", "literature lookup", "verify DOI", "strict other citation", "article citation table", "influential citer" | [Details](skills/nature-academic-search/README_EN.md) | | [`nature-downloader`](skills/nature-downloader/README_EN.md) | Beta | Legally obtain academic full text/PDFs through library access, Chrome login state, and open-access routes | "download papers", "library paper download", "CARSI", "Web of Science", "PDF download" | [Details](skills/nature-downloader/README_EN.md) | | [`nature-literature-pipeline`](skills/nature-literature-pipeline/README_EN.md) | Stable | Automated literature discovery pipeline: multi-source retrieval, six-axis scoring, deep-reading delivery, and local archiving | "literature pipeline", "daily literature", "literature push", "daily literature push", "cron" | [Details](skills/nature-literature-pipeline/README_EN.md) | | [`nature-experiment-log`](skills/nature-experiment-log/README_EN.md) | Draft | Standardize experiment images, voice, and text into Obsidian experiment logs with YAML frontmatter and archived source materials | "experiment log", "record experiment", "Obsidian vault", "Feishu research group" | [Details](skills/nature-experiment-log/README_EN.md) | | [`nature-proposal-writer`](skills/nature-proposal-writer/README_EN.md) | Beta | Proposal-first research writing state machine: establish evidence, argument, and section contracts before drafting or reviewing text | "researchwrite", "proposal", "opening report", "research plan", "research writing QA" | [Details](skills/nature-proposal-writer/README_EN.md) | ## 7. Contribution and Development ### 7.1 Shared Design Principles 1. **Prefer primary sources**: rules should be grounded in published Nature content, official journal guidance, or explicit local sources rather than generic taste. 2. **Make rules explicit**: explain the reason behind each rule instead of giving unsupported assertions. 3. **Respect section and task context**: writing, figures, citations, and responses depend on the manuscript section and task. 4. **Output first**: every skill should produce something directly usable, such as paste-ready text, `.svg`, `.pptx`, `.docx`, or concrete instructions. 5. **Keep skills extensible**: each skill should be self-contained, and adding a new skill should not require modifying existing skills. ### 7.2 Repository Layout ```text skills/ ├── nature-shared/ # keep this when skills reference ../nature-shared ├── nature-/ │ ├── README.md │ ├── README_EN.md │ ├── SKILL.md │ ├── manifest.yaml # present in router-style skills │ ├── static/ # present in router-style skills │ └── references/... └── nature-proposal-writer/ ├── README.md ├── README_EN.md ├── SKILL.md ├── scripts/... ├── templates/... └── references/... ``` ### 7.3 Adding a Skill When adding a skill to this repository, follow this process. **1. Create the skill directory** ```text skills/nature-/ ``` **2. Add required files** | File | Required | Purpose | |---|---:|---| | `SKILL.md` | Yes | Frontmatter (`name`, `description`) plus rules and workflow loaded by the agent | | `README.md` | Yes | Human-facing Chinese documentation | | `README_EN.md` | Yes | English documentation paired with the Chinese details page | | `references/*.md` | Recommended for complex skills | Modular rule files, API references, design theory, tutorials, chart types, and similar material | **3. Write the Chinese and English READMEs** Every new skill must include both `README.md` and `README_EN.md`. The README is a human-facing entry page, not a duplicate of `SKILL.md` and not an installation manual. Its job is to help users decide within 30 seconds whether the skill fits their task, what they need to provide, what it will output, and where its boundaries are. Basic rules: - The Chinese and English README files must be one-to-one mirrors: same heading count, same order, and same information points. Do not let the English page become a separate template. - Start with the skill name, language switch link, and one positioning sentence. - Use the base structure below by default; add optional sections only when they are genuinely needed. - Do not repeat repository installation instructions, author bios, changelogs, development history, full file trees, or long internal implementation details inside a single skill README. - Put complex rules, API parameters, long tutorials, script explanations, and template indexes in `references/`, `static/`, `scripts/`, or `SKILL.md`. Keep only navigational pointers in the README. - If the skill has visual assets, a small preview table is fine; do not turn the README into a large gallery or long technical manual. Chinese README base structure: ```markdown # `nature-` 技能 [English](README_EN.md) 一句话说明这个技能的定位、主要任务和使用边界。 ## 适合用它做什么 ## 典型请求 ## 你需要提供 ## 产出 ## 边界 ## 相关技能 ``` The English README must mirror it as: ```markdown # `nature-` Skill [中文说明](README.md) One sentence describing the skill's role, main task, and usage boundary. ## What To Use It For ## Typical Requests ## What You Need To Provide ## Outputs ## Boundaries ## Related Skills ``` Optional sections must be inserted in both languages and in the same order. Common optional sections: | Chinese Section | English Section | Use Case | |---|---|---| | `## 工作方式` | `## Workflow` | Explain the core workflow or routing behavior | | `## 运行和依赖` | `## Runtime and Dependencies` | Scripts, MCP services, API keys, local config, or external dependencies | | `## 示例预览` | `## Example Preview` | A few figures, screenshots, or visual assets are worth showing | | `## 内置参考` | `## Built-In References` | Point to `references/`, `assets/`, or demos | | `## 方法来源` | `## Method Sources` | Writing, review, or analysis rules come from specific sources | | `## 三种模式` | `## Three Modes` | The skill has clear compose/revise/hybrid-style modes | | `## 与 ... 的关系` | `## Relationship With ...` | The skill is easy to confuse with another skill and needs a division-of-labor note | Before submitting, run at least these README checks: ```bash git diff --check for d in skills/nature-*; do [ -f "$d/README.md" ] && [ -f "$d/README_EN.md" ] || continue rg -q '^\[English\]\(README_EN\.md\)$' "$d/README.md" rg -q '^\[中文说明\]\(README\.md\)$' "$d/README_EN.md" test "$(rg -c '^## ' "$d/README.md")" = "$(rg -c '^## ' "$d/README_EN.md")" done ``` **4. Record a usage tutorial** When submitting a PR, please also record a short usage tutorial explaining what problem the skill solves, how to trigger it, what inputs it needs, and what outputs it produces. Add the video, screencast link, or public tutorial URL to the PR description. **5. Configure `SKILL.md` frontmatter** ```yaml --- name: nature- description: >- One sentence explaining what the skill does, when it should trigger, primary outputs, and core use cases. --- ``` **6. Update the skill index** After adding a skill, update the [Skill Index](#6-skill-index) table: ```markdown | [`nature-`](skills/nature-/README_EN.md) | Draft / Stable | One-sentence purpose | Trigger terms | [Details](skills/nature-/README_EN.md) | ``` **7. Set the status label** | Status | Meaning | |---|---| | `Draft` | Rules are defined but not yet tested on real cases | | `Beta` | Tested on examples, with possible edge-case issues | | `Stable` | Validated on real academic content and relatively stable | --- ## 8. Star History [![Star History Chart](assets/star-history.svg?v=20260715T1629Z)](https://star-history.com/#Yuan1z0825/nature-skills&Date)