自然数据
- 作者仓库星标 16,057
- 作者仓库 nature-skills
- 领域
- 数据
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @Yuan1z0825 · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Nature Data Availability — Router
This skill is split into two layers:
- A **static layer** under `static/` that holds versioned, reusable content fragments (the default stance and source hierarchy, the Chinese-user operating mode, and the workflow with output format).
- A **dynamic layer** (this file plus `manifest.yaml`) that loads the core every time and reaches for the deeper policy/repository/FAIR references only when a step needs them.
Do not try to apply the data-availability logic from memory or from this router. Always load fragments from disk as described below.
## Routing protocol
Follow these four steps every time the skill is invoked.
### 1. Load the manifest and the core layer
Read [manifest.yaml](manifest.yaml). Then read every file listed under `always_load`:
- `static/core/stance.md` — what the data-availability package is, the default stance, and the source hierarchy.
- `static/core/chinese-mode.md` — how to operate when the user writes in Chinese (accept Chinese, draft English, convert terms precisely).
- `static/core/workflow.md` — the eight-step workflow and the output format.
### 2. No content axis — confirm journal and language inline
Unlike nature-writing or nature-figure, nature-data has no fragment axis. Its variation is handled at runtime, not by loading different content bodies:
- **journal/article type** — if journal-specific instructions conflict with this skill, follow the journal.
- **access route** — each dataset is classified into one route (public repository, controlled access, within paper, reused public, third-party restricted, justified request, or not applicable).
- **user language** — if the user writes Chinese, follow `core/chinese-mode.md` and add the 中文核对 block.
### 3. Run the workflow
Follow the eight-step workflow in `core/workflow.md`: identify the journal, inventory every supporting dataset, classify each into one access route, choose repository and identifier strategy before drafting, draft the statement with explicit dataset-to-location mapping, add formal dataset citations, run the FAIR/metadata audit, and return ready-to-paste text plus unresolved fields.
Do not invent DOIs, accession numbers, repository names, licences, embargo dates, ethics approvals, access committees, or data-use conditions. Flag "available upon request" as weak unless there is a specific legal, ethical, commercial, or third-party restriction.
### 4. 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/policy-principles.md` for the governing rules and edge cases, `references/repository-and-identifiers.md` for repository/accession/DOI choices, `references/statement-patterns.md` for ready-to-adapt statements, `references/fair-metadata-checklist.md` for the FAIR audit, `references/chinese-author-alignment.md` for Chinese wording, and `references/source-basis.md` to justify a rule with its official source.
## Why this split
- The static layer is versioned and reviewable; the core stays small for a normal statement.
- The dynamic layer keeps each invocation cheap: the policy, repository, and FAIR 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`, `nature-paper2ppt`, `nature-figure`, `nature-citation`, and `nature-response`.
章节与文件索引
按说明文件中的顺序排列。
路由协议
1.加载manifest和核心层
2. 无内容轴——确认内联期刊和语言
3. 运行工作流程
4. 仅在需要时才获取参考资料
文件/命令 -> static/ · manifest.yaml · always_load · static/core/stance.md · static/core/chinese-mode.md · static/core/workflow.md · core/chinese-mode.md · core/workflow.md
内容校验值 -> 7c53c4535540
当前原文的自动摘译,尚未人工审校。
路由协议
每次调用该技能时,请遵循以下四个步骤。
1.加载manifest和核心层
阅读manifest.yaml。然后阅读
always_load下列出的每个文件:static/core/stance.md- 数据可用性包是什么,默认立场和源层次结构。static/core/chinese-mode.md— 用户用中文书写时如何操作(接受中文、起草英文、精确转换术语)。static/core/workflow.md— 八步工作流程和输出格式。2. 无内容轴——确认内联期刊和语言
与自然写作或自然人物不同,自然数据没有片段轴。它的变化是在运行时处理的,而不是通过加载不同的内容体来处理:期刊/文章类型 - 如果期刊特定的说明与此技能冲突,请遵循期刊。访问路径——每个数据集被分类为一种路径(公共存储库、受控访问、纸内访问、公共重用、第三方限制、合理请求或不适用)。
3. 运行工作流程
遵循
core/workflow.md中的八步工作流程:识别期刊,清点每个支持数据集,将每个数据集分类为一个访问路径,在起草之前选择存储库和标识符策略,使用明确的数据集到位置映射起草声明,添加正式的数据集引用,运行 FAIR/元数据审计,并返回准备粘贴的文本和未解析的字段。请勿发明 DOI、登录号、存储库名称、许可证、禁运日期、道德批准、访问委员会或数据使用条件。将“根据要求提供”标记为弱,除非有特定的法律、道德、商业或第三方限制。4. 仅在需要时才获取参考资料
references/下的文件是深层引用,而不是默认文件。根据清单中的references.on_demand表按需打开它们 - 例如,references/policy-principles.md用于管理规则和边缘情况,references/repository-and-identifiers.md用于存储库/访问/DOI选择,references/statement-patterns.md用于准备适应语句,references/fair-metadata-checklist.md用于FAIR审核,references/chinese-author-alignment.md用于中文措辞,以及references/source-basis.md用其官方来源来证明规则的合理性。