自然纸2
- 作者仓库星标 16,057
- 作者仓库 nature-skills
- 领域
- 设计与多媒体
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 92 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @Yuan1z0825 · v2.0.0 · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- Python
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Paper-to-PPTX — Router
This skill is split into two layers:
- A **static layer** under `static/` that holds versioned, reusable content fragments (core principles, toolchain policy, the 9-step workflow, output/quality rules, and per-paper-type presentation arcs).
- A **dynamic layer** (this file plus `manifest.yaml`) that detects the paper type and loads only the fragments needed for the current job. Deep design, figure, and self-review material lives in on-demand references.
Do not try to apply the deck-building logic from memory or from this router. Always load fragments from disk as described below.
## Routing protocol
Follow these five steps every time the skill is invoked.
### 1. Load the manifest and the core layer
Read [manifest.yaml](manifest.yaml). It declares the `paper_type` axis, the allowed values, and the file paths each value maps to.
Also read every file listed under `always_load`. These hold the purpose and core principle, the lean operating mode and toolchain policy, the 9-step workflow spine, and the output/quality rules that apply to every deck, plus the shared Terminology Ledger used to keep technical terms consistent across slides.
### 2. Classify the paper type
Decide the `paper_type` value using the manifest's `detect:` hint and the source:
- `discovery` — discovery / mechanism papers (question-to-evidence arc). Default.
- `methods` — methods / AI / tool / algorithm papers (problem-to-solution arc).
- `resource` — resource / dataset / atlas / omics / benchmark papers (workflow-to-validation arc).
- `clinical` — clinical / population / intervention studies (design-to-inference arc).
- `materials` — materials / chemistry / physics / engineering papers (property-to-mechanism / design-to-performance arc).
- `review` — reviews / perspectives / commentaries / meta-analyses (evidence-map arc).
State the detected value in one short line to the user before designing slides, so they can correct you cheaply.
### 3. Load the matching fragment
Read the file mapped for the detected `paper_type`. It gives the presentation arc and how to adapt the default slide structure for this type. Do **not** read every fragment in `static/`.
### 4. Build the deck using the loaded material
Apply the loaded fragments in this priority order:
1. Core principles (`core/principles.md`) — the argument is the spine; lean operating mode; accepted inputs; Chinese-by-default language rule.
2. Toolchain policy and fast path (`core/toolchain.md`) — cross-platform Python-first stack, default fast path.
3. Paper-type arc (the loaded `paper_type` fragment) — narrative order and slide structure for this paper.
4. Workflow (`core/workflow.md`) — run the 9 steps end to end.
5. Output and quality rules (`core/output-and-quality.md`) — deliverables, quality gates, fallbacks.
Build the Terminology Ledger (`../_shared/core/terminology-ledger.md`) while reading the source, so model names, gene/protein names, datasets, metrics, and abbreviations stay identical across every slide and speaker note.
The end product is a real `.pptx` deck, not an outline or script. Do not fabricate results, numbers, or figure details.
### 5. 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:
- composing/auditing slide layout, visual rhythm, typography, anti-template design, archetypes, on-slide text budget → `references/design-and-layout.md`.
- selecting, extracting, cropping, and quality-checking figure/table assets → `references/figure-assets.md`.
- running the self-review/corrective revision loop, severity grading, programmatic python-pptx checks, rendered-preview policy, and final verification → `references/self-review.md`.
## Why this split
- The static layer is versioned and reviewable. Adding a new paper-type arc is one new fragment plus one manifest line.
- The dynamic layer keeps each invocation cheap: only the arc for this paper enters context up front; heavy design and QA material loads only when that step runs.
- The router itself is short on purpose. Update fragments, not this file, when adding scope.
- This structure mirrors `nature-writing`, `nature-polishing`, and `nature-reader` so shared content lives in `_shared/`.
章节与文件索引
按说明文件中的顺序排列。
路由协议
1.加载manifest和核心层
2.按纸张类型分类
3.加载匹配的片段
4. 使用加载的材料构建甲板
文件/命令 -> static/ · manifest.yaml · paper_type · always_load · detect: · discovery · methods · resource
内容校验值 -> 795b23a702b1
当前原文的自动摘译,尚未人工审校。
路由协议
每次调用该技能时,请遵循以下五个步骤。
1.加载manifest和核心层
阅读manifest.yaml。它声明了
paper_type轴、允许的值以及每个值映射到的文件路径。另请阅读always_load下列出的每个文件。这些包含目的和核心原则、精益操作模式和工具链策略、9 步工作流程主干、适用于每个平台的输出/质量规则,以及用于保持幻灯片之间技术术语一致的共享术语分类帐。2.按纸张类型分类
使用清单的
detect:提示和来源确定paper_type值:discovery— 发现/机制论文(问题到证据弧)。默认。methods——方法/人工智能/工具/算法论文(问题到解决方案的弧线)。resource— 资源/数据集/图集/组学/基准论文(工作流程到验证弧)。clinical— 临床/人群/干预研究(设计到推理弧)。3.加载匹配的片段
读取检测到的
paper_type映射的文件。它提供了演示文稿弧线以及如何调整此类型的默认幻灯片结构。不要阅读static/中的每个片段。4. 使用加载的材料构建甲板
按以下优先顺序应用加载的片段: 核心原则 (
core/principles.md) — 参数是脊柱;精益运营模式;接受的输入;默认语言规则为中文。工具链策略和快速路径(core/toolchain.md)——跨平台Python优先堆栈,默认快速路径。纸型弧线(加载的paper_type片段)——本文的叙述顺序和幻灯片结构。