Menu
Use when the user needs help choosing or organizing an academic-writing workflow by deliverable, stage, or format, including review articles, guided reading, paper sections, PPT or slides, posters, and technical reports.
Use when the user wants to install, configure, diagnose, or troubleshoot ScholarAIO, including setup check, dependency status, API keys, and bilingual setup flow.
Use when the user explicitly asks for Nature Skills, nature-skills, Nature style, Nature-style, Nature Communications, Nature-family, CNS, high-impact journal, or Springer Nature workflows, including Nature figure work, polishing, writing, reviewer critique, high-impact journal major revision response, Nature/CNS citations, Nature data-sharing workflows, paper readers, reviewer response, paper-to-PPT, submission checklist, or Nature-specific academic-search workflows.
Use when the user wants to rebuild or refresh ScholarAIO keyword, full-text, FTS5, FAISS, or semantic search indexes after data or metadata changes.
Use when the user wants to find academic papers, search the local library, run keyword or semantic search, search by author, explore topics, or federate across library, explore databases, and arXiv.
Use when the user wants to import papers from Endnote XML/RIS, Zotero Web API or local SQLite, attach PDFs, match PDFs to records, or supplement records with PDF content.
Use when the user wants to process new papers, patents, theses, documents, or proceedings from inbox queues into the knowledge base, run the ingest pipeline, or rebuild indexes.
| name | academic-writing |
| description | Use when the user needs help choosing or organizing an academic-writing workflow by deliverable, stage, or format, including review articles, guided reading, paper sections, PPT or slides, posters, and technical reports. |
Route academic-writing requests to the right specialized skill with minimal overlap.
This skill is the entry point for users who know what they want to produce, but do not know which writing workflow to use.
Do not duplicate the full instructions of the downstream skills. Your job is to:
| User wants | Route |
|---|---|
| 文献综述 / survey / review article | /literature-review |
| 单篇论文引导式精读 / guided deep reading of one paper | /paper-guided-reading |
| 论文具体章节（Introduction / Method / Results / Discussion / Conclusion） | /paper-writing |
| 审稿回复 / rebuttal / response letter | /review-response |
| 研究空白分析 / 选题调研 | /research-gap |
| 语言润色 / 去 AI 味 / 风格迁移 | /writing-polish |
| 引用真实性检查 | /citation-check |
| 正式 Word 报告 | 写作 skill + /document |
| 汇报 PPT / 答辩幻灯片 | 写作 skill + /document |
| 海报内容包 | /poster |
| 专题/技术调研报告 | /technical-report |
| Stage | Route |
|---|---|
| 还没确定应该用哪个 skill | 留在本 skill，先做任务分流 |
| 需要先锁定并深读一篇论文 | /paper-guided-reading |
| 已有论文集合，需要组织叙述 | /literature-review |
| 已有研究内容，需要写论文段落 | /paper-writing |
| 已收到审稿意见 | /review-response |
| 还在找空白和方向 | /research-gap |
| 只需要修语言 | /writing-polish |
| 快交稿了，要核验引用 | /citation-check |
| 需要交付 DOCX / PPTX | /document |
PPTX，通过 /document 生成和检查。beamer，先按“演示文稿内容工作流”组织结构、标题、每页要点、图表需求。PPTX，不要假设仓库已经有 beamer 专用后端。/poster，由它负责 poster 专属的版块和文本密度控制。/poster 会继续组合 /literature-review、/paper-writing、/research-gap、/draw、/document。/technical-report，由它负责 audience、结构和建议层组织。/technical-report 会继续组合 /literature-review、/research-gap、/paper-writing、/document。DOCX/PPTX/XLSX；对 beamer/poster 用“工作流支持”表述，不要伪装成已有独立后端。用户说："我想做一个给导师汇报的 PPT，但还没想好结构"
→ 先用本 skill 路由到 “汇报 PPT” 工作流，再转 /document，必要时补 /research-gap 或 /literature-review
用户说："帮我写一个技术调研报告"
→ 先判断是偏综述还是偏研究空白分析，然后转 /literature-review 或 /research-gap，最后如需正式文件再接 /document
用户说："我想先找一篇最相关的论文，然后带着我精读"
→ 先路由到 /paper-guided-reading
用户说："我想写 beamer"
→ 先确认是否真的需要 LaTeX beamer；若不是硬要求，默认走演示内容 + PPTX 工作流