Skip to content
FunCoding

Search

Search docs, Skills and MCP

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.

文档与办公1.2kAAAI-Skills/skills/aaai-camera-ready/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/brycewang-stanford/awesome-journal-skills/aaai-camera-ready/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

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-27 allocates accepted main-track papers 7 proceedings pages plus up to 2 acknowledgement/reference pages, with an option to purchase up to two additional technical-content pages at $300 each. Camera-ready source files are due 2026-12-14.
  • 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] <PDF/source/bib/figures/supplement>
[Page status] within limit / extra pages needed / over limit
[Publication obligations] copyright / registration / presentation / metadata
[Final fixes] <ordered list before upload>

Similar Skills

pdf
anthropics/skills180k

pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

Docs & office

discernment-nudge
anthropics/skills180k

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

Docs & office

doc-coauthoring
anthropics/skills180k

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Docs & office

docx
anthropics/skills180k

docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

Docs & office

pptx
anthropics/skills180k

pptx

Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.

Docs & office

canvas-design
anthropics/skills180k

canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

Docs & office