Menu
Use when you need to retarget a paper to a different journal (rename, swap bib, update citations).
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when you need to audit a research project against the init-project-research template.
Use when you need to validate a paper's bibliography — cross-references \cite{} keys against .bib files or embedded \bibitem entries, finds missing/unused/typo'd keys, and checks every key against the Paperpile library via the local resolver. Deep verification mode spawns parallel agents for DOI/metadata validation at scale. Fix mode rekeys drifted keys to canonical and stages missing entries for Paperpile.
Use when you need to bootstrap a full research project with directory scaffold and Overleaf symlink.
Use when you need to create a preprint / working-paper variant of a paper currently in conference or journal format. Forks the existing Overleaf project — adds a `preprint/` subfolder using the user's `your-template` Template, ports the body content from the source paper. The preprint is accessed locally via the existing `paper-{venue}/paper/preprint/` path (subfolder under the conference paper's symlink); no separate `paper-wp/` directory. Trigger on "set up a working paper", "create a preprint", "WP version", "arXiv-ready version", "ready to preprint". Never creates a new top-level Overleaf project — always nests inside the existing one. Never uses the conference's own style (.sty / .cls); always swaps to `your-template`.
Use when you need academic proofreading of a LaTeX paper (11 check categories).
Use when you need to assemble, anonymize, or audit a replication package.
| name | retarget-journal |
| description | Use when you need to retarget a paper to a different journal (rename, swap bib, update citations). |
| allowed-tools | Bash(latexmk*), Bash(pdflatex*), Bash(xelatex*), Bash(mkdir*), Bash(ls*), Bash(cp*), Bash(mv*), Bash(git*), Read, Write, Edit, Glob, Grep, Task |
| argument-hint | ["target-journal-name"] |
Switch a paper manuscript from one journal to another. Handles folder renaming, bibliography swaps, citation key updates, formatting changes, and compilation verification.
Ask the user for:
Read the project's CLAUDE.md and README.md to understand current state.
Read the current manuscript and compare against the target journal's requirements:
| Check | What to compare |
|---|---|
| Word/page limit | Does the draft fit? Need to cut or can expand? |
| Required sections | Does the target need sections the current draft lacks? (e.g., "Relevance Statement", "AI Disclosure") |
| Citation style | Author-year vs numbered? natbib vs biblatex? |
| Formatting | Template class? Column layout? Font requirements? |
| Supplementary material | Online appendix conventions? |
Present the assessment to the user before proceeding.
Rename project folder if it references the old journal:
mv "old-journal-name/" "new-journal-name/"
Update Overleaf symlink if one exists:
# Remove old symlink
rm paper/
# Create new symlink to the correct Overleaf directory
ln -s "/path/to/Overleaf/new-project" paper
Update folder references in CLAUDE.md, README.md, .gitignore
.bib file if the user provides a new export from Paperpile.tex files:
.bib to get the new key format\cite{...}, \citet{...}, \citep{...}, \citeauthor{...} commands in .tex files/bib-validate to ensure no missing or unused keys\bibliographystyle{} if citation style changesCLAUDE.md — update target journal, formatting notesREADME.md — update journal reference, submission infoMEMORY.md — carry forward any learnings, update journal-specific noteshistory: row (event: decision, outcome: reject or event: withdrawn) to the OLD venue's submission entry per rules/submission-file-archive.md § history — the new target's entry gets its own history: when it is actually submitted, not at retarget timeoutputs[] — update the retargeted output's venue (slug must resolve to a ~/vault/venues/ file). Refresh or clear cycle: if the new venue is a Conference/Workshop and the output is submission-active, set cycle: <NewVenue> <edition-year>; if the new venue is a journal, remove any stale cycle — per rules/atlas-status-vocabulary.md § submission-join completeness. A stale cycle from the old venue must never survive a retarget. If the retarget also changed the paper's title, update paper_title here and the registry canonical_title together (keep them aligned per paper-vault-alignment.md).out/ with latexmkReport a summary:
Retargeted [Paper Name]: [Old Journal] → [New Journal]
Changes made:
- Folder: [old path] → [new path]
- Symlink: updated to [new Overleaf project]
- Bibliography: [N] citation keys updated
- Sections added: [list]
- Sections removed: [list]
- Page count: [N] pages (limit: [M])
- Compilation: clean (0 warnings)
Updated: CLAUDE.md, README.md, vault
.bib file — rename it to old-journal.bib.bak as a safety copyWhen retargeting, the writing style often needs to change too — not just the formatting. Read the appropriate guide from the shared venue-guides resource:
skills/shared/venue-guides/venue_writing_styles.md — style spectrum and adaptation tipsskills/shared/venue-guides/journals_formatting.md (journals) / conferences_formatting.md (conferences)nature_science_style.md, ml_conference_style.md, cs_conference_style.md, cell_press_style.md, medical_journal_styles.md — all in skills/shared/venue-guides/skills/shared/venue-guides/examples/ — abstract and introduction formats by venue type| Skill | When to use alongside |
|---|---|
/bib-validate | After Phase 3 to verify all citation keys |
/latex | Default compiler — use for compilation with auto error resolution |
/latex | For manual compilation config and .latexmkrc setup |
/proofread | After retarget to check for remnants of old journal formatting |
vault sync (edit vault files directly) | After Phase 5 to sync with central context library |