paperpush: Skill for Claude Code

paperpush prepare & submit (Claude skill)

Orchestrates the full submission path for a manuscript directory when the user has not named a .sub file. It generates the .sub, hands off to the paperpush-autofill skill to fill it, validates, and then (with the user's go-ahead) logs in and submits. This skill only sequences the steps; each underlying paperpush command does the real work.

Inputs you need

1. The manuscript directory — required. If the user did not give it, ask in plain text (a path is free-text; do not use a multiple-choice prompt). Never guess it, scan the repository for candidate folders, or fall back to test fixtures.
2. The venue slug (e.g. bioinformatics). If the user did not say it, ask or infer it from their message. Confirm it is supported with paperpush --venues.

Do not ask for a .sub path. Resolve it by this hierarchy: (1) an explicit .sub the user provided; (2) else an existing <venue>.sub in the manuscript directory; (3) else create <venue>.sub in the manuscript directory on the fly. See step 1.

Steps

1. Check the login first, before any other work. Run:

   paperpush login --list
   

   If the venue is not listed (or the output is Not logged in to any venues.), tell the user immediately — in your next message, not at the end — to run

   paperpush login <venue>
   

   themselves in a terminal, since it opens a browser and may need their password, ORCID, CAPTCHA, or two-factor code. Then carry on with steps 1-3 anyway while they do it; a missing login only blocks step 5.

2. Resolve the .sub by hierarchy (user-provided > in manuscript dir > create on the fly):

   • If the user named a .sub path, use it as-is.

   • Else if <manuscript-dir>/<venue>.sub already exists, reuse it (do not overwrite unless the user asks to regenerate).

   • Else create it in the manuscript directory, with an absolute path:

     paperpush subfile <venue> --fill-defaults -o <manuscript-dir>/<venue>.sub