Agent skill

Camera Ready

by flonat in flonat/flonat-research

Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews.

MITAuto-check passedResearch & Science

Install Camera Ready

skills CLI
$ npx skills add flonat/flonat-research --skill camera-ready -a claude-code

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

GitHub CLI
$ gh skill install flonat/flonat-research camera-ready --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/camera-ready .claude/skills/camera-ready && 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
camera-ready
GitHub stars
145
Token cost
~2.1k tokens
SKILL.md length
892 words
Files
1
Skills in repo
83
Repo updated
First seen
Licence
MIT

At a glance

Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews.

  • Works in 7 steps: Setup & verify → Camera-ready mechanics (low-risk) → Bibliography → …
  • A paper is accepted with no rebuttal and you need to de-anonymize
  • SKILL.md covers When to Use, Operating Rules (read first), Phase 0 — Setup & verify and Phase 1 — Camera-ready…, plus 8 more sections
  • Calls uv

What it does

Camera Ready is an agent skill from flonat/flonat-research. Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews. Use when a paper is accepted with no rebuttal and you need to de-anonymize, add copyright, turn on section numbering, implement each reviewer's minor revisions, optionally move proofs to a non-counted appendix, and QA. Not for R&R/revise-and-resubmit (use strategic-revision --external) or for preprints (use preprint).

Its SKILL.md is about 2.1k 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 Research & Science, covering Academic paper search and LaTeX. It works with LaTeX. 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

  • A paper is accepted with no rebuttal and you need to de-anonymize
  • Turn on section numbering
  • Implement each reviewers minor revisions
  • Optionally move proofs to a non-counted appendix

Example prompts

  • “/camera-ready”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, Bash(mkdir*), Bash(cp*), Bash(ls*), Bash(grep*), Bash(stat*), Bash(latexmk*), Bash(pdftotext*), Bash(pdftoppm*), Bash(mdls*), Bash(uv run python*), AskUserQuestion, Task

Workflow steps

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

  1. Setup & verify
  2. Camera-ready mechanics (low-risk)
  3. Bibliography
  4. Structure (appendix offload) — GATED on the page rule
  5. Reviewer revisions + intuition aids
  6. QA
  7. Author-side handoff

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
    • Write
    • Edit
    • Glob
    • Grep
    • Bash(mkdir*)
    • Bash(cp*)
    • Bash(ls*)
    • Bash(grep*)
    • Bash(stat*)

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

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv

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

  • Network

    No URLs in SKILL.md. Its commands use uv, 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

Camera Ready loads about 2.1k tokens when it runs. Until then it costs about 115 tokens; SKILL.md has 892 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.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 flonat/flonat-research at commit da27600, republished under its MIT licence (© flonat). 892 words, ~2,070 tokens.

