Manage submission
Skill VincenzoImp/academic-research-skills/skills/manage-submission
Use when submitting a paper, recording decisions and reviews, drafting rebuttals and response letters, applying revisions, or preparing the camera-ready version.From its SKILL.md
npx -y skills add VincenzoImp/academic-research-skills --skill manage-submissionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.0 KB, 434 tokens by cl100k_base, as published. Nobody here has run it
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 checkpasses
What ships with it: 1 file
757 B alongside SKILL.md
references/
- concern-map.md757 B