论文写作
- 作者仓库星标 3,238
- 作者更新于 实时读取
- 作者仓库 Research-Paper-Writing-Skills
- 领域
- 写作
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @Master-cai · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: research-paper-writing
description: Improve academic paper writing quality for ML/CV/NLP-style papers with clear section structure…
category: 写作
runtime: 无特殊运行时
---
# research-paper-writing 输出预览
## PART A: 任务判断
- 适用问题:文章、文案、发言稿、润色或结构化表达。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Overview / Core Workflow / Global Principles”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于文章、文案、发言稿、润色或结构化表达,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Overview / Core Workflow / Global Principles”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、执行终端命令、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件、执行终端命令;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件、执行终端命令。
先用一个小任务确认它会围绕“Overview / Core Workflow / Global Principles”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: research-paper-writing
description: Improve academic paper writing quality for ML/CV/NLP-style papers with clear section structure…
category: 写作
source: Master-cai/Research-Paper-Writing-Skills
---
# research-paper-writing
## 什么时候使用
- research-paper-writing 是写作方向的技能,帮你打磨文章、稿子、内容表达 适合处理文章、文案、润色、翻译、总结和结构化表达,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆…
- 面向文章、文案、发言稿、润色或结构化表达,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Overview / Core Workflow / Global Principles」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件、执行终端命令;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "research-paper-writing" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Overview / Core Workflow / Global Principles
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件、执行终端命令 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Research Paper Writing
Overview
Use this skill to rewrite a research paper into a reviewer-friendly, high-clarity draft. Prioritize first-impression quality (figures/tables/layout), logical flow, and evidence-backed claims.
Core Workflow
- Clarify the paper story before sentence-level edits.
- Use section-specific guidance in
references/. - Rewrite paragraph-by-paragraph with one message per paragraph.
- Run reverse outlining after writing each section.
- Check every major claim in Abstract/Introduction against experimental evidence.
- Run final-paper adversarial review with
references/paper-review.md.
Global Principles
- Keep one paragraph for one message only.
- State the paragraph message in the first sentence.
- Make nouns self-contained; define new terms before reusing them.
- Maintain sentence-to-sentence flow (cause, contrast, consequence, or refinement).
- Iterate with adversarial self-review: read as a skeptical reviewer.
- Treat visual quality as core content, not decoration.
- Use a clean teaser and pipeline figure.
- Use readable, minimal-ink tables.
- Keep formatting consistent and tidy.
Paragraph Clarity Check (Important)
Use this quick test whenever the user asks whether a paragraph "flows" or is clear.
- Read as an external reader:
- Does this paragraph have one explicit message?
- Does the first sentence state what this paragraph will do?
- Are all key nouns/terms readable without hidden context?
- Does each sentence connect to the previous one with a clear relation (cause, contrast, consequence, refinement, example)?
- Run reverse outlining for the current section:
- Write down thesis/main claim.
- Write down each paragraph topic sentence.
- Write down the evidence/explanation points under each paragraph.
- Check mapping: topic sentence -> thesis, and evidence -> topic sentence.
- Revise or remove any paragraph that cannot be mapped cleanly.
- If flow is still weak, add temporary section headers and explicit transition phrases during revision, then remove unnecessary headers before finalizing.
Source reference for this check:
references/does-my-writing-flow-source.md
Section Guides
Load only the needed section file:
- Introduction:
references/introduction.md - Abstract:
references/abstract.md - Related Work:
references/related-work.md - Method:
references/method.md - Experiments:
references/experiments.md - Conclusion:
references/conclusion.md - Paper review (Paper Rview):
references/paper-review.md - Paragraph clarity source:
references/does-my-writing-flow-source.md - Example bank index:
references/examples/index.md
Paper Review Core Points
Use references/paper-review.md for the full checklist and workflow.
- Add an end-of-draft self-review question list in five dimensions:
- contribution,
- writing clarity,
- experimental strength,
- evaluation completeness,
- method design soundness.
- Treat claim-evidence alignment as a hard constraint, especially for Abstract and Introduction.
- Perform adversarial writing: review as a skeptical reviewer and resolve every high-risk question.
- Revise until major rejection risks are explicitly addressed.
Execution Rules
- Build a mini-outline before drafting prose.
- For each subsection, explicitly include motivation, design, and technical advantage when applicable.
- Avoid writing style that looks like incremental patching of a naive baseline.
- Keep terminology stable across the full paper.
- If a claim cannot be supported by results, weaken or remove the claim.
- Before finalizing, append and answer a five-dimension self-review question list, then revise the paper based on unresolved items.
- Do not load all section references (Introduction/Abstract/Related Work/Method/Experiments/Conclusion) at once; load only the specific section guide needed for the current edit target.
Output Contract
When asked to rewrite or draft sections, return:
- A compact section outline (3-7 bullets).
- Revised paragraphs with explicit paragraph roles (opening/challenge/method/advantage/evidence/limitation).
- A short self-review checklist covering clarity, flow, terminology consistency, unsupported claims, and missing evidence.
- A claim-evidence map for each major claim in the revised text using
Claim: ... | Evidence: ... | Status: supported/needs evidence.
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核