使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/vincenzoimp/academic-research-skills --skill manage-submission开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Manage Submission
Operate the lifecycle of papers/<slug>/ around its venue events. The current version always lives in manuscript/; every submitted version is frozen forever in archive/.
Read First
papers/README.md— the lifecycle contractpapers/<slug>/correspondence/— current review statereferences/concern-map.md
Events
Submit. Verify make paper P=<slug> and make check pass and the artifacts bundle is current. Freeze: copy manuscript/ (with its PDF) and artifacts/ into archive/r<N>/ exactly as submitted. Archives are immutable from that moment.
Decision received. Save the decision letter and the reviews verbatim in correspondence/. Summarize the outcome for the user.
Rebuttal. Build the concern map per references/concern-map.md. Draft the response in correspondence/: per concern — direct answer, evidence, and the exact manuscript change it commits to. Get user approval before anything is sent.
Revision. Apply the promised changes to manuscript/, tracking which concern each change answers (concern ids in a change log in correspondence/). New scientific work requested by reviewers goes through develop-contribution first, never directly into prose. Rebuild, re-check, then Submit again as the next round.
Camera-ready. Apply final venue requirements (de-anonymization, format, DOI links), then freeze archive/camera-ready/.
Rules
- Never edit anything inside
archive/. - A response letter only promises changes that can actually land in the
revision before the deadline.
- Reviews are private input: they stay inside
correspondence/and are
never quoted in public artifacts.
Done When
- The event is fully recorded — archive frozen and/or correspondence
updated — the manuscript state is consistent, and make check passes
