# Aaai Camera Ready

> Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.

- **Type:** Skill
- **Install:** `agentstack add skill-brycewang-stanford-awesome-journal-skills-aaai-camera-ready`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [brycewang-stanford](https://agentstack.voostack.com/s/brycewang-stanford)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [brycewang-stanford](https://github.com/brycewang-stanford)
- **Source:** https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/AAAI-Skills/skills/aaai-camera-ready
- **Website:** https://www.copaper.ai

## Install

```sh
agentstack add skill-brycewang-stanford-awesome-journal-skills-aaai-camera-ready
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# AAAI Camera Ready

Use this after AAAI acceptance. Reopen the current camera-ready email, publication/attendance page,
author kit, copyright instructions, and proceedings source-file requirements.

## Camera-ready checklist

- Apply the current AAAI proceedings template and page rules. AAAI-26 accepted main-track papers
  used 7 proceedings pages plus pages solely for references and acknowledgments, with an option to
  purchase up to two additional technical-content pages.
- Prepare source files as required: LaTeX or Word source, figures, bibliography, style files, and a
  high-resolution PDF.
- Add author names, affiliations, acknowledgments, funding, and ethical disclosures where required.
- Keep all references from the submitted paper unless superseded, and explain major citation updates
  conservatively.
- Resolve reviewer-facing clarity issues without changing the scientific identity of the paper.
- Complete copyright transfer and any AAAI Digital Library metadata.
- Ensure at least one author registers and presents the paper, unless current exceptional-circumstance
  procedures apply.

## AAAI Press production gotchas

AAAI Press compiles the proceedings from your source, so a PDF that looks fine locally can still be
kicked back. The two-column AAAI style is strict about a few things that trip up authors arriving
from single-column or NeurIPS-style submissions:

- Do not alter margins, font sizes, or column gap; AAAI explicitly forbids style hacks to gain space.
  If you need room, purchase technical pages instead of shrinking the template.
- Disable `\pdfoutput` overrides and embed all fonts; non-embedded fonts are a common rejection.
- Move references and acknowledgments into the pages that do not count against the technical limit,
  per the current rule, rather than padding the main body.
- Restore author block, funding, and ethics statements that were stripped for double-blind review.

## Deanonymization sweep

Acceptance reverses the anonymity discipline: now identity must be present and correct, while stale
blind-mode placeholders must go. Walk the paper, supplement, and code for "Anonymous", redacted
citations to your own prior work, and `\\if-blind` toggles still set to blind.

## Worked vignette

A knowledge-representation paper lands at 7.5 technical pages after restoring the author block and an
ethics statement. Decision: it cannot shrink the template, so the author buys one extra technical
page (within the current cap), keeps references on the non-counting pages, and re-runs the
deanonymization sweep before uploading source to AAAI Press.

## Release plan

- Replace anonymous code/data links with durable public repositories or archives.
- Publish a project page only if it is stable, accurate, and does not overclaim beyond the paper.
- Preserve a copy of the submitted PDF, reviews, rebuttal, accepted PDF, source package, and artifact
  release for future journal extensions.

## Output format

```text
[Camera-ready state] Ready / Needs fixes / Blocked
[Proceedings files] 
[Page status] within limit / extra pages needed / over limit
[Publication obligations] copyright / registration / presentation / metadata
[Final fixes] 
```

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [brycewang-stanford](https://github.com/brycewang-stanford)
- **Source:** [brycewang-stanford/Awesome-Journal-Skills](https://github.com/brycewang-stanford/Awesome-Journal-Skills)
- **License:** MIT
- **Homepage:** https://www.copaper.ai

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-brycewang-stanford-awesome-journal-skills-aaai-camera-ready
- Seller: https://agentstack.voostack.com/s/brycewang-stanford
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.