vincenzoimp/academic-research-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.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/vincenzoimp/academic-research-skills --skill manage-submission

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

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 contract
  • papers/<slug>/correspondence/ — current review state
  • references/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

Relacionados por tarea

del mismo repositorio

Más Skills

Todos los Skills