自然引用

其他 社区

技能解读

当前原文的自动摘译,尚未人工审校。

1.加载manifest和核心层

阅读manifest.yaml。然后阅读always_load:static/core/principles.md下列出的每个文件——技能产生的内容、严格的期刊范围、来源层次结构和搜索质量规则。 static/core/chinese-mode.md — 当用户使用中文书写或要求Nature系列/CNS及子刊风格支持时如何操作。 static/core/workflow.md — 七步工作流程和最终报告格式。

2. 无内容轴——内联确认范围和语言

与其他 nature-* 技能不同,自然引用没有片段轴。它的变化是运行时参数,而不是不同的内容体:期刊范围 - Nature系列 / CNS / CNS及子刊 / 仅旗舰版。从用户的措辞中读取它(参见core/principles.md)并将其作为--scope传递给脚本。用户语言 — 如果用户写中文,请遵循core/chinese-mode.md(中文注释,英文搜索查询)。

3. 运行工作流程

请遵循core/workflow.md中的七个步骤:分段、解析、搜索、保守地评估支持、导出一个参考管理器文件、在有用时生成审阅工件,并首先使用 HTML 浏览器路径进行报告。当可以访问互联网时,首选使用scripts/nature_citation.py进行搜索/导出;打开references/script-usage.md查看其完整的标志列表和长文章批量策略。

4. 仅在需要时才获取参考资料

references/下的文件是深层引用,而不是默认文件。根据清单中的references.on_demand表按需打开它们:运行脚本、完整标志、长文章批处理→references/script-usage.md。将声明转化为搜索查询和支持等级 → references/search-strategy.md。确切的 Nature/CNS 期刊家族边界 → references/journal-scope.md。 RIS / EndNote / Zotero RDF 导出详细信息 → references/ris-endnote.md。

为何如此分裂

静态层是版本化且可审查的;在正常的短期内,核心保持较小。动态层使每次调用都很便宜:脚本标志转储和长文章策略仅在实际运行搜索时加载。路由器本身故意较短。添加范围时更新片段和引用,而不是此文件。该结构镜像nature-writing、nature-polishing、nature-reader、nature-paper2ppt和nature-figure。

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
通用
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@Yuan1z0825 · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
即装即用
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) SKILL.md

# Nature Citation — Router

This skill is split into two layers:

- A **static layer** under `static/` that holds versioned, reusable content fragments (core principles and scope, the Chinese-user operating mode, and the citation workflow).
- A **dynamic layer** (this file plus `manifest.yaml`) that loads the core every time and reaches for heavier material only when a step needs it.

Do not try to apply the citation 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/principles.md` — what the skill produces, the strict journal scope, the source hierarchy, and the search-quality rules.
- `static/core/chinese-mode.md` — how to operate when the user writes in Chinese or asks for `Nature系列`/`CNS及子刊` style support.
- `static/core/workflow.md` — the seven-step workflow and the final report format.

### 2. No content axis — confirm scope and language inline

Unlike the other nature-* skills, nature-citation has no fragment axis. Its variation is runtime parameters, not different content bodies:

- **journal scope** — `Nature系列` / `CNS` / `CNS及子刊` / flagship-only. Read it from the user's wording (see `core/principles.md`) and pass it to the script as `--scope`.
- **user language** — if the user writes Chinese, follow `core/chinese-mode.md` (Chinese notes, English search queries).
- **input length** — if there are more than ~10 segments, switch to the batched long-article strategy in `references/script-usage.md`.

State the detected scope and date limits in one short line before searching.

### 3. Run the workflow

Follow the seven steps in `core/workflow.md`: segment, parse, search, evaluate support conservatively, export one reference-manager file, generate review artifacts when useful, and report with the HTML browser path first. Prefer `scripts/nature_citation.py` for the search/export when internet access is available; open `references/script-usage.md` for its full flag list and the long-article batch strategy.

Never present a paper as support merely because its title is related, and never cite a metadata-only candidate without checking the abstract or publisher page. Do not invent missing bibliographic fields.

### 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:

- running the script, full flags, long-article batching → `references/script-usage.md`.
- turning a claim into search queries and support grades → `references/search-strategy.md`.
- the exact Nature/CNS journal-family boundary → `references/journal-scope.md`.
- RIS / EndNote / Zotero RDF export details → `references/ris-endnote.md`.

## Why this split

- The static layer is versioned and reviewable; the core stays small for a normal short run.
- The dynamic layer keeps each invocation cheap: the script flag dump and long-article strategy load only when actually running a search.
- 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`, and `nature-figure`.

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。