YCC-Lover/research-starter-skills / skills/rsk-paper-writing
rsk-paper-writing
Verified组织论文论证、起草或修改章节、核对学位论文一致性,也可单独自然润色并匹配作者语气。用于学术文字与实质写作;只润色时不启动整套研究流程。
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.5 KB |
| agents/openai.yaml | config | 316 B |
| assets/chapter-map.tsv | other | 107 B |
| assets/terminology.tsv | other | 140 B |
| references/abstract-introduction.md | markdown | 2.9 KB |
| references/advanced-writing.md | markdown | 1.7 KB |
| references/discussion-submission.md | markdown | 1.8 KB |
| references/examples.md | markdown | 1.5 KB |
| references/prose-editing.md | markdown | 9.8 KB |
| references/related-methods.md | markdown | 2.2 KB |
| references/results-discussion.md | markdown | 1.9 KB |
| references/source-manifest.json | config | 7.3 KB |
| references/sources.md | markdown | 3.5 KB |
| references/structure.md | markdown | 1.7 KB |
| references/thesis-longform.md | markdown | 2.6 KB |
| references/third-party-notices.md | markdown | 2.0 KB |
| scripts/check_prose_edit.py | script | 4.7 KB |
references/structure.md
View on GitHub# 论文整体结构
依据教程 08《如何写论文?》。这是论证框架,不是所有学科的固定目录。
## 写作前
先讨论作者贡献、署名及目标发表渠道。原文描述了贡献排序、主要写作者作为第一作者、负责人作为通讯作者的实验室惯例;实际必须按真实贡献、团队约定和机构或期刊规则处理,不由模型擅自确定。
确定读者已知什么、具体缺口是什么、目前有哪些证据。未验证的构思可写研究计划,不包装成完成的论文结果。
## 论证骨架
围绕以下问题组织文章:为什么问题重要;已有方案怎样解决;在什么条件下仍不足;我们做了什么;为什么预期更合适;公平比较得到什么;何时强或弱;下一步还有什么。
常见功能包括题名、摘要、引言、相关工作、贡献主体、理论或实验支持、讨论、结论和参考文献。贡献主体可能是方法,也可能是观察、基准或分析,不能强迫所有论文写成“新模型”。
题名反映对象或贡献,不靠堆砌形容词。结论回答开头的问题,限定证据范围,不临时增加新结论。讨论可解释替代原因、限制与未来工作;未来计划不能表述成已完成贡献。
## 跨章节一致性
建立轻量主张表:主张 | 来源或结果定位 | 支持范围 | 对应章节 | 尚缺验证。写作顺序可以围绕已稳定的证据安排,不必从第一段顺序写到最后。
检查摘要数字与实验表一致,贡献项在主体有对应内容,符号与图中名称一致,相关工作公平定位差异。抽象的优越性必须落到问题、条件和可比较的证据。
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |