AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Aaai Camera Ready

skill-brycewang-stanford-awesome-journal-skills-aaai-camera-ready · by brycewang-stanford

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.

No reviews yet
0 installs
13 views
0.0% view→install

Install

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

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-brycewang-stanford-awesome-journal-skills-aaai-camera-ready)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Aaai Camera Ready? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

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

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

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

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.