Agent skill

Oleafly Pre Submission

by Oleafly in Oleafly/Oleafly

Run a pre-flight pass over the project before uploading to arXiv or a venue, and write a pass or fail checklist.

MITAuto-check passedResearch & Science

Install Oleafly Pre Submission

skills CLI
$ npx skills add Oleafly/Oleafly --skill oleafly-pre-submission -a claude-code

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

GitHub CLI
$ gh skill install Oleafly/Oleafly oleafly-pre-submission --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/Oleafly/Oleafly.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src-tauri/resources/skills/oleafly-pre-submission .claude/skills/oleafly-pre-submission && 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
oleafly-pre-submission
GitHub stars
212
Token cost
~2.9k tokens
SKILL.md length
1,593 words
Files
5 (incl. references, assets)
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Run a pre-flight pass over the project before uploading to arXiv or a venue, and write a pass or fail checklist.

  • Works in 8 steps: Establish the target → Build clean → Source hygiene for arXiv → …
  • Preparing an arXiv submission
  • SKILL.md covers 1. Establish the target, 2. Build clean, 3. Source hygiene for arXiv and 4. Front matter and metadata, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Oleafly Pre Submission is an agent skill from Oleafly/Oleafly. Run a pre-flight pass over the project before uploading to arXiv or a venue, and write a pass or fail checklist. Use when preparing an arXiv submission or a camera-ready, when checking anonymity for a double-blind venue, page limits, reference style, or supplementary material rules, when hunting undefined references, missing fonts, or figure problems that only surface at the publisher, or when building a clean source bundle to upload.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files and assets (for example `assets/checklist-template.md`, `references/arxiv-checks.md` and `references/log-warnings.md`). Compatibility notes: Any Oleafly project. The compile and log checks need a project that builds. arXiv source rules apply to LaTeX projects only, and Typst projects get their own…

It sits in Research & Science, covering Academic paper search and LaTeX. It works with arXiv and LaTeX. The repository describes itself as: The local-first AI assisted research workspace for scientific writing & publishing. Research, Write, Compile, Verify and Publish in LaTeX • Typst • Markdown • Git-native • Open…. The licence is MIT.

When your agent uses it

  • Preparing an arXiv submission
  • Checking anonymity for a double-blind venue
  • Reference style
  • Supplementary material rules

Example prompts

  • “/oleafly-pre-submission”

Requirements

  • Compatibility (from SKILL.md): Any Oleafly project. The compile and log checks need a project that builds. arXiv source rules apply to LaTeX projects only, and Typst projects get their own source checks. Venue depth improves when the venue-templates skill is enabled.
  • Pre-approved tools (allowed-tools): read_file, list_files, search_project, project_map, compile, get_log, get_pdf_text, verify_pdf_pages, create_file, write_file, run_command, load_skill, read_skill_file, show_location, update_todos

Workflow steps

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

  1. Establish the target
  2. Build clean
  3. Source hygiene for arXiv
  4. Front matter and metadata
  5. Figures and tables
  6. Licensing, consent, and integrity
  7. Build the bundle
  8. Write the checklist

What it can do on your machine

Read from SKILL.md and the folder at commit dc582ef. 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_file
    • list_files
    • search_project
    • project_map
    • compile
    • get_log
    • get_pdf_text
    • verify_pdf_pages
    • create_file
    • write_file

    …and 5 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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.

  • Compatibility

    Any Oleafly project. The compile and log checks need a project that builds. arXiv source rules apply to LaTeX projects only, and Typst projects get their own source checks. Venue depth improves when the venue-templates skill is enabled.

    From compatibility in the SKILL.md frontmatter.

Context cost

Oleafly Pre Submission loads about 2.9k tokens when it runs, and up to ~7.1k if it reads all its reference files. Until then it costs about 115 tokens; SKILL.md has 1,593 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~115
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.1k

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 passed

The automated check found no risky patterns in SKILL.md.

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 Oleafly/Oleafly at commit dc582ef, republished under its MIT licence (© Oleafly). 1,593 words, ~2,932 tokens.

