Skip to content
Content
Skill

/acl-camera-ready

Use when preparing an accepted ACL main-conference or Findings paper for camera-ready, covering the extra content page, de-anonymization and acknowledgements, AI-assistance disclosure, keeping the Limitations section, ACL Anthology metadata and CC BY 4.0 publication,

From plugin
awesome-journal-skills
965200 skills
Install
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill acl-camera-ready --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/acl-camera-ready

Context preview

The summary Claude sees to decide when to auto-load this skill.

Use when preparing an accepted ACL main-conference or Findings paper for camera-ready, covering the extra content page, de-anonymization and acknowledgements, AI-assistance disclosure, keeping the Limitations section, ACL Anthology metadata and CC BY 4.0 publication,

SKILL.md

acl-camera-ready.SKILL.md
name: acl-camera-ready
description: Use when preparing an accepted ACL main-conference or Findings paper for camera-ready, covering the extra content page, de-anonymization and acknowledgements, AI-assistance disclosure, keeping the Limitations section, ACL Anthology metadata and CC BY 4.0 publication, meta-review-driven edits, and presentation-mode logistics.

ACL Camera Ready

Use this after ACL (or Findings of ACL) acceptance. Camera-ready quality controls how the paper looks forever in the ACL Anthology, which is the permanent open-access record. For ACL 2026 the camera-ready deadline was April 19, 2026 — confirm the current edition's date in the acceptance email before planning anything.

The extra page and what it is for

  • Accepted \*ACL papers traditionally receive one additional content page:

long papers up to 9 pages, short papers up to 5. The page exists to address reviewer and meta-review comments, not to smuggle in a new contribution.

  • Spend it in priority order: fixes the meta-review asked for, clarifications

reviewers requested, then de-anonymization overhead (author block, acknowledgements) which consumes real space.

  • References remain unlimited; the Limitations section remains **mandatory**

in the camera-ready and still sits outside the page count.

De-anonymization pass

  • Restore authors, affiliations, and acknowledgements; convert third-person

self-citations ("Smith showed") back to natural first person where clearer.

  • Replace anonymous supplement links with the permanent public repository,

dataset page, or model card; test every URL logged out.

  • Add the funding and AI-assistance acknowledgements: ACL policy requires

generative-AI use beyond polishing to be disclosed, with details in the Acknowledgements matching your Responsible NLP checklist answers.

Anthology-facing metadata

| Item | Why it matters at ACL | Common error | |---|---|---| | Title/abstract in the form | Becomes the Anthology landing page | Unicode or LaTeX macros pasted raw | | Author names + order | Permanent citation record, BibTeX for everyone | Name spelled differently than prior papers | | PDF fonts embedded | Anthology archival requirement | Missing Type-1/TrueType embedding from figures | | License acceptance | Anthology publishes under CC BY 4.0 (post-2016 policy) | Assuming you can restrict reuse later | | Video/poster uploads | Linked from the Anthology page when provided | Skipped, losing visibility |

Publication in the Anthology is open access with no author fee; ACL's cost model is conference registration, not APCs.

Integrating reviewer-mandated changes

Work from the meta-review, not memory:

1. Extract every "should," "must," and "the authors agreed to" from the meta-review and discussion thread into a checklist. 2. Map each to an edit: new sentence, moved table, scoped claim, added citation. The accepted contribution must not silently grow — a stronger claim than reviewers evaluated is an integrity problem, not a bonus. 3. Keep section and table numbering stable where possible so the review record still points at the right objects. 4. Re-run the checklist consistency pass: if you promised error bars or a contamination note in discussion, the camera-ready must contain it.

Main conference vs Findings logistics

  • Findings papers are full peer-reviewed publications in the Anthology but are

typically not part of the main oral program; presentation options (Findings poster sessions, workshop presentation slots, videos) vary per edition — check the current conference's Findings instructions rather than assuming.

  • Registration and presentation expectations differ by track and edition; ACL

2026 ran as a hybrid conference in San Diego (July 2-7, 2026). Verify the current attendance requirement before booking or skipping travel.

Camera-ready week runbook

Day 1: meta-review edit checklist; claim-scope audit
Day 2: de-anonymize; acknowledgements incl. funding + AI disclosure
Day 3: public artifact links live; README + license on the repo
Day 4: rebuild with final style; font embedding + page-count check
Day 5: metadata form; abstract matches PDF; submit and archive everything

Common camera-ready rejections and rework requests

  • Unembedded fonts from matplotlib or Inkscape figures — regenerate with

embedding forced rather than patching the PDF.

  • Title case mismatch between the form and the PDF, or LaTeX math left in

the plain-text abstract field.

  • Author list drift: an author added or reordered after review needs chair

approval, not a silent metadata edit.

  • Limitations section deleted "for space" — it is still required and still

free; removing it can bounce the paper at publication checks.

  • Non-resolving artifact URLs: the Anthology page will outlive your lab

server; prefer archived, versioned hosting for the link of record.

If the paper landed in Findings

  • The Anthology volume is "Findings of the Association for Computational

Linguistics: ACL <year>" — cite and list it that way; miscrediting your own venue tier propagates into others' bibliographies.

  • Camera-ready mechanics are the same as main-conference papers, extra page

included; deadlines are usually shared — confirm in the decision letter.

  • Ask early which presentation options the edition offers Findings papers

(poster session, affiliated workshop slot, video); slots can require separate sign-up shortly after notification.

Presentation assets riding the same deadline window

  • Poster/slide templates, video-upload requirements, and session-format

details arrive with or shortly after camera-ready instructions; the video deadline is often earlier than authors expect.

  • Registration typically must be completed by a named author before the

paper is scheduled — check the decision email for the binding rule.

  • Book the error budget: font, metadata, and form rejections bounce back

days later, so submitting on

Read more
Ships withawesome-journal-skills

Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证

Get the whole plugin
Stats
965
Stars
121
Forks
Active
Maintenance
Stata
Language
MIT
License
14h ago
Last commit
2mo ago
Created

Repo: brycewang-stanford/Awesome-Journal-Skills

Other skills on awesome-journal-skills.