SkillAgentSearch skills...

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, meta-review-driven edits, and pr…

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill acl-camera-ready

Installs into whichever agent you are using.

About this skill
πŸ“„

SKILL.md

Installable skill definition

Quality Score

90/100

Supported Platforms

Universal

Our assessment of acl-camera-ready

acl-camera-ready scores 90/100 on our quality scale, 1405th of 4,702 Development & Engineering skills we index (top 30%).

Its SKILL.md is 6.2 KB long, well organised into 11 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.

With 1,158 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so acl-camera-ready is actively maintained.
  • Our last check on 2026-10-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β€” read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk β€” read a skill before letting an agent act on it.

acl-camera-ready compared with similar skills

All 4 of these similar skills score higher than acl-camera-ready; compare them before choosing.

SkillScoreStarsUpdatedFormat
acl-camera-ready (this skill)by brycewang-stanford901.2k2mo agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
lobehubby lobehub10085.7ktodayMCP Server

Frequently asked questions

How do I install acl-camera-ready?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill acl-camera-ready. The install tabs above show the steps for each supported agent.
Which AI agents does acl-camera-ready work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is acl-camera-ready safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is acl-camera-ready still maintained?
The repository was last updated about 2 months ago, so acl-camera-ready is actively maintained.

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 the deadline hour forfeits the retry.

Output format

[Camera-ready status] Ready / Needs fixes / Blocked
[Meta-review edits] <requested change -> edit made>
[Extra-page budget] <what the added space was spent on>
[De-anonymization + disclosure] <authors/acks/AI-use/links status>
[Anthology package] <PDF/metadata/license/artifact links>

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryDevelopment
Updated2mo ago
Forks153

Languages

Stata

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit β€” see the Safety scan above for what the skill file itself contains.

No cautions
acl-camera-ready β€” Universal Skill: Install & Safety Check | SkillAgent