Download SKILL.mdSave it as .claude/skills/oleafly-pre-submission/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
oleafly-pre-submission
description
Run a pre-flight pass over the project before uploading to arXiv or a venue, and write a pass or fail checklist. Use when preparing an arXiv submission or a camera-ready, when checking anonymity for a double-blind venue, page limits, reference style, or supplementary material rules, when hunting undefined references, missing fonts, or figure problems that only surface at the publisher, or when building a clean source bundle to upload.
allowed-tools
read_file, list_files, search_project, project_map, compile, get_log, get_pdf_text, verify_pdf_pages, create_file, write_file, run_command, load_skill, read_skill_file, show_location, update_todos
compatibility
Any Oleafly project. The compile and log checks need a project that builds. arXiv source rules apply to LaTeX projects only, and Typst projects get their own source checks. Venue depth improves when the venue-templates skill is enabled.
license
MIT
metadata.version
1.1.0
metadata.skill-author
Oleafly

Pre-submission check

Everything that goes wrong at upload time is findable beforehand. This runs the checks and writes down what passed, what failed, and what only the author can decide.

Output is submission/checklist.md with a verdict per item. You do not fix things silently. You find them, report them, and fix only what the user asks you to fix.

1. Establish the target

Ask, or state your assumption:

  • arXiv, a journal, a conference, or more than one?
  • Initial submission, revision, or camera-ready? The rules differ at each stage.
  • Double-blind, single-blind, or open?
  • Which year and track?

The rules that matter are on the venue's current call for papers. Anything bundled here or in venue-templates is a snapshot that may be stale. Never state a page limit or a deadline from memory. Say where the number came from, or ask the user to confirm it.

When the venue-templates skill is enabled and read_skill_file is available, load_skill it and pull what applies:

  • references/conferences_formatting.md
  • references/journals_formatting.md
  • references/reviewer_expectations.md

Then use references/venue-rules.md in this skill for the checks that apply regardless of venue.

2. Build clean

  1. compile. Zero errors is the bar. A warning-free build is the goal.
  2. get_log and scan for the warnings that matter. references/log-warnings.md lists them with what each means and whether it blocks.
  3. project_map and read unresolvedRefs and unresolvedCites. Both must be empty. A ?? in the PDF is the single most common thing an author ships by accident.
  4. get_pdf_text and read the rendered text end to end. Look for ??, [?], a missing figure box, a truncated table, an orphaned heading, or a bibliography that stopped early.

Record the page count and compare it against the venue limit. Count what the venue counts: some exclude references, some exclude the appendix, some count everything.

3. Source hygiene for arXiv

Only for arXiv, and only for LaTeX sources. Read references/arxiv-checks.md in full and work through it. The short version, each of which is a checklist row:

  • The source builds with the engine arXiv will use. arXiv runs pdfLaTeX by default; Oleafly compiles with Tectonic, which is XeTeX. A document needing fontspec will not build on arXiv's default path.
  • \pdfoutput=1 within the first few lines of the main file when the document is meant to be built as PDF output.
  • The .bbl file is included. arXiv does not run BibTeX or Biber for you.
  • No absolute paths in \input, \include, \includegraphics, or \bibliography.
  • File names are plain ASCII with no spaces, no leading dots, and no two files differing only by case.
  • Figures are PDF, PNG, or JPEG. No .bmp, no .tif, and no mixing an .eps and a .pdf of the same figure.
  • Fonts are embedded, and none of them are Type 3 bitmaps.
  • Supplementary material that is not compiled sits in anc/.
  • The abstract for the metadata field fits arXiv's character limit. Check it before you open the form.
  • The license choice is deliberate. It cannot be changed after announcement.
Typst projects

