submit-paperlisted
Install: claude install-skill zernie/paperlint
<!-- vigiles:sha256:4a42424fd18098e5 compiled from skills/submit-paper/SKILL.md.spec.ts -->
# submit-paper — get a reviewed paper from "done" to "ready for review"
## Run me
🔴 FIRST, before any other step:
```
node .claude/skills/paper-pipeline/scripts/announce.mjs submit-paper <paper-dir>
```
An advisory pass cannot be observed failing — silence is both its error state and its normal
state — so starting is an event, and events get written down.
Assumes the paper is already hardened (run `pc-panel-review` — incl. its venue-fit mode — +
`paper-adversarial-review` first). This skill is the submission mechanics — the part that bit us with
avoidable friction the first time. Distilled from the AgenticDev 2026 submission.
## Venue specifics — a DATA card, not a skill
The venue-specific facts (deadline, page limits, tracks, PC-member conflict list, blind model, format
quirks, whether a supplementary-upload field exists, the extension target) live as **plain reference
data files** under `references/venues/<venue>.md`:
- `references/venues/agenticdev.md` — AgenticDev @ ASE (workshop; ACM DL/IEEE Xplore).
- `references/venues/aisec.md` — AISec @ ACM CCS (security workshop; ACM DL; harder bar).
**The pattern (follow it for every new venue):** when you fetch a venue's exact submission instructions,
save them as a new **data file** `references/venues/<venue>.md` (short `title:` frontmatter only — NOT a
skill with `name:`/`description:`). This preserves the "save the exact venue i