自然抛光

写作 社区 v6.1.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/failure-modes.md中的paper type -> section job -> paragraph logic -> claim/evidence/boundary -> sentence polish规则:纸质剧本(架构、书写顺序)。特定于部分的工作和故障模式。期刊特定的框架和限制。特定于语言的句子和段落规则(最后应用)。

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

references/下的文件是深层引用,而不是默认文件。根据清单中的references.on_demand表按需打开它们,例如当用户明确要求短语库风格的替代方案或更严格的风格审核时。布局/排版(排版)要求不同。如果用户要求修复“位置”而不是措辞 - 松散/稀疏的页面、搁浅的标题、未填满页面或跨页面拆分的数字、“浮动太大”、多面板

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

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

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

# Nature-Style Academic Polishing — Router

This skill is split into two layers:

- A **static layer** under `static/` that holds versioned, reusable content fragments (core principles, paper-type playbooks, per-section 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 polishing 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, failure-mode diagnosis, ethics, and output format that apply to every polish 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 / results / discussion / conclusion / title / methods. May be multiple. Ask the user if it is ambiguous and matters for the polish.
- `language` — en or zh-to-en. Detect from the draft itself.
- `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 proceeding, 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 if the user has supplied free-floating prose with no section context.

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

### 4. Polish using the loaded material

Apply the loaded fragments in this priority order, matching the `paper type -> section job -> paragraph logic -> claim/evidence/boundary -> sentence polish` rule from `core/failure-modes.md`:

1. Paper-type playbook (architecture, writing order).
2. Section-specific job and failure modes.
3. Journal-specific framing and constraints.
4. Language-specific sentence and paragraph rules (apply last).
5. Core stance and ethics throughout.

If a paragraph's structural problem cannot be fixed without inventing content, flag it instead of papering over it.

### 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, for example when the user explicitly asks for phrasebank-style alternatives or a stricter style audit.

**Layout/typesetting (排版) requests are different.** If the user asks to fix
*placement* rather than wording — loose/sparse pages, stranded headings, figures
that don't fill the page or split across pages, "Float too large", multi-panel
arrangement, sparse Supplementary Information — skip the prose axes (paper_type,
section, language, journal) and load `references/latex-layout.md` directly. That
file is self-contained: it carries the diagnosis workflow (render → contact-sheet →
read the log), the float-glue and `[H]`/`\clearpage`/`placeins` patterns, and the
"regenerate wide figures taller at the source" rule. Always compile and visually
inspect rendered pages before and after — never judge layout from the `.tex` alone.

## Why this split

- The static layer is versioned and reviewable. Adding a new journal style or paper type 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 1000-line monolith.
- The router itself is short on purpose. Update fragments, not this file, when adding scope.

讨论

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