arXiv does not build Typst. It refuses a PDF that was made from TeX, but a Typst PDF was not, so a PDF-only upload is the normal route. Skip the LaTeX rows above and check these instead, for arXiv and for any other venue:

  • The Typst version is on record. Read typst.version in project.json and write it into the checklist, so a camera-ready rebuild uses the same version. A project with no pin compiles with whatever default the app has at the time.
  • Every @preview import names an exact version, and the project has compiled once while online so the packages are cached.
  • The log has no unknown font family warning. Typst embeds and subsets every font it uses, so the risk is a silent fallback font, not a missing one.
  • The PDF title and author come from #set document(title: ..., author: ...). Check that the title matches, and for a double-blind venue that author is empty or absent.
  • A missing label or citation key stops a Typst compile with an error instead of printing ??, so a clean build already covers that row. Still read the bibliography in get_pdf_text, because an entry with missing fields renders without complaint.
  • When the venue wants source files, the bundle holds the main .typ file, every file it includes or imports, the .bib or .yml bibliography, every image, and a note with the Typst version.

4. Front matter and metadata

  • Title matches between the manuscript, the metadata, and any cover letter.
  • Abstract present, within the venue's word limit, and free of undefined macros, citations, and references to figures.
  • Author list complete, in the agreed order, with affiliations and any required identifiers.
  • Corresponding author and contact details where required.
  • Keywords or subject categories chosen.
  • Funding, acknowledgements, data availability, code availability, ethics, and conflict statements present where the venue asks for them.

For a double-blind venue, all of the following must be absent from the submission: author names, affiliations, acknowledgements, funding statements naming a grant holder, a repository URL that identifies the group, self-citations written in the first person ("in our previous work [12]"), and identifying metadata in the PDF. In a Typst project that metadata comes from the author in #set document(...). Search for them with search_project rather than trusting a read-through. references/venue-rules.md has the search patterns.

5. Figures and tables

  • Every figure and table referenced from the text.
  • Raster figures at the resolution the venue asks for, usually 300 dpi for photographs and 600 or more for line art. Vector where the figure is a plot or a diagram.
  • Text inside figures readable at print size, and no smaller than the caption text.
  • Colour is not the only encoding, and the palette works for colour-blind readers.
  • Captions self-contained: what is shown, what n is, what error bars mean.
  • Nothing important sitting outside the trim area or in the gutter.

Use verify_pdf_pages to look at the rendered pages when PDF page capture is on in Settings. It rasterizes up to six pages, so pick the pages with figures. When it is off, fall back to get_pdf_text and list_files.

Show full SKILL.md (591 more words)Show less
  • The target venue's preprint policy allows an arXiv posting at this stage.
  • The arXiv licence does not conflict with a later copyright transfer, and is irreversible after announcement.
  • Third-party and reused figures carry permission and attribution.
  • Ethics, consent, and data governance statements present where they apply.
  • Author contributions and conflicts declared.

7. Build the bundle

list_files and decide what goes up. Exclude:

  • .oleafly/ and everything under it, including build
  • .git/
  • editor and OS junk: .DS_Store, ._*, *.swp, *~
  • compile intermediates the venue does not want, except the .bbl, which arXiv needs
  • large source data that belongs in a repository

For a ZIP of the whole project, use the app: the Export menu has "Export as ZIP", which excludes application metadata and git internals for you.

For an arXiv upload, the tarball is a specific list of files, not the whole project. Name the files in the checklist. On macOS, build it with COPYFILE_DISABLE=1 so BSD tar does not embed ._ resource forks.

8. Write the checklist

create_file then write_file for submission/checklist.md, following assets/checklist-template.md. Each row carries the item, the verdict, and the evidence:

ItemVerdictEvidence
Compiles with zero errorspasscompile returned success, log has no error lines
No unresolved referencesfailproject_map reports unresolvedRefs: fig:ablation, tab:main
Page count within limitneeds decision9 pages of body, venue limit unconfirmed by the author

Three verdicts only: pass, fail, needs decision. Anything you could not check is needs decision with a note saying why, never a silent pass.

Then show_location on the first two or three failures, and report in chat: how many failures, what they are, and where the checklist is.

Decision points

