camera-ready-paper

Preserve byte-identical reviewed content while preparing camera-ready and arXiv releases.

4|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/AMindToThink/claude-code-settings --skill camera-ready-paper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: camera-ready-paper
Source: https://github.com/AMindToThink/claude-code-settings/tree/main/skills/camera-ready-paper
Command: npx skills add https://github.com/AMindToThink/claude-code-settings --skill camera-ready-paper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps turn an accepted, often anonymized paper into a public camera-ready or arXiv release without accidentally changing the reviewed content or violating concurrent-submission rules.

Core Features & Use Cases

  • Dual-submission safety: Checks whether a concurrent venue treats the work as archival or non-archival and flags risky public-release conditions.
  • Byte-identity discipline: Preserves the accepted paper's content exactly while allowing only de-anonymization edits in the public version.
  • Integrity and packaging workflow: Verifies citation and number-generation consistency, then prepares a reproducible arXiv bundle with the right files and validation steps.
  • Use case: An accepted conference paper needs a camera-ready PDF, a safe arXiv upload, and a changelog for reviewer-requested additions after review.

Quick Start

Use this skill to review the accepted paper, preserve the reviewed content byte for byte, de-anonymize only the public copy, and package a safe arXiv-ready release.

Frequently Asked Questions about camera-ready-paper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare a camera-ready paper without violating dual submission or concurrent venue rules?

To prepare a camera-ready paper safely, you must check whether concurrent venues treat the work as archival. This skill flags risky public-release conditions and enforces dual-submission safety during your camera-ready preparation.

How do I de-anonymize an accepted paper for arXiv without changing the reviewed content?

To de-anonymize an accepted paper for arXiv without content drift, you must preserve the accepted paper byte for byte. This skill enforces byte-identity discipline, allowing only de-anonymization edits on the public copy.

What is the best way to package a reproducible arXiv release bundle?

Packaging a reproducible arXiv release requires verifying citation consistency and bundling the correct files. This skill prepares a validated arXiv bundle with the right files and checks number-generation integrity.

Can I add reviewer-requested changes after the camera-ready PDF is generated?

Yes, you can add reviewer-requested changes after the camera-ready PDF is generated. This skill provides a safe handling workflow and changelog generation for post-review additions while preserving reviewed content integrity.

Does this skill check citation and number-generation consistency for camera-ready papers?

Yes, citation and number-generation consistency checking is a core feature. The integrity and packaging workflow verifies your references and numbers before preparing the final reproducible public archives.