[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71F7NWCYRJG4C1WVFSDPS2H":3,"skill-same:01M71F7NWCYRJG4C1WVFSDPS2H":188},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":32,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M71F7NWCYRJG4C1WVFSDPS2H","writing-router",null,"统一写作协作流程，并处理普通中文编辑。Use when 用户要撰写、重写、润色或审查项目书、技术方案、会前技术交流稿、系统说明、专利技术交底书、测试与结果分析、调研报告、会议纪要、中文或英文论文，先确定主稿、修改范围和协作方式，再结合对应专业技能完成正文、检查与写回；也直接处理界面文案、普通中文去 AI 味、删废话和无法直接归类的中文材料。投稿事务、停稿审查、文献检索和单纯文件排版由对应专门技能处理。","SanAntonio021\u002Fagents-skills","SanAntonio021","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F56460680?v=4","01M71F2WGFWC4J9XYAKBEYGHSY","Weipeng Wang","01M71F2WHCP3JATT5FGJSXZXXC",0,"MIT","https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002FSKILL.md",[19,24,27],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":28,"categoryName":29,"taxonomyType":30,"taxonomyTypeDesc":31},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[33,34,35,36,37,38,39,40,41,42,43],"router","writing router","writing","文案","中文","testing","报告","文件","use","协作","when","2026-11-10 10:12:30",false,"---\nname: writing-router\ndescription: 统一写作协作流程，并处理普通中文编辑。Use when 用户要撰写、重写、润色或审查项目书、技术方案、会前技术交流稿、系统说明、专利技术交底书、测试与结果分析、调研报告、会议纪要、中文或英文论文，先确定主稿、修改范围和协作方式，再结合对应专业技能完成正文、检查与写回；也直接处理界面文案、普通中文去 AI 味、删废话和无法直接归类的中文材料。投稿事务、停稿审查、文献检索和单纯文件排版由对应专门技能处理。\n---\n\n# 通用写作流程与编辑\n\n## 目标\n\n统一管理如何协作、确认和交付；专业技能负责具体文体的结构、论证、证据和检查要求。进入专业技能后，共同流程继续有效；普通中文编辑由本技能直接完成。已有决定与准确授权继续沿用。\n\nMarkdown 正文写作或实质修改时，按 [Markdown 正文写法](references\u002Fmarkdown-writing.md)组织标题、段落和并列内容。确定研究、实验材料的主记录，或整合入口、专题记录、历史及跨文档引用时，读取 [Markdown 文档组织](references\u002Fmarkdown-document-organization.md)确定载体、职责和验收；完整保存分类集中在该参考，不在各入口复制。句子质量和具体文体要求仍按本技能及下游专业技能执行。\n\n## 工作流程\n\n1. 确定当前主稿、来源、模板、本轮修改范围和受保护片段，建立或沿用下方写作上下文。批量编辑时列清获准处理的文件，语言镜像仅在授权范围内纳入。\n2. 按[文稿协作](references\u002Fcollaborative-writing.md)选择直接处理、结构讨论、分批确认或只读审查；具体条件和正文循环由该参考统一维护。原文保留操作和界面短文案沿用下方专门分支。\n3. 实验方案按下方专门分支进入实验技能，其余按文体对应表加载专业技能；按最小加载规则准备共同质量要求与本轮所需资料，处理正文。共同流程贯穿专业写作，不因切换技能重复确认或重新改写。\n4. 按共同质量规则完成必要检查，再按已选协作方式交付、写回并回读。材料缺口只暂停依赖未决事实的内容；批量任务核对每篇已修改、无需修改或无法处理。默认只交付正文或审查意见，不附检查记录和改写理由；用户要求解释时与正文分开。\n\n## 原文保留操作\n\n用户明确要求正文逐字不动、仅在开头加标题或末尾追加给定文字时，按[原文保留编辑](references\u002Fexact-edit.md)直接拼接并校验。本地 UTF-8 文稿使用其中的工具生成并校验结果；已有 Markdown 主稿按单一主稿约定回写，工具所需新候选放过程目录，不作为第二份主稿。不重新生成或润色受保护正文；其他写作任务沿用共同流程。\n\n## 界面文案\n\n中文 GUI、网页或上位机的标题、按钮、字段名、状态和操作提示也属于润色范围，包括源代码里的用户可见字符串。创建或修改界面时进入此分支，先读 [界面文案检查](references\u002Fui-copy.md)，再实际读取 [style-vocab](..\u002Fstyle-vocab\u002FSKILL.md) 及其适用词表；当前任务已经加载且内容未变时复用。界面入口仍负责布局、运行和截图核验。\n\n这类短文案按 `document_type=general`、`mode=general_edit` 和已有修改范围处理；只审不改时为 `audit_only`。本分支替代长文稿流程，不要求确认提纲、分批正文或形成完整正式稿，不自动运行整份代码的文稿审计。复用现有授权，检查通过后继续原界面任务。\n\n## 写作上下文\n\n开始正文工作前，在任务内部确定以下字段；文稿、范围和阶段未变时沿用，变化时只更新相关项，不另建记录文件。普通交付不展示这段记录。评测提示包含 `TRACE_WRITING_CONTEXT=1` 时，才在文末输出同名 JSON 对象。\n\n| 字段 | 允许值 |\n|---|---|\n| `document_type` | `project`、`technical`、`research_report`、`meeting_notes`、`paper`、`general` |\n| `mode` | 使用下表中与文稿类型对应的值 |\n| `edit_scope` | `draft`、`structural`、`bounded`、`in_place`、`audit_only` |\n| `language` | `zh`、`en`、`mixed` |\n| `loaded_refs` | 本轮实际读取过的规则和样稿路径；不得登记“准备读取”或凭规则名称猜测 |\n\n`edit_scope` 的含义：\n\n- `draft`：从材料起草正文。\n- `structural`：允许调整章节、段落职责和信息顺序。\n- `bounded`：只改用户指定章节、段落或问题。\n- `in_place`：保留结构和作者声音，只做必要的原位修改。\n- `audit_only`：只审不改，按共同质量规则在对话中分点报告问题。\n\n## 专业写作衔接\n\n| `document_type` | `mode` | 主技能 |\n|---|---|---|\n| `project` | `proposal`、`expert_reply`、`final_audit` | [project-writing](..\u002Fproject-writing\u002FSKILL.md) |\n| `technical` | `technical_scheme`、`technical_exchange`、`system_description`、`patent_disclosure`、`test_result_analysis` | [technical-writing](..\u002Ftechnical-writing\u002FSKILL.md) |\n| `research_report` | `evidence_report`、`decision_report`、`final_audit` | [research-report](..\u002Fresearch-report\u002FSKILL.md) |\n| `meeting_notes` | `discussion`、`action`、`mixed` | [meeting-notes](..\u002Fmeeting-notes\u002FSKILL.md) |\n| `paper` | `zh_paper`、`en_paper`、`final_audit` | [ieee-manuscript-edit](..\u002Fieee-manuscript-edit\u002FSKILL.md) |\n| `general` | `general_edit` | 本技能的通用编辑流程 |\n\n判断顺序：\n\n1. 用户明确说出的文稿类型、用途和读者。\n2. 原文件的栏目、模板和内容职责。\n3. 仍无法区分且会改变产物时，只问一个最关键的问题；不影响实质结果时按最窄范围继续。\n\n会前方案讨论稿、技术交流材料或待讨论问题清单，目标是区分已有条件、会上决定和另行工作时，使用 `document_type=technical`、`mode=technical_exchange`。会议已经结束，任务是整理实际发言、结论和行动项时，使用 `meeting_notes`。\n\n制定、修改或续写可执行实验方案时，使用 `document_type=technical`、`mode=technical_scheme`，主技能直接选 [lab-notebook](..\u002Flab-notebook\u002FSKILL.md#讨论实验方案)，由其组织讨论进度、现场步骤和后续记录；本分支替代上表的通用技术写作入口。独立技术问答仍按下方工程判断分支直接回答。\n\n专利构思讨论、技术交底书起草或审校使用 `document_type=technical`、`mode=patent_disclosure`。仅讨论时沿用当前范围，不自动建稿；专利检索、权利要求及保护范围分析不因进入交底书模式而自动开展。\n\n按表应用对应文体技能的专业要求，共同协作与质量规则持续适用；普通中文直接在本技能完成，不另找写作入口。\n\n## 规则优先级\n\n按共同质量规则的“优先级”处理冲突；事实与关系保护、必要复述、审查输出和停笔条件均以该参考为准，文体技能补充专业要求。\n\n## 最小加载规则\n\n以下要求同样适用于直接调用文体技能；按其现有引用复用共同参考，不必先返回本入口。实际读取的路径记入 `loaded_refs`；同任务材料与规则未变时复用，已变化或无法确认读过时补读必要文件。\n\n1. 建立写作上下文后、处理正文前，读取[文稿协作](references\u002Fcollaborative-writing.md)，将实际路径记入 `loaded_refs`，据此选择直接处理或分批协作，不另加确认关口。\n2. 实际读取文体对应表选定的主技能及本轮所需参考；对应表不能代替专业规则。`general_edit` 不加载另一个写作入口。论文和 `final_audit` 只读当前稿件语言对应的细则。\n3. 各类正文都读取[共同质量规则](references\u002Fcommon-quality.md)。中文正文首次起草、续写、局部修改或审查前，按其中“中文正文展示前检查”读取 [AI 气味目录](references\u002Fai-smell-catalog.md)和 `style-vocab` 适用词表，逐批检查；混合稿只对中文部分执行。英文在完整草稿、结构重写、终稿审校或 `audit_only` 时读取气味目录，沿用当前文体的检查时机。\n4. 个人样稿按共同质量规则的“个人样稿”读取当前文体已批准的材料；完整正式稿按 `style-vocab` 执行术语与正式词表审计。已经完成的共同质量检查传递给后续技能，不重复通用改写。\n   跨技能交接沿用当前请求范围、准确授权、材料版本及已完成检查；材料变化时重读并检查受影响部分，影响不明时扩大必要检查。接入下游工具不重置协作方式，也不把局部任务扩成整稿审查；只读限制继续有效。\n5. 实际写入本地 `.md`、`.tex` 及必要源文件前读取[文稿版本保护](references\u002Fdocument-version-protection.md)；只读审查和聊天内改句不触发。Word 转换时读取[Markdown 到 DOCX 交接契约](references\u002Fmarkdown-docx-contract.md)，由 `docx` 核对当前材料并处理交付。\n\n## 普通中文编辑\n\n已有普通中文的 `general_edit` 默认 `in_place`：以原文为底稿，先定位具体问题，再只替换必要片段；没有具体问题就原样交付，不从头另写一版。新建文档使用 `draft`，用户要求重搭结构时使用 `structural`，均按文稿协作处理。只看问题时使用 `audit_only`，不顺手改稿。\n\n按最小加载规则准备，再按共同质量规则的“中文正文展示前检查”和“修改强度”处理；普通讨论回复不进入文稿检查。\n\n## 私有样稿\n\n仅在用户要求维护样稿时更新，不在业务交付后自动追问。候选与批准内容分开，复用已明确的替换范围和选择；读取规则见最小加载规则及共同质量参考。\n\n## `audit_only` 审查输出\n\n保持只读，按共同质量规则的同名章节在对话中分点报告问题；不生成替换稿，不因先前授权过修改而越过本轮只读范围。\n\n## 相邻任务边界\n\n- 工程判断：申报指标由 `project-writing` 处理；技术方案、独立指标、实验设计和结果解释由 `technical-writing` 处理，按需共用[指标可行性判断](..\u002Ftechnical-writing\u002Freferences\u002Fmetric-feasibility.md)。仅问判断时直接回答，不自动写报告或改项目。\n- 调研与资料：报告由 `research-report` 连续完成调研和写作；仅检索、下载论文用 `paper-search`、`paper-download`，持续产品库用 `product-research-workbook`，查 Zotero 笔记和批注用 `zotero-workspace-library`，写入 Zotero 笔记目前没有技能支持，给出可粘贴的文字由用户保存。调用资料工具不自动扩大为报告任务。\n- 论文审查：技术内容、论证、结论、原文及笔记准确性核对和明确要求的模拟审稿由 `paper-review` 处理，局部疑问只检查相关内容；文字与语言审校由 `ieee-manuscript-edit` 处理。\n- 停稿审查：用户要“还要不要改”“按严重程度审”这类结论时，不分文体都用 `paper-review` 的停稿审查；要终稿审校或交付前检查时，用对应文体技能自己的审校。\n- 投稿与制作：投稿合规和事务由 `journal-submission` 处理；按实际产物使用 `docx`、`pdf`、`latex-paper`、`paper-figure-review` 或 `pptx` 的现有流程。准备投稿不自动触发全文审稿，排版不自动授权改写；同时要求内容与格式检查时复用当前稿件和已有检查，仅在范围不明且明显影响工作量时询问。\n\n需要判断完整学术流程时，按需读取 [学术流程地图](references\u002Facademic-workflow-map.md)，不要因此加载所有下游技能。\n\n## 完成条件\n\n- 写作上下文字段已经确定，`loaded_refs` 与实际读取一致。\n- 本轮范围及适用的协作、质量和交付检查已完成，满足共同质量规则的停笔条件。\n- 写入已回读核验；未完成或受阻的部分如实说明，不把待确认内容算作已保存。\n","# 通用写作流程与编辑\n\n## 目标\n\n统一管理如何协作、确认和交付；专业技能负责具体文体的结构、论证、证据和检查要求。进入专业技能后，共同流程继续有效；普通中文编辑由本技能直接完成。已有决定与准确授权继续沿用。\n\nMarkdown 正文写作或实质修改时，按 [Markdown 正文写法](references\u002Fmarkdown-writing.md)组织标题、段落和并列内容。确定研究、实验材料的主记录，或整合入口、专题记录、历史及跨文档引用时，读取 [Markdown 文档组织](references\u002Fmarkdown-document-organization.md)确定载体、职责和验收；完整保存分类集中在该参考，不在各入口复制。句子质量和具体文体要求仍按本技能及下游专业技能执行。\n\n## 工作流程\n\n1. 确定当前主稿、来源、模板、本轮修改范围和受保护片段，建立或沿用下方写作上下文。批量编辑时列清获准处理的文件，语言镜像仅在授权范围内纳入。\n2. 按[文稿协作](references\u002Fcollaborative-writing.md)选择直接处理、结构讨论、分批确认或只读审查；具体条件和正文循环由该参考统一维护。原文保留操作和界面短文案沿用下方专门分支。\n3. 实验方案按下方专门分支进入实验技能，其余按文体对应表加载专业技能；按最小加载规则准备共同质量要求与本轮所需资料，处理正文。共同流程贯穿专业写作，不因切换技能重复确认或重新改写。\n4. 按共同质量规则完成必要检查，再按已选协作方式交付、写回并回读。材料缺口只暂停依赖未决事实的内容；批量任务核对每篇已修改、无需修改或无法处理。默认只交付正文或审查意见，不附检查记录和改写理由；用户要求解释时与正文分开。\n\n## 原文保留操作\n\n用户明确要求正文逐字不动、仅在开头加标题或末尾追加给定文字时，按[原文保留编辑](references\u002Fexact-edit.md)直接拼接并校验。本地 UTF-8 文稿使用其中的工具生成并校验结果；已有 Markdown 主稿按单一主稿约定回写，工具所需新候选放过程目录，不作为第二份主稿。不重新生成或润色受保护正文；其他写作任务沿用共同流程。\n\n## 界面文案\n\n中文 GUI、网页或上位机的标题、按钮、字段名、状态和操作提示也属于润色范围，包括源代码里的用户可见字符串。创建或修改界面时进入此分支，先读 [界面文案检查](references\u002Fui-copy.md)，再实际读取 [style-vocab](..\u002Fstyle-vocab\u002FSKILL.md) 及其适用词表；当前任务已经加载且内容未变时复用。界面入口仍负责布局、运行和截图核验。\n\n这类短文案按 `document_type=general`、`mode=general_edit` 和已有修改范围处理；只审不改时为 `audit_only`。本分支替代长文稿流程，不要求确认提纲、分批正文或形成完整正式稿，不自动运行整份代码的文稿审计。复用现有授权，检查通过后继续原界面任务。\n\n## 写作上下文\n\n开始正文工作前，在任务内部确定以下字段；文稿、范围和阶段未变时沿用，变化时只更新相关项，不另建记录文件。普通交付不展示这段记录。评测提示包含 `TRACE_WRITING_CONTEXT=1` 时，才在文末输出同名 JSON 对象。\n\n| 字段 | 允许值 |\n|---|---|\n| `document_type` | `project`、`technical`、`research_report`、`meeting_notes`、`paper`、`general` |\n| `mode` | 使用下表中与文稿类型对应的值 |\n| `edit_scope` | `draft`、`structural`、`bounded`、`in_place`、`audit_only` |\n| `language` | `zh`、`en`、`mixed` |\n| `loaded_refs` | 本轮实际读取过的规则和样稿路径；不得登记“准备读取”或凭规则名称猜测 |\n\n`edit_scope` 的含义：\n\n- `draft`：从材料起草正文。\n- `structural`：允许调整章节、段落职责和信息顺序。\n- `bounded`：只改用户指定章节、段落或问题。\n- `in_place`：保留结构和作者声音，只做必要的原位修改。\n- `audit_only`：只审不改，按共同质量规则在对话中分点报告问题。\n\n## 专业写作衔接\n\n| `document_type` | `mode` | 主技能 |\n|---|---|---|\n| `project` | `proposal`、`expert_reply`、`final_audit` | [project-writing](..\u002Fproject-writing\u002FSKILL.md) |\n| `technical` | `technical_scheme`、`technical_exchange`、`system_description`、`patent_disclosure`、`test_result_analysis` | [technical-writing](..\u002Ftechnical-writing\u002FSKILL.md) |\n| `research_report` | `evidence_report`、`decision_report`、`final_audit` | [research-report](..\u002Fresearch-report\u002FSKILL.md) |\n| `meeting_notes` | `discussion`、`action`、`mixed` | [meeting-notes](..\u002Fmeeting-notes\u002FSKILL.md) |\n| `paper` | `zh_paper`、`en_paper`、`final_audit` | [ieee-manuscript-edit](..\u002Fieee-manuscript-edit\u002FSKILL.md) |\n| `general` | `general_edit` | 本技能的通用编辑流程 |\n\n判断顺序：\n\n1. 用户明确说出的文稿类型、用途和读者。\n2. 原文件的栏目、模板和内容职责。\n3. 仍无法区分且会改变产物时，只问一个最关键的问题；不影响实质结果时按最窄范围继续。\n\n会前方案讨论稿、技术交流材料或待讨论问题清单，目标是区分已有条件、会上决定和另行工作时，使用 `document_type=technical`、`mode=technical_exchange`。会议已经结束，任务是整理实际发言、结论和行动项时，使用 `meeting_notes`。\n\n制定、修改或续写可执行实验方案时，使用 `document_type=technical`、`mode=technical_scheme`，主技能直接选 [lab-notebook](..\u002Flab-notebook\u002FSKILL.md#讨论实验方案)，由其组织讨论进度、现场步骤和后续记录；本分支替代上表的通用技术写作入口。独立技术问答仍按下方工程判断分支直接回答。\n\n专利构思讨论、技术交底书起草或审校使用 `document_type=technical`、`mode=patent_disclosure`。仅讨论时沿用当前范围，不自动建稿；专利检索、权利要求及保护范围分析不因进入交底书模式而自动开展。\n\n按表应用对应文体技能的专业要求，共同协作与质量规则持续适用；普通中文直接在本技能完成，不另找写作入口。\n\n## 规则优先级\n\n按共同质量规则的“优先级”处理冲突；事实与关系保护、必要复述、审查输出和停笔条件均以该参考为准，文体技能补充专业要求。\n\n## 最小加载规则\n\n以下要求同样适用于直接调用文体技能；按其现有引用复用共同参考，不必先返回本入口。实际读取的路径记入 `loaded_refs`；同任务材料与规则未变时复用，已变化或无法确认读过时补读必要文件。\n\n1. 建立写作上下文后、处理正文前，读取[文稿协作](references\u002Fcollaborative-writing.md)，将实际路径记入 `loaded_refs`，据此选择直接处理或分批协作，不另加确认关口。\n2. 实际读取文体对应表选定的主技能及本轮所需参考；对应表不能代替专业规则。`general_edit` 不加载另一个写作入口。论文和 `final_audit` 只读当前稿件语言对应的细则。\n3. 各类正文都读取[共同质量规则](references\u002Fcommon-quality.md)。中文正文首次起草、续写、局部修改或审查前，按其中“中文正文展示前检查”读取 [AI 气味目录](references\u002Fai-smell-catalog.md)和 `style-vocab` 适用词表，逐批检查；混合稿只对中文部分执行。英文在完整草稿、结构重写、终稿审校或 `audit_only` 时读取气味目录，沿用当前文体的检查时机。\n4. 个人样稿按共同质量规则的“个人样稿”读取当前文体已批准的材料；完整正式稿按 `style-vocab` 执行术语与正式词表审计。已经完成的共同质量检查传递给后续技能，不重复通用改写。\n   跨技能交接沿用当前请求范围、准确授权、材料版本及已完成检查；材料变化时重读并检查受影响部分，影响不明时扩大必要检查。接入下游工具不重置协作方式，也不把局部任务扩成整稿审查；只读限制继续有效。\n5. 实际写入本地 `.md`、`.tex` 及必要源文件前读取[文稿版本保护](references\u002Fdocument-version-protection.md)；只读审查和聊天内改句不触发。Word 转换时读取[Markdown 到 DOCX 交接契约](references\u002Fmarkdown-docx-contract.md)，由 `docx` 核对当前材料并处理交付。\n\n## 普通中文编辑\n\n已有普通中文的 `general_edit` 默认 `in_place`：以原文为底稿，先定位具体问题，再只替换必要片段；没有具体问题就原样交付，不从头另写一版。新建文档使用 `draft`，用户要求重搭结构时使用 `structural`，均按文稿协作处理。只看问题时使用 `audit_only`，不顺手改稿。\n\n按最小加载规则准备，再按共同质量规则的“中文正文展示前检查”和“修改强度”处理；普通讨论回复不进入文稿检查。\n\n## 私有样稿\n\n仅在用户要求维护样稿时更新，不在业务交付后自动追问。候选与批准内容分开，复用已明确的替换范围和选择；读取规则见最小加载规则及共同质量参考。\n\n## `audit_only` 审查输出\n\n保持只读，按共同质量规则的同名章节在对话中分点报告问题；不生成替换稿，不因先前授权过修改而越过本轮只读范围。\n\n## 相邻任务边界\n\n- 工程判断：申报指标由 `project-writing` 处理；技术方案、独立指标、实验设计和结果解释由 `technical-writing` 处理，按需共用[指标可行性判断](..\u002Ftechnical-writing\u002Freferences\u002Fmetric-feasibility.md)。仅问判断时直接回答，不自动写报告或改项目。\n- 调研与资料：报告由 `research-report` 连续完成调研和写作；仅检索、下载论文用 `paper-search`、`paper-download`，持续产品库用 `product-research-workbook`，查 Zotero 笔记和批注用 `zotero-workspace-library`，写入 Zotero 笔记目前没有技能支持，给出可粘贴的文字由用户保存。调用资料工具不自动扩大为报告任务。\n- 论文审查：技术内容、论证、结论、原文及笔记准确性核对和明确要求的模拟审稿由 `paper-review` 处理，局部疑问只检查相关内容；文字与语言审校由 `ieee-manuscript-edit` 处理。\n- 停稿审查：用户要“还要不要改”“按严重程度审”这类结论时，不分文体都用 `paper-review` 的停稿审查；要终稿审校或交付前检查时，用对应文体技能自己的审校。\n- 投稿与制作：投稿合规和事务由 `journal-submission` 处理；按实际产物使用 `docx`、`pdf`、`latex-paper`、`paper-figure-review` 或 `pptx` 的现有流程。准备投稿不自动触发全文审稿，排版不自动授权改写；同时要求内容与格式检查时复用当前稿件和已有检查，仅在范围不明且明显影响工作量时询问。\n\n需要判断完整学术流程时，按需读取 [学术流程地图](references\u002Facademic-workflow-map.md)，不要因此加载所有下游技能。\n\n## 完成条件\n\n- 写作上下文字段已经确定，`loaded_refs` 与实际读取一致。\n- 本轮范围及适用的协作、质量和交付检查已完成，满足共同质量规则的停笔条件。\n- 写入已回读核验；未完成或受阻的部分如实说明，不把待确认内容算作已保存。\n",{"name":5,"description":7},"main","62ffea78624f3af0f5b8b0664e264bf62a8ec0ec","https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills","https:\u002F\u002Fgithub.com\u002FSanAntonio021","2026-11-14 03:01:39",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add SanAntonio021\u002Fagents-skills --skill writing-router",{"tool":60,"command":61},"bunx","bunx skills add SanAntonio021\u002Fagents-skills --skill writing-router",{"tool":63,"command":64},"pnpm","pnpm dlx skills add SanAntonio021\u002Fagents-skills --skill writing-router","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002FSKILL.md",true,[68,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142,148,152,156,160,164,168,172,176,180,184],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fchat-style-v2.json","REFERENCE","参考文档",1770,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Fevals\u002Fchat-style-v2.json",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fcollaborative-writing.json",6831,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Fevals\u002Fcollaborative-writing.json",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fevals.json",16366,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Fevals\u002Fevals.json",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fparagraph-quality.json",23135,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Fevals\u002Fparagraph-quality.json",{"path":87,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002FREADME.md",9198,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Fevals\u002FREADME.md",{"path":91,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Fwriting-quality-v2.json",27769,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Fevals\u002Fwriting-quality-v2.json",{"path":95,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":16},"LICENSE","许可证",1063,{"path":99,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Facademic-workflow-map.md",11133,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Freferences\u002Facademic-workflow-map.md",{"path":103,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fai-smell-catalog.md",7071,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Freferences\u002Fai-smell-catalog.md",{"path":107,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fcollaborative-writing.md",10543,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Freferences\u002Fcollaborative-writing.md",{"path":111,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fcommon-quality.md",14451,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Freferences\u002Fcommon-quality.md",{"path":115,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fdocument-version-protection.md",2125,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Freferences\u002Fdocument-version-protection.md",{"path":119,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fexact-edit.md",2930,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Freferences\u002Fexact-edit.md",{"path":123,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fmarkdown-document-organization.md",5781,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Freferences\u002Fmarkdown-document-organization.md",{"path":127,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fmarkdown-docx-contract.md",5434,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Freferences\u002Fmarkdown-docx-contract.md",{"path":131,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fmarkdown-writing.md",1286,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Freferences\u002Fmarkdown-writing.md",{"path":135,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Fui-copy.md",2596,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Freferences\u002Fui-copy.md",{"path":139,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fupstream-sources.md",2951,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Freferences\u002Fupstream-sources.md",{"path":143,"resourceType":144,"resourceTypeDesc":145,"sizeBytes":146,"sourceHtmlUrl":147},"scripts\u002Fexact_edit.py","SCRIPT","脚本",8435,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Fscripts\u002Fexact_edit.py",{"path":149,"resourceType":144,"resourceTypeDesc":145,"sizeBytes":150,"sourceHtmlUrl":151},"tests\u002Fcollect_collaboration_evidence.py",3138,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Ftests\u002Fcollect_collaboration_evidence.py",{"path":153,"resourceType":144,"resourceTypeDesc":145,"sizeBytes":154,"sourceHtmlUrl":155},"tests\u002Ffake_document_store.py",2515,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Ftests\u002Ffake_document_store.py",{"path":157,"resourceType":144,"resourceTypeDesc":145,"sizeBytes":158,"sourceHtmlUrl":159},"tests\u002Fgrade_version_protection_eval.py",3578,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Ftests\u002Fgrade_version_protection_eval.py",{"path":161,"resourceType":144,"resourceTypeDesc":145,"sizeBytes":162,"sourceHtmlUrl":163},"tests\u002Ftest_collaborative_writing.py",8119,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Ftests\u002Ftest_collaborative_writing.py",{"path":165,"resourceType":144,"resourceTypeDesc":145,"sizeBytes":166,"sourceHtmlUrl":167},"tests\u002Ftest_document_version_git_flow.py",5450,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Ftests\u002Ftest_document_version_git_flow.py",{"path":169,"resourceType":144,"resourceTypeDesc":145,"sizeBytes":170,"sourceHtmlUrl":171},"tests\u002Ftest_document_version_protection.py",2647,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Ftests\u002Ftest_document_version_protection.py",{"path":173,"resourceType":144,"resourceTypeDesc":145,"sizeBytes":174,"sourceHtmlUrl":175},"tests\u002Ftest_exact_edit.py",18057,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Ftests\u002Ftest_exact_edit.py",{"path":177,"resourceType":144,"resourceTypeDesc":145,"sizeBytes":178,"sourceHtmlUrl":179},"tests\u002Ftest_markdown_docx_contract.py",1524,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Ftests\u002Ftest_markdown_docx_contract.py",{"path":181,"resourceType":144,"resourceTypeDesc":145,"sizeBytes":182,"sourceHtmlUrl":183},"tests\u002Ftest_paragraph_quality.py",20116,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Ftests\u002Ftest_paragraph_quality.py",{"path":185,"resourceType":144,"resourceTypeDesc":145,"sizeBytes":186,"sourceHtmlUrl":187},"tests\u002Ftest_writing_quality_v2.py",6913,"https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fwriting-router\u002Ftests\u002Ftest_writing_quality_v2.py",[189,207,232,243,270,290],{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":44},"01M71F7F7J66P4K9SKXR9JD6KD","web-access","统一处理联网任务的工具选择，包括搜索、网页读取、下载和浏览器操作。 普通检索直接使用可用搜索或读取工具；抓取受阻、正文不完整时主动转到浏览器继续。 已知依赖登录态、动态内容或页面交互时直接使用浏览器，无需用户再次点名。","https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fweb-access\u002FSKILL.md",[],[196,197,198,199,200,201,202,203,204,205,206],"access","web","web access","https","下载","交互","Existing","github","工具","搜索","edge",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":211,"sourceHtmlUrl":212,"categories":213,"keywords":217,"publishedAt":44},"01M71F7C4AP46V8XEM7XX0HFYW","visiomaster","在 Windows 上将已确认的文字讨论或参考图片绘制为可编辑 Visio 流程图、系统架构图和端口连接图，并打开已有 .vsdx 按页面和 Shape ID 局部修改原生模块、文字、分组及连线，保留其他对象。用户要求画 Visio、生成 .vsdx、修改旧 Visio 图或多轮修订时使用。场景起图以 .scene.json 迭代，旧图以当前 .vsdx 迭代；不要求 Visio 的系统框图和科研配图交 research-schematic-imagegen，飞书文档或画板里的图交 lark-whiteboard，论文投稿图审查交 paper-figure-review。","https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fvisiomaster\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fvisiomaster\u002FSKILL.md",[214],{"categoryNo":215,"categoryName":216,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000021","资料检索与研究",[209,218,219,220,221,222,223,224,225,226,227,228,229,230,231],"id","json","imagegen","schematic","review","windows","image","生成","架构图","流程图","文字","shape","paper","research",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":236,"licenseFileUrl":237,"sourceHtmlUrl":238,"categories":239,"keywords":240,"publishedAt":44},"01M71F6VZN093VVJD7NCT809J9","skill-creator","创建、修改和改进技能，检查技能结构、触发说明及执行效果。根据实际影响选择文字检查、独立行为试跑或新旧对照，也提供按需使用的盲评、查看器、Claude 触发优化和打包工具。用户要求新建技能、调整流程、修复技能行为或比较技能效果时使用；普通业务任务不因此进入技能维护。","Apache-2.0","https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fskill-creator\u002FSKILL.md",[],[241,242,228,204],"skill creator","creator",{"skillNo":244,"name":245,"nameZh":6,"description":246,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":247,"sourceHtmlUrl":248,"categories":249,"keywords":257,"publishedAt":44},"01M71F5XZPZ7Y7YYNFSAEFSQXF","paper-search","为科研问题检索、扩展并核实论文证据，也负责正式参考文献生成、DOI\u002F元数据一致性核验和已有引用纠错。Use when 用户要找论文、查文献、补参考文献、找代表作\u002F最新进展\u002F相反证据，或说“继续找”“再深入”；正式引用任务核实相关条目的出版字段，复用可定位且未变化的核验结果，有具体疑点只核相关条目。仅 BibTeX 语法、样式、引用键对应和编译问题转 latex-paper，不因 IEEE\u002FBibTeX 关键词全查。普通检索快速返回可核实且去重的结果，联网用 web-access。已知论文下载转 paper-download，原文技术核对和审稿转 paper-review，整篇稿件引用覆盖检查转对应论文编辑或审查技能。普通参数或多渠道比较表转 xlsx，明确持续产品库或库契约审计转 product-research-workbook，远程写回转对应文档技能。","https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fpaper-search\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fpaper-search\u002FSKILL.md",[250,253,254],{"categoryNo":251,"categoryName":252,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":215,"categoryName":216,"taxonomyType":22,"taxonomyTypeDesc":23},{"categoryNo":255,"categoryName":256,"taxonomyType":30,"taxonomyTypeDesc":31},"01JBSEEDCAT000000000000031","产品经理",[230,258,259,260,261,262,197,231,222,263,43,196,41,264,265,225,266,267,268,269],"paper search","search","数据","doi","product","关键词","product-research","adaptation","local","xlsx","evidence","ieee",{"skillNo":271,"name":272,"nameZh":6,"description":273,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":274,"sourceHtmlUrl":275,"categories":276,"keywords":281,"publishedAt":44},"01M71F5M874YA5YD9893SHFC6Y","paper-download","获取、复用或导入论文 PDF 到 Zotero，先查已有条目、附件和任务本地资料，只补请求的缺项；归档保留已有阅读内容与外部新增附件，超时先核实原操作。Use when 用户给出题名、DOI、论文 URL、作者主页、论文列表、本地 PDF 或 paper-search 结果，要求下载、保存到 Zotero、整理已有论文或继续机构授权下载。研究问题检索与引用元数据核验用 paper-search；原文技术核对用 paper-review。联网由 web-access 路由；Windows 版机构模块通过 web-access HTTP Broker 复用当前 Edge 会话，负责出版物核验，不自行执行浏览器登录或验证码。","https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fpaper-download\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fpaper-download\u002FSKILL.md",[277,280],{"categoryNo":278,"categoryName":279,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":215,"categoryName":216,"taxonomyType":22,"taxonomyTypeDesc":23},[230,282,283,223,284,285,222,200,286,43,196,41,287,206,260,259,288,197,289,261],"download","paper download","broker","http","URL","整理","Zotero","PDF",{"skillNo":291,"name":292,"nameZh":6,"description":293,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":294,"sourceHtmlUrl":295,"categories":296,"keywords":299,"publishedAt":44},"01M71F4F14TKK63R4DR4KB2C97","humanizer","Remove signs of AI-generated writing from general English prose. Use when\nediting or reviewing general English text to make it sound more natural and\nhuman-written. Do not use for Chinese text, IEEE\u002FSCI manuscript delivery, or\nengineering proposal delivery; route those to writing-router,\nieee-manuscript-edit, or project-writing. Based on Wikipedia's comprehensive\n\"Signs of AI writing\" guide. Detects and fixes patterns including:\ninflated symbolism, promotional language, superficial -ing analyses, vague\nattributions, em dash overuse, rule of three, AI vocabulary words, passive\nvoice, negative parallelisms, and filler phrases.","https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fhumanizer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSanAntonio021\u002Fagents-skills\u002Fblob\u002Fmain\u002Fhumanizer\u002FSKILL.md",[297,298],{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},{"categoryNo":28,"categoryName":29,"taxonomyType":30,"taxonomyTypeDesc":31},[292,300,301,302,303,304,305,306,307,308,33,309,310,43,35,311,312,313,314,315],"english","patterns","edit","delivery","wikipedia","human","em dash","route","text","vague","dash","generated","remove","project","chinese","proposal"]