SituationWhat to do
Venue unknownRun every general and arXiv check, mark the venue-specific rows needs decision
Compile failsStop the pass. A failing build makes every downstream check meaningless. Report the first error.
Document needs XeTeX or LuaTeX and the target is arXivFlag it as a fail with two options: make the source pdfLaTeX-compatible, or submit a PDF-only version
Typst project and the target is arXivPlan a PDF-only upload. Leave out the LaTeX source rows and add one row that records the upload as PDF only
Double-blind and an author name appears anywherefail, with every location listed
Page count over the limitfail. Do not start cutting text yourself unless asked.
PDF page capture is offNote it in the checklist and do the figure pass from the source and get_pdf_text
The user asks you to fix the failuresFix them one at a time, recompile after each, and rerun the checklist at the end

When something goes wrong

  • get_log is truncated: the log is capped, so recompile and read it immediately, or search the source for the construct the last visible error mentions.
  • project_map is not offered: fall back to search_project for \ref{, \cite{, and \label{ and reconcile by hand. In a Typst project search for @ references, #cite( calls, and <label> markers instead.
  • run_command is declined: everything except the tarball build can be done with the project tools. Say which check you skipped.
  • Fonts cannot be checked without external tools: mark the row needs decision and point the user at the PDF reader's document properties.
  • A venue rule cannot be confirmed: needs decision, with the exact question the user should answer. Never guess a number.

Artifacts

  • submission/checklist.md

Done when

  • Every row has a verdict and evidence.
  • No row is pass on an assumption.
  • The failures are listed in chat, worst first.
  • The user knows exactly which decisions are theirs.

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

Files

SKILL.md and 4 other files (references, assets) in src-tauri/resources/skills/oleafly-pre-submission of Oleafly/Oleafly.

  • SKILL.md
  • assets/checklist-template.md
  • references/arxiv-checks.md
  • references/log-warnings.md
  • references/venue-rules.md

Open the folder on GitHubat commit dc582ef

Compare with similar skills

Oleafly Pre Submission 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.

Oleafly Pre Submission compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Oleafly Pre Submission this skillOleafly/Oleafly212—~2.9kAutomated safety check: PassMIT
Paper OrchestraAr9av/PaperOrchestra6791 repos~3.5kAutomated safety check: PassCustom licence
Section Writing AgentAr9av/PaperOrchestra6791 repos~3.3kAutomated safety check: PassCustom licence
SearchMuuuun/luxas1.2k—~2.3kAutomated safety check: WarnMIT
Anmath Submissionfranklee16/academic-research-skills2231 repos~1.1kAutomated safety check: PassNone
Arxiv Latex Sourcewentorai/research-plugins2981 repos~2kAutomated safety check: PassMIT

Similar skills

  • 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…

    679 GitHub starsUsed in 1 repo~3.5k tokens
    Research & ScienceAuto-check passed
  • Section Writing Agent

    Ar9av/PaperOrchestra

    Step 4 of the PaperOrchestra pipeline (arXiv:2604.05018). An agent skill from Ar9av/PaperOrchestra.

    679 GitHub starsUsed in 1 repo~3.3k tokens
    Research & ScienceAuto-check passed
  • Search

    Muuuun/luxas

    Unified academic paper search, citation chains, paper download (arXiv LaTeX/PDF, Sci-Hub), figure extraction from papers, LaTeX source reading, BibTeX fetching, web search, and browser automation…

    1.2k GitHub stars~2.3k tokensUpdated 1 mo ago
    Research & ScienceAuto-check: warnings
  • Anmath Submission

    franklee16/academic-research-skills

    A skill your agent uses when running the final pre-submission preflight for an Annals of Mathematics manuscript — AMS-LaTeX compile, theorem environments, abstract and MSC, references, arXiv…

    223 GitHub starsUsed in 1 repo~1.1k tokens
    Research & ScienceAuto-check passed
  • Arxiv Latex Source

    wentorai/research-plugins

    Download and parse LaTeX source files from arXiv preprints. An agent skill from wentorai/research-plugins.

    298 GitHub starsUsed in 1 repo~2k tokens
    Research & ScienceAuto-check passed
  • Arxiv Paper Processor

    wentorai/research-plugins

    Process and analyze arXiv papers systematically for research workflows

    298 GitHub starsUsed in 1 repo~1.5k tokens
    Research & ScienceAuto-check passed

More from Oleafly/Oleafly

All 12 skills in this repo
  • Perform bounded, local exploratory analysis of explicitly supported scientific files.

    212 GitHub starsUsed in 2 repos~3.4k tokens
    Auto-check: notes
  • Experimental Design

    Oleafly/Oleafly

    Design experiments and studies BEFORE data is collected — choosing a design, randomizing, blocking, and laying out treatment combinations so results are interpretable.

    212 GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes
  • Facilitates evidence-aware scientific ideation with independent generation, structured discussion, explicit assumptions, transparent evaluation, adversarial review, and decision logs.

    212 GitHub starsUsed in 2 repos~3.5k tokens
    Auto-check passed
  • Create and audit truthful, accessible, publication-ready scientific figures with Matplotlib, Seaborn, or Plotly.

    212 GitHub stars~3.4k tokensUpdated today
    Auto-check: notes
  • Turn a research question into an annotated reading list with provenance.

    212 GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • Oleafly Research Loop

    Oleafly/Oleafly

    Entry point for research writing in Oleafly. An agent skill from Oleafly/Oleafly.

    212 GitHub stars~3.7k tokensUpdated today
    Auto-check passed

Works with

Questions about Oleafly Pre Submission

What does Oleafly Pre Submission do?

Run a pre-flight pass over the project before uploading to arXiv or a venue, and write a pass or fail checklist. Oleafly Pre Submission is an agent skill from Oleafly/Oleafly. Run a pre-flight pass over the project before uploading to arXiv or a venue, and write a pass or fail checklist.

When should I use Oleafly Pre Submission?

Oleafly Pre Submission fits situations like: preparing an arXiv submission; checking anonymity for a double-blind venue; reference style; supplementary material rules.

How do I install Oleafly Pre Submission in Claude Code?

Run `npx skills add Oleafly/Oleafly --skill oleafly-pre-submission -a claude-code`. Or copy the skill folder (src-tauri/resources/skills/oleafly-pre-submission in Oleafly/Oleafly) into .claude/skills/oleafly-pre-submission in your project. Claude Code loads it when a task matches its description.

How do I install Oleafly Pre Submission in Codex?

Run `npx skills add Oleafly/Oleafly --skill oleafly-pre-submission -a codex`. Or copy the skill folder (src-tauri/resources/skills/oleafly-pre-submission in Oleafly/Oleafly) into .agents/skills/oleafly-pre-submission in your project. Codex loads it when a task matches its description.

Can I use Oleafly Pre Submission 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 Oleafly/Oleafly --skill oleafly-pre-submission -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oleafly-pre-submission, .gemini/skills/oleafly-pre-submission, .github/skills/oleafly-pre-submission and .opencode/skills/oleafly-pre-submission in your project.

What does Oleafly Pre Submission need to run?

SKILL.md names no scripts, command-line tools or credentials: Oleafly Pre Submission is instructions for the agent only. Its frontmatter pre-approves these tools: read_file, list_files, search_project, project_map, compile, get_log, get_pdf_text, verify_pdf_pages, create_file, write_file, run_command, load_skill, read_skill_file, show_location, update_todos. Compatibility (from SKILL.md): Any Oleafly project. The compile and log checks need a project that builds. arXiv source rules apply to LaTeX projects only, and Typst projects get their own source checks. Venue depth improves when the venue-templates skill is enabled..

Does Oleafly Pre Submission access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Oleafly Pre Submission safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Oleafly Pre Submission use?

Oleafly Pre Submission is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Oleafly Pre Submission use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.1k tokens, read only when the agent opens those files.

What are the alternatives to Oleafly Pre Submission?

Skills that share tags, products or a category with Oleafly Pre Submission: Paper Orchestra (Ar9av/PaperOrchestra, 679 stars), Section Writing Agent (Ar9av/PaperOrchestra, 679 stars), Search (Muuuun/luxas, 1.2k stars) and Anmath Submission (franklee16/academic-research-skills, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Oleafly Pre Submission?

Oleafly (a GitHub organization) maintains it in Oleafly/Oleafly, which has 212 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 10, 2026.

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