Agent skill

Venue Fork

by flonat in flonat/flonat-research

Fork an existing paper into a concurrent second-venue submission variant with policy checks, separate Overleaf ownership, format conversion, budget refit, QA, and Atlas/Vault writeback.

MITAuto-check: notesDocuments & Office

Install Venue Fork

skills CLI
$ npx skills add flonat/flonat-research --skill venue-fork -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install flonat/flonat-research venue-fork --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/venue-fork .claude/skills/venue-fork && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
venue-fork
GitHub stars
146
Token cost
~2.7k tokens
SKILL.md length
1,269 words
Files
1
Skills in repo
83
Repo updated
First seen
Licence
MIT

At a glance

Fork an existing paper into a concurrent second-venue submission variant with policy checks, separate Overleaf ownership, format conversion, budget refit, QA, and Atlas/Vault writeback.

  • Works in 6 steps: CFP compliance sheet (blocks everything) → Create the fork → Document-class conversion → …
  • Submitting the same work concurrently to another permitted venue
  • SKILL.md covers When to Use, Phase 0 — CFP compliance sheet…, Phase 1 — Create the fork and Phase 2 — Document-class…, plus 6 more sections
  • Calls pdftotext and curl

What it does

Venue Fork is an agent skill from flonat/flonat-research. Fork an existing paper into a concurrent second-venue submission variant with policy checks, separate Overleaf ownership, format conversion, budget refit, QA, and Atlas/Vault writeback. Use when submitting the same work concurrently to another permitted venue. Not for preprints, ordinary retargeting, or camera-ready work.

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering LaTeX and Academic paper search. The repository describes itself as: Shareable Claude Code + Codex infrastructure for PhD researchers — skills, agents, hooks, and rules for academic workflows. The licence is MIT.

When your agent uses it

  • Submitting the same work concurrently to another permitted venue
  • Tasks that involve LaTeX
  • Tasks that involve Academic paper search

Example prompts

  • “/venue-fork”

Requirements

  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit, Bash, WebFetch, AskUserQuestion

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. CFP compliance sheet (blocks everything)
  2. Create the fork
  3. Document-class conversion
  4. Page-budget refit (relocate, never cut)
  5. QA gates (all must pass)
  6. Submission + writeback (after the user submits)

What it can do on your machine

Read from SKILL.md and the folder at commit da27600. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Write
    • Edit
    • Bash
    • WebFetch
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pdftotext
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Venue Fork loads about 2.7k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 1,269 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Glob, Grep, Write, Edit, Bash, WebFetch, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from flonat/flonat-research at commit da27600, republished under its MIT licence (© flonat). 1,269 words, ~2,703 tokens.

