自然写作

写作 社区 v1.0.0

技能解读

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

1.加载manifest和核心层

阅读manifest.yaml。它声明了轴(paper_type、section、language、journal)、允许的值以及每个值映射到的文件路径。另请阅读always_load下列出的每个文件。它们保留适用于每个绘图作业的默认立场、写作工作流程和输出格式。

2.检测该请求的轴值

对于清单中的每个轴,使用清单的 detect: 提示和用户输入来确定值:paper_type — 研究/方法/假设/算法/审查。默认:研究。 section — 摘要/介绍/相关工作/方法/实验/讨论/结论/标题。可能是多个。询问用户是否有歧义以及对草稿是否重要。 language — en 或 zh-to-en。从用户自己的笔记中检测。

3.加载匹配的片段

对于每个轴值,读取清单中映射的文件。仅当用户明确要求没有节上下文的自由浮动参数段落时,才跳过 section 轴。不要阅读static/中的每个片段。仅加载步骤 2 选择的内容。

4. 使用加载的材料绘制草稿

按此优先顺序应用加载的片段:核心立场+摄入(core/stance.md)-起草前表面缺失的主张/证据/边界。纸质剧本——论证链、起草顺序。具体章节的起草规则和结构。期刊特定的框架和限制。

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

references/下的文件是深度引用和示例库,而不是默认值。根据清单中的references.on_demand表按需打开它们。典型的触发因素:用户要求提供具体示例或模板 → references/examples/index.md。章节的草稿存在结构问题,章节片段本身无法解释 → 匹配的references/<section>.md。用户需要一个广泛的受众Nature摘要开场或询问summary paragraph→references/nature-summary-paragraph.md。

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

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

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

# Nature-Style Scientific Writing — Router

This skill is split into two layers:

- A **static layer** under `static/` that holds versioned, reusable content fragments (core stance + workflow, paper-type playbooks, per-section drafting guidance, language-specific rules, per-journal style).
- A **dynamic layer** (this file plus `manifest.yaml`) that detects the request's axes and loads only the fragments needed for the current job.

Do not try to apply the drafting 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 axes (`paper_type`, `section`, `language`, `journal`), the allowed values, and the file paths each value maps to.

Also read every file listed under `always_load`. These hold the default stance, writing workflow, and output format that apply to every drafting job.

### 2. Detect the axis values for this request

For each axis in the manifest, decide the value using the manifest's `detect:` hint and the user's input:

- `paper_type` — research / methods / hypothesis / algorithmic / review. Default: research.
- `section` — abstract / intro / related-work / method / experiments / discussion / conclusion / title. May be multiple. Ask the user if it is ambiguous and matters for the draft.
- `language` — en or zh-to-en. Detect from the user's notes themselves.
- `journal` — nature / nat-comms / generic. Default: generic. If the user names a Nature subjournal, treat it as `nature`.

State the detected axis values in one short line to the user before drafting, so they can correct you cheaply.

### 3. Load the matching fragments

For each axis value, Read the file mapped in the manifest. Skip the `section` axis only when the user has explicitly asked for a free-floating argument paragraph with no section context.

Do **not** read every fragment in `static/`. Load only what step 2 selected.

### 4. Draft using the loaded material

Apply the loaded fragments in this priority order:

1. Core stance + intake (`core/stance.md`) — surface missing claim / evidence / boundary before drafting.
2. Paper-type playbook — argument chain, drafting order.
3. Section-specific drafting rules and structure.
4. Journal-specific framing and constraints.
5. Language-specific sentence and paragraph rules (apply last).

Run the 8-step workflow in `core/workflow.md` end-to-end. Do not skip steps 1-3 (planning) just because the user asked for prose immediately — write the one-sentence argument first.

If essential evidence or boundary is missing, write a placeholder and list it under `Assumptions or missing inputs:` instead of inventing content.

### 5. Reach for references only when needed

The files under `references/` are deep references and the example library, not defaults. Open them on demand per the `references.on_demand` table in the manifest. Typical triggers:

- The user asks for a concrete example or template → `references/examples/index.md`.
- A section's draft has structural problems that the section fragment alone does not explain → the matching `references/<section>.md`.
- The user needs a broad-audience `Nature` abstract opening or asks about a `summary paragraph` → `references/nature-summary-paragraph.md`.
- The user asks "does this paragraph flow?" → `references/paragraph-flow.md`.
- The user asks for a self-review or rejection-risk audit → `references/paper-review.md`.

## Why this split

- The static layer is versioned and reviewable. Adding a new journal style, paper type, or section is one new file plus one manifest line.
- The dynamic layer keeps each invocation cheap: only the fragments relevant to this draft enter context, instead of the full multi-thousand-line reference set.
- The router itself is short on purpose. Update fragments, not this file, when adding scope.
- This structure mirrors `nature-polishing` so shared content can later be lifted into a `_shared/` layer used by both skills.

讨论

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