SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsscholarly-publishing

scholarly-publishing

Office & productivity

View repository

Updated 10-16 05:47

About this skill

Scholarly Publishing (Full Manuscript Submission Workflow)

What You Get (Output Contract)

When the user says "I want to submit/revise/camera-ready/need LaTeX engineering/write a rebuttal/write a cover letter", this skill is responsible for breaking the goal down intoa deliverable publication asset package：

  • manuscript/: manuscript source files (LaTeX / Word / Markdown, any one as source-of-truth）
  • figures/: source code/source data/final export requirements for each figure (PDF/EPS/SVG/TIFF)
  • supplement/: supplementary materials (method details, appendix, extended experiments, additional figures and tables)
  • submission/: files required for submission (cover letter, graphical abstract, highlights, checklist, packaged zip)
  • revision/: revision assets (rebuttal, diff, point-by-point response matrix)
  • build/: reproducible build artifacts (PDF, packaged zip, CI logs)

The goal is not to "write a passage/draw a figure", but to producesubmittable, revisable, reusable, auditableset of files and specifications.

When to Use (Trigger Scenarios)

Applicable scenarios (mixed Chinese and English both acceptable):

  • Submission/revision:投稿、submission、返修、revision、rebuttal、回复审稿意见、camera-ready、proof
  • LaTeX engineering:latex template、latexmk、bibtex、biber、Overleaf、chktex、latexindent
  • Reproducible publication package:manuscript as code、reproducible manuscript、submission zip、paper pdf build

Not applicable:

  • Purely document processing such as "extracting text from PDF/merging PDFs/replying to comments".
  • Purely "drawing flowcharts/conceptual diagrams/data result figures/group meeting slides", and not involving a submission asset package or publication delivery.

Input Information (Minimal Inquiry)

To land reliably, at least the following are needed:

  1. Target venue: journal/conference/publisher (if unknown, you can first use a "category": Nature/IEEE/ACM/NeurIPS/PLOS)
  2. Manuscript type: research paper/methods paper/review/short paper/technical report
  3. Deliverables: submission package, revision package, camera-ready package, reproducible build package, dissemination assets such as project homepage/video abstract/poster (multiple selections allowed)
  4. Writing source: Is there already a draft/data/figures? (If yes, focus on "revising the manuscript/completing the specifications")

Workflow (Executable Process)

Phase 0 — Choose the "Single Source of Truth"

Choose one of the following three as the source file (strongly recommended to choose only one):

  • LaTeX: suitable for journals/conferences, many equations, strict typesetting required, CI-buildable
  • Word: suitable for some medical and life science journals/teams whose collaborators prefer Word
  • Markdown/Quarto: suitable for technical reports/internal reports/publishable web pages (can export PDF)

Meta-rule: Do not edit the same manuscript in parallel in multiple formats. Other formats can only be "exports".

Phase 1 — Establish "Submission Constraints" Before Writing the Main Text

  1. Target venue and template: record layout, anonymization, page limits, figures and tables, citations, and supplementary material constraints
  2. Submission checklist: list required files by the four stages of pre-submission, submission, revision, and camera-ready
  3. Clarify figure specifications: list each figure's purpose, type (line art / raster / combination), and export format (PDF/TIFF)

Phase 2 — Manuscript Main Line (Writing)

Execute two-stage writing:

  • First write the "structural outline (bullets allowed)"
  • Then write the "final main text (must be paragraphs, bullets prohibited)"

Meta-rule (common to top journals):

  • Figures before text: The main storyline of Results is driven by Figures
  • Sentences are not overloaded: One claim per sentence; one topic sentence per paragraph; one question per section
  • Make it easy for reviewers: Methods reproducible, statistics traceable, figure captions self-explanatory

Phase 3 — Figure and Table Delivery Constraints

This skill only defines the figure and table delivery constraints required for submission; it does not require invoking other plotting experts within the main text:

  • For data figures: unify fonts, font sizes, line widths, color schemes, subplot spacing, panel labels (A/B/C)
  • Export: prefer PDF/EPS/SVG(vector), and when necessary TIFF 600dpi(raster)
  • Accessibility: colorblind-friendly (Okabe-Ito / colorcet / cmcrameri)

Phase 4 — LaTeX/Build/Packaging

If the source-of-truth is LaTeX:

  • Specify the local compilation command, lint/format requirements, CI compilation requirements, and the submission zip file list

If the source-of-truth is Word:

  • Still follow the "figure and table output standards + citation consistency + file naming conventions", and prepare the attachments required by the submission system

Phase 5 — Submission and Revision

  • Before submission: list the main manuscript, figures and tables, supplementary materials, ethics/data/conflict-of-interest statements, and cover letter
  • Revision: maintain a point-by-point response matrix, modification locations, sources of evidence, and reasons for non-adoption
  • Camera-ready: check the final layout, author information, copyright/license, source files, and final PDF

Phase 6 — Dissemination Assets (Optional)

If a project homepage, video abstract, or poster is needed, first define the input sources, target audience, output directory, and conference/institution restrictions. This skill is not responsible for generating slides, nor does it require invoking dissemination experts within the main text.

Meta Rules

A. Asset Naming Conventions

  • Figure files:fig-01-overview.pdf、fig-02-results.tiff
  • Subfigures:fig-02A-...、fig-02B-...
  • Uniformly use kebab-case; avoid spaces and Chinese characters; avoid "final_v7_reallyfinal"

B. Reproducibility Minimum

Provide at least:

  • Build command (make pdf / latexmk / quarto render）
  • Environment description (Python version, dependencies, or lockfile)
  • Figure and table sources (code/parameters) and export scripts (automation preferred)

C. Quality Gates (Self-check Before Submission)

  • Consistent fonts, readable font sizes, uniform line widths
  • Statistical figures include uncertainty (CI/SEM/SD) and explain it in the caption
  • Figure captions are self-contained: reading the caption allows understanding what the figure expresses, the sample size, and the statistical test
  • Accurate citations: every key claim can be traced back to data or a citation

Case Library (High-signal GitHub Repositories)

See:references/case-library.md(categorized by "writing checklist/paper engineering/publication package/revision assets")

Quick Invocation Examples (for VCO Routing)

  • "I want to submit a Nature-style paper: please provide the submission asset package directory structure + checklist + figure and table export standards"
  • "Top-journal figures: matplotlib multiple subplots + colorblind-friendly + export PDF + TIFF 600dpi (write out the specifications for each figure clearly)"
  • "I want to reply to reviewer comments: please generate a rebuttal matrix and provide writing conventions for point-by-point responses"
  • "Please connect the current LaTeX project to GitHub Actions for automatic compilation and generate a submission zip"