Download SKILL.mdSave it as .claude/skills/venue-fork/SKILL.md (or your agent's skills folder).
name
venue-fork
description
Fork an existing paper into a concurrent second-venue submission variant with policy checks, separate Overleaf ownership, format conversion, budget refit, QA, and Atlas/Vault writeback. Use when submitting the same work concurrently to another permitted venue. Not for preprints, ordinary retargeting, or camera-ready work.
allowed-tools
Read, Glob, Grep, Write, Edit, Bash, WebFetch, AskUserQuestion

Venue Fork: Second-Venue Submission Variant

Fork a paper for a second venue while the original submission keeps living. A fork is a copy (both venues track independently), unlike retarget-journal (a move) and preprint (a non-archival variant that must NOT get a vault submission entry).

When to Use

  • A venue window explicitly permits concurrent submission (e.g. WINE 2026 ⟷ FOCS/SAGT/AFT 2026)
  • A rejected paper needs a reformatted version for a differently-formatted venue
  • the user says "submit this also to X", "concurrent submission to X", "make the X version"

Phase 0 — CFP compliance sheet (blocks everything)

Fetch the official CFP (never WikiCFP alone; mark-unverified applies) and record:

ItemWhy it matters
Page limit + what's excluded (title page? references? appendix policy)Drives the refit budget in Phase 3
Font size / margins / class requirementsSubmission format is often looser than camera-ready (e.g. WINE: ≥11pt, ≥1in, any class; LNCS only at camera-ready)
Blind policyAnonymity QA in Phase 4; third-person self-citation per double-blind-self-citation rule
Concurrent policy — on BOTH sidesThe target naming the source venue is not enough; verify the source venue's CFP reciprocates
Deadlines: submission, rebuttal, notificationAlso the SOURCE venue's notification date

Timing analysis (report to the user): if the source venue notifies before the target's rebuttal/notification, acceptance there forces withdrawal from the target before any reviews arrive — the fork is then insurance + comments-on-rejection, not guaranteed feedback. Say so explicitly before doing the work.

Phase 1 — Create the fork

  1. New Overleaf project via Dropbox (the active client may create these — folder + main.tex = project): Apps/Overleaf/Paper {Theme} {Short Name} ({VENUE} {YY})/ — Title Case, venue suffix, per the existing naming convention. Resolve the Dropbox root per multi-machine.md.
  2. Copy from the source project: main.tex, the bib, figure dirs, any .bst the target format needs. Never edit the source project's files — it is a live submission surface. Copy files by name only — never cp -r a whole template/source dir into the new Overleaf folder, which would drag a .git in and make it a repo on the wrong remote. Confirm find <new-overleaf-folder> -name .git is empty. See .claude/rules/template-scaffold-strip-git.md.
  3. Project dir: mkdir <project>/paper-{venue}/ + relative symlink paper-{venue}/paper → ../../../../../Apps/Overleaf/<name> (absolute symlinks break cross-machine).

Phase 2 — Document-class conversion

Target submission formats like WINE's are satisfied by plain \documentclass[11pt,a4paper]{article}

  • \usepackage[margin=1in]{geometry}. Conversion map:
Source classStripReplace with
lipics-v2021\Copyright, \ccsdesc, \category, \relatedversion, \supplement, \funding, \acknowledgements, all \Event*/\SeriesVolume/\ArticleNo, \titlerunning/\authorrunning, 5-arg \author{}{}{}{}{}article \title + \author{Anonymous submission} + \date{}; keywords as a \noindent\textbf{Keywords:} line inside the abstract
llncs\titlerunning, \institute, \spnewtheorem defs, LNCS author-suppression hacksamsthm with explicit \newtheorem for every env the body uses (theorem, lemma, proposition, corollary, definition, example, remark, observation, claim); proof comes from amsthm — do NOT redefine. \keywords shim: \newcommand{\keywords}[1]{\par\medskip\noindent{\bfseries Keywords:} {\def\and{\unskip{} $\cdot$ }#1}}
acmart\ccsdesc, \keywords, \copyright*, \settopmatter, \authornoteas above
  • Grep the body first: grep -o '\\begin{[a-z]*}' main.tex | sort | uniq -c tells you exactly which theorem environments to define — the AFT paper needed none, the SAGT paper needed nine.
  • cleveref: load hyperref then \usepackage[capitalise,noabbrev]{cleveref} when the body uses \cref/\Cref (LIPIcs loads it via class option).
  • .bst files: plainurl.bst ships with TeX Live (urlbst); splncs04.bst must be copied into the fork. Check with kpsewhich <name>.bst before assuming.

Shared math core. A class conversion is a legitimate adoption window for user-math.sty (templates/venues/_shared/): copy it in, load it AFTER the new class, and delete the preamble's now-duplicate \newcommand{\E}-style lines — it supplies the macro set, operators, delimiters, and theorem environments clash-safely ([notheorems] when the kit owns them). Papers not being converted are NOT retrofitted (templates/venues/_shared/README.md; candidates: docs/reference/user-math-adoption-candidates.md).

Phase 3 — Page-budget refit (relocate, never cut)

  1. Compile; find where the body ends: pdftotext -f N -l N main.pdf - per page around the expected boundary — locate the References header page.
  2. Compute overrun against the CFP budget (mind what's excluded: title page/references usually don't count; an 18pp LNCS body ≈ 12–13pp at 11pt/1in — LNCS text block is ~40% smaller).
  3. Relocate in this order until the body fits, adding \appendix sections with pointer lines (\noindent\emph{The proof appears in Appendix~\ref{...}.}):
    1. Detail subsections readers can defer (experimental-design grids, implementation details)
    2. Large floats (tables/figures) — \cref keeps resolving when labels move with the float
    3. Longest proofs → "Omitted Proofs" appendix, re-titled \begin{proof}[Proof of Theorem~\ref{...}]
    4. Whole peripheral sections (motivating applications, extended demarcation)
  4. Never cut prose to fit — relocation only (manuscript-edit-budget rule). Update any in-text Section~\ref pointing at moved content to Appendix~\ref.

Phase 4 — QA gates (all must pass)

  • latexmk -pdf exit 0; grep -c 'LaTeX Warning: Reference\|Warning: Citation' main.log → 0.
  • Body-end page ≤ budget (re-run the Phase 3 boundary check — floats move on recompile).
  • Anonymity grep on the tex: author surname, first name, all affiliated institutions, acknowledg, our prior, we showed, in earlier work. Then eyeball p1 of the PDF.
  • Render-level check (compile logs cannot catch wrong-symbol output): pdftotext the PDF and grep for symbols that should/shouldn't appear — especially after any macro rename (see Gotchas).
Show full SKILL.md (472 more words)Show less

Phase 5 — Submission + writeback (after the user submits)

Multi-system completeness — all of these, then verify:

  1. Vault submission file submissions/<topic>-<venue>-<year>.md: status: Submitted, submitted_date, and exactly one attention date: notification_date for a real CFP decision date or follow_up_date for an operational journal check-in. Set conference dates, double_blind, paper_id, and a body concurrency clause: which venue notifies first and the withdrawal obligation. Link the primary submission entry.
  2. Atlas topic outputs[]: new venue entry, status: Submitted (output-ladder canon only), same dates, notes carrying the concurrency clause, and the full submission-join set per rules/atlas-status-vocabulary.md § submission-join completeness: paper_id (same as the vault entry), paper_title (must equal the registry canonical_title), and — if the venue is a Conference/Workshop — cycle: <Venue> <edition-year> (journals exempt). (Do NOT bump last_reviewed — a venue swap is not topic-file curation; only update-topic-file writes that field.) Validate with atlas-vault/schema.py; validate-portfolio-registry.py catches any missed join as cycle-gap/title-gap at the next session-close. If the fork target has no venue file yet, create ~/vault/venues/<slug>.md with canon-only ranking fields (cabs/core/scimago/venue_type from the fixed sets — lookup caveats go in # comments after a canon value, never in the value).
  3. Submitted-PDF archive: verify the HotCRP/CMT-downloaded PDF page-matches the local build, file at <project>/paper-{venue}/submitted-YYYY-MM-DD.pdf (outside the Overleaf symlink), add a pointer line in the vault entry.
  4. Inbox: curl -X POST localhost:8765/api/sync (Mac Mini) and confirm the notification item appears; mark the met submission-deadline item done.

Gotchas (each cost real time on 2026-07-02)

  • Macro renames: \b does not fire before _. re.sub(r'\\cap\b', ...) misses \cap_j (underscore is a word char) — and the un-renamed token still compiles, rendering the WRONG symbol silently. Use (?![a-zA-Z]) as the boundary and pdftotext-verify the output.
  • Macro names: \newcommand{\cap_} is invalid (redefines \cap); never end a macro name with _; check clashes with amssymb (\Cap) before choosing.
  • Missing bib looks fine in Overleaf because a copied .bbl renders references anyway — check the file list, not the PDF, when confirming the fork is complete.
  • Paperpile CLI snapshot lag: freshly imported refs miss in get-item/lookup-by-doi for a while; the app-side BibTeX export is the authoritative canonical-key source meanwhile.
  • Merge adjacent \cite{a}\cite{b} → \cite{a,b} after batch key swaps.

Anti-Patterns

  • Don't edit or compile inside the source venue's Overleaf project — fork first, then touch.
  • Don't cut prose to make the page budget — relocate to appendices.
  • Don't create the vault submission entry for a preprint-server post — that's preprint's domain and the preprint-vs-submission rule forbids it.
  • Don't skip verifying the concurrent policy on the SOURCE venue's side.
  • Don't report "ready" from compile success alone — run the render-level check.
  • Don't hand-author bib entries — Paperpile-canonical keys only (paperpile-citations rule).

Verification

The fork is done when: fork compiles clean at/under budget with 0 warnings; anonymity + render checks pass; source project untouched (ls -lt mtimes); after submission, vault + atlas agree (Submitted, same dates), schema validates, the inbox shows the notification or follow-up item, and the submitted-PDF archive is filed with a pointer.

© flonat, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/venue-fork of flonat/flonat-research.

Open the folder on GitHubat commit da27600

Compare with similar skills

Venue Fork next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Venue Fork compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Venue Fork this skillflonat/flonat-research146—~2.7kAutomated safety check: NotesMIT
Paper Interpreterchujianyun/skills740—~810Automated safety check: PassCustom licence
Latex Paper ArtifactBingHanOfUESTC/open_agent_team106—~635Automated safety check: PassMIT
Write Paperfrenzymath/Danus476—~18kAutomated safety check: PassApache-2.0
Paper2htmlcnfjlhj/ai-collab-playbook453—~2.4kAutomated safety check: PassNone
Paper 2 Webdavila7/claude-code-templates32k12 repos~4kAutomated safety check: NotesMIT

Similar skills

  • Paper Interpreter

    chujianyun/skills

    论文解读助手。适用于用户发送 arXiv 论文链接,并希望下载论文、解读论文、生成读书笔记、做论文拆解或输出详细报告时使用。会在工作目录创建论文文件夹、下载 PDF 与 TeX Source(如有)、生成中文 Markdown 报告。默认先交付初稿,不自动复查;如果用户明确同意,再安排后续复查。不适用于只要简短推荐语的情况。

    740 GitHub stars~810 tokensUpdated today
    Documents & OfficeAuto-check passed
  • Latex Paper Artifact

    BingHanOfUESTC/open_agent_team

    A skill your agent uses when producing the final arXiv-style LaTeX paper, BibTeX, figures, tables, reproducibility statement, appendix, and artifact manifest.

    106 GitHub stars~635 tokensUpdated 3 mo ago
    Documents & OfficeAuto-check passed
  • Write Paper

    frenzymath/Danus

    Turn a project's verified fact graph into a publishable LaTeX paper in a configurable house style — a standalone amsart .tex with a real bibliography, compiled to PDF.

    476 GitHub stars~18k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed
  • Paper2html

    cnfjlhj/ai-collab-playbook

    A skill your agent uses when turning an academic paper PDF/arXiv/OpenReview page/local LaTeX source into a single-file Chinese HTML deep-reading page, especially when the user wants a Cheat-Sheet…

    453 GitHub stars~2.4k tokensUpdated 25 days ago
    Documents & OfficeAuto-check passed
  • Paper 2 Web

    davila7/claude-code-templates

    This skill should be used when converting academic papers into promotional and presentation formats including interactive websites (Paper2Web), presentation videos (Paper2Video), and conference…

    32k GitHub starsUsed in 12 repos~4k tokens
    Documents & OfficeAuto-check: notes
  • Paper Orchestra

    Ar9av/PaperOrchestra

    Orchestrate the full PaperOrchestra (Song et al., 2026, arXiv:2604.05018) five-agent pipeline to turn unstructured research materials (idea, experimental log, LaTeX template, conference guidelines…

    677 GitHub starsUsed in 1 repo~3.5k tokens
    Research & ScienceAuto-check passed

More from flonat/flonat-research

All 83 skills in this repo
  • Latex Posters

    flonat/flonat-research

    Create a large-format academic poster in LaTeX using beamerposter, tikzposter, or baposter.

    146 GitHub stars~1.5k tokensUpdated 10 days ago
    Auto-check: notes
  • Skill Creator

    flonat/flonat-research

    Create, revise, and evaluate reusable AI workflow skills, including trigger-quality tests.

    146 GitHub stars~4.4k tokensUpdated 10 days ago
    Auto-check passed
  • DOCX

    flonat/flonat-research

    Create, read, edit, or convert Microsoft Word documents while preserving professional document structure.

    146 GitHub stars~1.2k tokensUpdated 10 days ago
    Auto-check passed
  • PDF

    flonat/flonat-research

    Read, create, combine, split, rotate, OCR, watermark, secure, or extract content from PDF files.

    146 GitHub stars~488 tokensUpdated 10 days ago
    Auto-check passed
  • Init Project Orchestration

    flonat/flonat-research

    Create or migrate project-level agents, repeatable project workflows, and planning state from one client-neutral contract, then render repository-scoped adapters for both Claude Code and Codex.

    146 GitHub stars~1.6k tokensUpdated 10 days ago
    Auto-check passed
  • Pre Commit Audit

    flonat/flonat-research

    Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers.

    146 GitHub stars~2.8k tokensUpdated 10 days ago
    Auto-check: notes

Questions about Venue Fork

What does Venue Fork do?

Fork an existing paper into a concurrent second-venue submission variant with policy checks, separate Overleaf ownership, format conversion, budget refit, QA, and Atlas/Vault writeback. Venue Fork is an agent skill from flonat/flonat-research. Fork an existing paper into a concurrent second-venue submission variant with policy checks, separate Overleaf ownership, format conversion, budget refit, QA, and Atlas/Vault writeback.

When should I use Venue Fork?

Venue Fork fits situations like: submitting the same work concurrently to another permitted venue; tasks that involve LaTeX; tasks that involve Academic paper search.

How do I install Venue Fork in Claude Code?

Run `npx skills add flonat/flonat-research --skill venue-fork -a claude-code`. Or copy the skill folder (skills/venue-fork in flonat/flonat-research) into .claude/skills/venue-fork in your project. Claude Code loads it when a task matches its description.

How do I install Venue Fork in Codex?

Run `npx skills add flonat/flonat-research --skill venue-fork -a codex`. Or copy the skill folder (skills/venue-fork in flonat/flonat-research) into .agents/skills/venue-fork in your project. Codex loads it when a task matches its description.

Can I use Venue Fork in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add flonat/flonat-research --skill venue-fork -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/venue-fork, .gemini/skills/venue-fork, .github/skills/venue-fork and .opencode/skills/venue-fork in your project.

What does Venue Fork need to run?

Going by SKILL.md and its folder, Venue Fork needs the command-line tools its instructions call (pdftotext and curl). Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit, Bash, WebFetch, AskUserQuestion.

Does Venue Fork access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Venue Fork safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Venue Fork use?

Venue Fork is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Venue Fork use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Venue Fork?

Skills that share tags, products or a category with Venue Fork: Paper Interpreter (chujianyun/skills, 740 stars), Latex Paper Artifact (BingHanOfUESTC/open_agent_team, 106 stars), Write Paper (frenzymath/Danus, 476 stars) and Paper2html (cnfjlhj/ai-collab-playbook, 453 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Venue Fork?

flonat (a GitHub user) maintains it in flonat/flonat-research, which has 146 GitHub stars. The repository holds 83 skills in this directory. The repository was last updated on September 29, 2026.

Source: flonat/flonat-research on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.