Download SKILL.mdSave it as .claude/skills/camera-ready/SKILL.md (or your agent's skills folder).
name
camera-ready
description
Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews. Use when a paper is accepted with no rebuttal and you need to de-anonymize, add copyright, turn on section numbering, implement each reviewer's minor revisions, optionally move proofs to a non-counted appendix, and QA. Not for R&R/revise-and-resubmit (use strategic-revision --external) or for preprints (use preprint).
allowed-tools
Read, Write, Edit, Glob, Grep, Bash(mkdir*), Bash(cp*), Bash(ls*), Bash(grep*), Bash(stat*), Bash(latexmk*), Bash(pdftotext*), Bash(pdftoppm*), Bash(mdls*), Bash(uv run python*), AskUserQuestion, Task
skill-dependencies
proofread

camera-ready: Accepted Paper → Camera-Ready + Review Implementation

For a paper that has been accepted (no rebuttal stage): produce the camera-ready version and implement the reviewers' (typically minor) revisions. Distinct from strategic-revision --external, which handles R&R (rebuttal, DAG, resubmission strategy).

When to Use

  • Acceptance notification arrived; reviews are final; you implement rather than argue.
  • Triggers: "prepare the camera-ready", "implement the reviews for the accepted paper", "de-anonymize and finalize".

Operating Rules (read first)

  • Overleaf-canonical: edit the Overleaf/paper/ symlink target, not any git mirror (overleaf-canonical-source.md). The .tex is a live edit surface — obey reconcile-before-rewriting.md (fresh-read, narrow edits, no replace_all/full-Write, mtime check).
  • Phased-work: stop after each phase, summarize, await continue (phased-work.md) unless --autonomous.
  • mark-unverified: never assert a reviewer-suggested citation/venue fact you haven't verified.
  • Status logging: acceptance means the vault/atlas status should move to Accepted/camera-ready per multi-system-completeness.md — but if the formal decision letter hasn't landed yet (early prep), hold status changes until the user confirms.

Phase 0 — Setup & verify

  1. Save the reviews to paper-{venue}/correspondence/referee-reviews/<YYYY-MM-DD>-<venue>-reviews.md (score table + verbatim text).
  2. Back up the submitted main.tex/.bib/.pdf → paper-{venue}/backup/submitted-<YYYY-MM-DD>/.
  3. Verify reviewer-suggested citations before adding any (DOI/title via scholarly/paperpile); reviewers often mis-spell/mis-date (e.g. "Edelmann 1996" → Suchman & Edelman 1996). Stash verified new entries.
  4. Build a reviewer-point → action table so nothing is dropped; confirm scope with the user.
  5. Confirm the page-limit rule (see Phase 3) — [UNVERIFIED] until checked against the CfP/acceptance email.

Phase 1 — Camera-ready mechanics (low-risk)

  • De-anonymize: replace \author{Anonymous Submission} with the real author/affiliation block.
  • Copyright: AAAI auto-renders the slug from the style; set \copyrightyear{<proceedings year>}. ACM: set \setcopyright/\acmConference/DOI per the rights email. Never use \nocopyright for AAAI.
  • Section numbering: AAAI submissions ship with \setcounter{secnumdepth}{0} → set to 2. This also fixes blank Section~\ref{} references (a common reviewer complaint).
  • Compile; confirm 0 undefined refs and the copyright slug renders on p1.

Phase 2 — Bibliography

  • If adopting canonical (e.g. Paperpile) keys, invoke bib-rekey (DOI-safe remap + diff-verified \cite rewrite).
  • Add the verified reviewer-suggested citations and any self-citations (camera-ready is de-anonymized, so self-cites are normal — use the published entry, not the arXiv preprint, when one exists).
  • Compile; 0 undefined citations.

Phase 3 — Structure (appendix offload) — GATED on the page rule

  • First verify whether the venue's page limit excludes the technical appendix (AAAI/AIES typically count body + figures; references and a post-references appendix are often exempt — confirm). This determines how aggressively to offload.
  • If excluded: move full proofs / long derivations / worked-example arithmetic to \appendix after references; leave each result's statement + a 3–5 sentence proof sketch + appendix pointer in the body.
  • Equation-label coupling: if a proof you are moving defines equations the body references, lift those equations into the body first (else body text points at appendix equation numbers). Verify 0 undefined after.

Phase 4 — Reviewer revisions + intuition aids

  • Implement each row of the Phase-0 action table.
  • Common high-value additions for broad-audience venues: a plain-language mechanics paragraph, a notation table, a results-at-a-glance table, one-line Reading glosses, and a mechanism figure/boxed causal chain (covers "more visualization" and "more plain-language" asks at once).
  • Apply any consistency fixes surfaced in Phase 0 (e.g. clamped first-best, index-vs-probability clarifications) — flag any that touch a theorem's math for author sign-off before editing.
Show full SKILL.md (381 more words)Show less

Phase 5 — QA

  • latexmk clean (exit 0); 0 undefined refs/citations; no large overfull boxes; no placeholders/TODOs.
  • Page-budget check: locate where references/appendix begin (pdftotext + form-feed page count, or per-label pages from .aux); confirm body ≤ limit (appendix/refs exempt per Phase 3).
  • Visual render key pages (pdftoppm) — de-anon header + copyright slug, new tables/figures, appendix.
  • Run proofread scoped to the new prose only.
  • Token conservation vs the submitted version — uv run python .scripts/check_token_conservation.py --source backup/<submitted>.tex --revision <current>.tex per edited file: every advisory row (changed number, dropped/added citation) must map to a Phase-0 action-table row or a Phase-3 appendix move. Spot-check reworded claims against the claim-strength ladder (docs/reference/claim-strength-ladder.md) — no silent strength moves between the reviewed version and camera-ready.
  • Arithmetic forensics (empirical papers) — uv run python .scripts/check_stat_forensics.py <main>.tex: recomputed p-values, df-vs-N, t-vs-descriptives, GRIM. Any HARD finding gets resolved or explained before upload — reviewers approved the numbers as submitted; the camera-ready must not introduce (or ship) an arithmetic impossibility.

Phase 6 — Author-side handoff

Report what remains for the human: acknowledgments (now un-anonymized — offer a funding stub), signed copyright/rights form, reproducibility checklist, and the vault/atlas status update to Accepted (per the Operating Rules caveat).

When the user confirms the camera-ready was uploaded: append the history: rows to the vault submission entry (event: decision, outcome: accept if not already recorded, then event: camera-ready with the archive files: pointer) and archive the as-submitted files per rules/submission-file-archive.md (human-supplied only).

Anti-Patterns

  • Don't move proofs to an appendix before confirming the appendix is page-exempt. If it counts, you've just relocated, not saved, space.
  • Don't replace_all or full-Write the live .tex. Narrow edits; for bulk citekey work defer to bib-rekey's diff-verified flow.
  • Don't add a reviewer-suggested citation from memory. Verify it — reviewers mis-cite.
  • Don't chain all phases in one response. Checkpoint per phased-work.md.
  • Don't log acceptance to vault/atlas if the formal decision letter hasn't arrived — confirm with the user.

Verification

  • All reviewer points map to a concrete edit (action table fully checked off).
  • Build clean, 0 undefined, body within page limit, copyright slug present, author block de-anonymized.
  • Submitted version preserved in backup/.

Cross-References

SkillRelationship
bib-rekeyPhase 2 bibliography rekey + \cite remap
strategic-revision --externalThe R&R counterpart (rebuttal + DAG) — use that, not this, for revise-and-resubmit
proofread, latex, bib-validateQA components composed in Phases 2 & 5
preprintFor an arXiv/working-paper variant instead of a venue camera-ready

© 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/camera-ready of flonat/flonat-research.

Open the folder on GitHubat commit da27600

Compare with similar skills

Camera Ready 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.

Camera Ready compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Camera Ready this skillflonat/flonat-research145—~2.1kAutomated safety check: PassMIT
Paper OrchestraAr9av/PaperOrchestra6771 repos~3.5kAutomated safety check: PassCustom licence
Section Writing AgentAr9av/PaperOrchestra6771 repos~3.3kAutomated safety check: PassCustom licence
SearchMuuuun/luxas1.2k—~2.3kAutomated safety check: WarnMIT
Oleafly Pre SubmissionOleafly/Oleafly206—~2.9kAutomated safety check: PassMIT
Oleafly Review ManuscriptOleafly/Oleafly206—~2.3kAutomated 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…

    677 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.

    677 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
  • Oleafly Pre Submission

    Oleafly/Oleafly

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

    206 GitHub stars~2.9k tokensUpdated today
    Research & ScienceAuto-check passed
  • Run a referee-grade review of the manuscript in the open project without changing a single manuscript file.

    206 GitHub stars~2.3k tokensUpdated today
    Research & ScienceAuto-check passed
  • Literature Survey Generator

    brycewang-stanford/Auto-Empirical-Research-Skills

    Generate a complete academic literature survey from scratch using multi-agent orchestration.

    4.5k GitHub stars~2.7k tokensUpdated 2 days ago
    Research & ScienceAuto-check: notes

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.

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

    flonat/flonat-research

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

    145 GitHub stars~4.4k tokensUpdated 8 days ago
    Auto-check passed
  • DOCX

    flonat/flonat-research

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

    145 GitHub stars~1.2k tokensUpdated 8 days ago
    Auto-check passed
  • PDF

    flonat/flonat-research

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

    145 GitHub stars~488 tokensUpdated 8 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.

    145 GitHub stars~1.6k tokensUpdated 8 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.

    145 GitHub stars~2.8k tokensUpdated 8 days ago
    Auto-check: notes

Works with

Questions about Camera Ready

What does Camera Ready do?

Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews. Camera Ready is an agent skill from flonat/flonat-research. Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews.

When should I use Camera Ready?

Camera Ready fits situations like: A paper is accepted with no rebuttal and you need to de-anonymize; turn on section numbering; implement each reviewers minor revisions; optionally move proofs to a non-counted appendix.

How do I install Camera Ready in Claude Code?

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

How do I install Camera Ready in Codex?

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

Can I use Camera Ready 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 camera-ready -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/camera-ready, .gemini/skills/camera-ready, .github/skills/camera-ready and .opencode/skills/camera-ready in your project.

What does Camera Ready need to run?

Going by SKILL.md and its folder, Camera Ready needs the command-line tools its instructions call (uv). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, Bash(mkdir*), Bash(cp*), Bash(ls*), Bash(grep*), Bash(stat*), Bash(latexmk*), Bash(pdftotext*), Bash(pdftoppm*), Bash(mdls*), Bash(uv run python*), AskUserQuestion, Task.

Does Camera Ready access the network?

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

Is Camera Ready 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 Camera Ready use?

Camera Ready 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 Camera Ready use?

About 2.1k tokens (SKILL.md is roughly 8.3k 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 Camera Ready?

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

Who maintains Camera Ready?

flonat (a GitHub user) maintains it in flonat/flonat-research, which has 145 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.