Convert
remotion-dev/remotion
Start the local @remotion/convert app and open it in the Codex browser.
A skill your agent uses when converting a paper accepted to NAACL Main or Findings into its final ACL Anthology version — merging promised revisions, restoring identity and community…
MITAuto-check passed
Install Naacl Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill naacl-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills naacl-camera-ready --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/NAACL-Skills/skills/naacl-camera-ready .claude/skills/naacl-camera-ready && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "naacl-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NAACL-Skills/skills/naacl-camera-ready into .claude/skills/naacl-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naacl-camera-ready", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NAACL-Skills/skills/naacl-camera-readyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill naacl-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills naacl-camera-ready --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/NAACL-Skills/skills/naacl-camera-ready .agents/skills/naacl-camera-ready && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "naacl-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NAACL-Skills/skills/naacl-camera-ready into .agents/skills/naacl-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naacl-camera-ready", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill naacl-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills naacl-camera-ready --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/NAACL-Skills/skills/naacl-camera-ready .cursor/skills/naacl-camera-ready && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "naacl-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NAACL-Skills/skills/naacl-camera-ready into .cursor/skills/naacl-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naacl-camera-ready", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path NAACL-Skills/skills/naacl-camera-ready--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill naacl-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills naacl-camera-ready --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/NAACL-Skills/skills/naacl-camera-ready .gemini/skills/naacl-camera-ready && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "naacl-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NAACL-Skills/skills/naacl-camera-ready into .gemini/skills/naacl-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naacl-camera-ready", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills naacl-camera-readyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill naacl-camera-ready -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/NAACL-Skills/skills/naacl-camera-ready .github/skills/naacl-camera-ready && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "naacl-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NAACL-Skills/skills/naacl-camera-ready into .github/skills/naacl-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naacl-camera-ready", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill naacl-camera-ready -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills naacl-camera-ready --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/NAACL-Skills/skills/naacl-camera-ready .opencode/skills/naacl-camera-ready && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "naacl-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NAACL-Skills/skills/naacl-camera-ready into .opencode/skills/naacl-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naacl-camera-ready", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
naacl-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 653 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when converting a paper accepted to NAACL Main or Findings into its final ACL Anthology version — merging promised revisions, restoring identity and community…
- Works in 3 steps: The reviewed PDF — the text the… → The promise ledger — every "we will… → De-anonymization — author block,…
- Converting a paper accepted to NAACL Main
- SKILL.md covers The three-source merge, De-anonymization with an…, Metadata: the part search… and Findings-specific handling, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Naacl Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting a paper accepted to NAACL Main or Findings into its final ACL Anthology version — merging promised revisions, restoring identity and community acknowledgements, applying the extra-page allowance, fixing Anthology metadata, and planning presentation logistics for an Americas host city.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Converting a paper accepted to NAACL Main
- Findings into its final ACL Anthology version — merging promised revisions
- Restoring identity and community acknowledgements
- Applying the extra-page allowance
Example prompts
- “/naacl-camera-ready”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- The reviewed PDF — the text the committee actually accepted.
- The promise ledger — every "we will clarify/add/rescope at
- De-anonymization — author block, acknowledgements, funding, real
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Naacl Camera Ready loads about 1.5k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 653 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 653 words, ~1,470 tokens.
Download SKILL.mdSave it as
.claude/skills/naacl-camera-ready/SKILL.md (or your agent's skills folder).- name
- naacl-camera-ready
- description
- Use when converting a paper accepted to NAACL Main or Findings into its final ACL Anthology version — merging promised revisions, restoring identity and community acknowledgements, applying the extra-page allowance, fixing Anthology metadata, and planning presentation logistics for an Americas host city.
NAACL Camera Ready
Acceptance at NAACL produces a permanent object: an open-access paper in the ACL Anthology under the chapter's proceedings (or under Findings of NAACL). The camera-ready phase is where the anonymous ARR artifact, the promises made in your author response, and your public identity get merged into that object. Historical anchor: NAACL 2025 set a single final-version deadline of February 8, 2025 covering both Main and Findings; always reconfirm the current edition's date and instructions.
The three-source merge
Reconstruct the final paper from three inputs, in this order:
- The reviewed PDF — the text the committee actually accepted.
- The promise ledger — every "we will clarify/add/rescope at camera-ready" sentence from your response and the meta-review's requests.
- De-anonymization — author block, acknowledgements, funding, real artifact URLs, and first-person self-citation where it reads better.
Work from a diff against the reviewed version. Silent substantive additions that reviewers never saw are the classic camera-ready foul; the extra page exists to honor the ledger, not to smuggle in a new experiment.
*ACL convention grants accepted papers one additional content page (long papers to 9, short to 5) precisely for integrating reviewer-driven changes — confirm the current edition's instructions rather than assuming.
De-anonymization with an Americas accent
NAACL papers frequently owe debts that anonymization suppressed: language consultants, speaker communities, data-sharing agreements with institutions in Latin America, translation help. Restoring these is not decoration — data-use agreements often require named credit, and omitting it can breach the terms under which a corpus was shared. Sweep for:
- consultant and community acknowledgements tied to specific datasets;
- grant and agency numbers (including non-U.S. funders) in required formats;
- artifact links flipped from anonymized mirrors to the permanent, licensed repository — then click every one from a logged-out session.
Metadata: the part search engines keep forever
| Field | Checked against | Frequent failure |
|---|---|---|
| Title in submission form | Title in the PDF | Casing drift; math or diacritics mangled |
| Author names | Each author's preferred spelling | Accents stripped (García → Garcia) — especially painful at this venue |
| Author order | The accepted submission | Unagreed reordering at the deadline |
| Abstract | Final PDF abstract | Old-cycle abstract pasted in |
| PDF text layer | Copy-paste of the title and quotes | Ligature/encoding damage from a bad toolchain |
The Anthology renders names with full Unicode; the fix for a stripped accent takes one minute now and a correction request months later.
Show full SKILL.md (269 more words)Show less
Findings-specific handling
A Findings acceptance publishes identically (Anthology, open access, citable) but presentation rights differ by edition — some years offer poster slots or workshop presentation matching. Do not guess: read the decision letter, answer the presentation-preference form, and update the paper's own footer or citation guidance to say "Findings of NAACL" so downstream citations land in the right volume.
Logistics checklist for the host city
[ ] Registration completed under the presenting author's name
[ ] Visa/ESTA lead time checked for the host country (US, Mexico,
or elsewhere in the Americas — requirements differ sharply
by author nationality; start immediately at acceptance)
[ ] Presentation format confirmed: oral / poster / Findings slot
[ ] Travel grants: chapter and conference D&I programs have
deadlines separate from camera-ready — check both
[ ] Artifact repository public before the talk, not afterFinal-week failure catalog
Recurring self-inflicted wounds in the last days before the final-version deadline, in descending frequency:
- The promise ledger applied from memory instead of from the actual response text — reviewers notice the one promised clarification that never landed.
- A de-anonymization pass that restores authors but forgets the anonymized
repository placeholder, shipping
anonymous.4open.scienceinto the permanent record. - The extra content page treated as license for a new subsection of results nobody reviewed.
- Acknowledgements added without checking the data agreement's required attribution wording — close is not compliant for partnership credits.
- Rebuilding with the final style switch and never re-reading page breaks, so a table straddles the new author block.
- Uploading a PDF whose embedded title metadata still says "Anonymous ACL submission."
Each of these is a two-minute check now and a proceedings-correction request later; the Anthology does process errata, but a corrected PDF never fully overwrites the copies already downloaded.
Ordered final pass
- Apply the promise ledger; diff against the reviewed PDF.
- Restore identity, acknowledgements, and live artifact links.
- Verify metadata fields and Unicode rendering one by one.
- Rebuild with the final-version style switch; recheck page budget.
- Upload early; keep the confirmation email and the exact final PDF.
Output format
[Merge status] <ledger items applied / deferred / dropped-with-reason>
[Identity restore] <authors, acks, funding, links — done/pending>
[Metadata audit] <field -> ok/fixed>
[Findings handling] n/a / presentation plan
[Logistics] <registration, visa, travel-grant deadlines>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in NAACL-Skills/skills/naacl-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Naacl Camera Ready next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Naacl Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Convertremotion-dev/remotion | 63k | — | ~247 | Automated safety check: Pass | Custom licence | |
| Find Releaseflutter/flutter | 179k | — | ~545 | Automated safety check: Pass | BSD-3-Clause | |
| QA Acceptancepaperclipai/paperclip | 99k | — | ~964 | Automated safety check: Pass | MIT | |
| Fd Findpenpot/penpot | 61k | — | ~882 | Automated safety check: Pass | MPL-2.0 | |
| Acceptance Orchestratorsickn33/agentic-awesome-skills | 47k | 2 repos | ~943 | Automated safety check: Pass | MIT |
Similar skills
- Official
Find Release
flutter/flutter
A skill to find the lowest Dart and Flutter release containing a given commit.
QA Acceptance
paperclipai/paperclip
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
Fd Find
penpot/penpot
A fast and user-friendly alternative to 'find' - simple syntax, smart defaults, respects gitignore.
Acceptance Orchestrator
sickn33/agentic-awesome-skills
A skill your agent uses when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Naacl Camera Ready
What does Naacl Camera Ready do?
A skill your agent uses when converting a paper accepted to NAACL Main or Findings into its final ACL Anthology version — merging promised revisions, restoring identity and community…. Naacl Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting a paper accepted to NAACL Main or Findings into its final ACL Anthology version — merging promised revisions, restoring identity and community acknowledgements, applying the extra-page allowance, fixing Anthology metadata, and planning presentation logistics for an Americas host city.
When should I use Naacl Camera Ready?
Naacl Camera Ready fits situations like: converting a paper accepted to NAACL Main; findings into its final ACL Anthology version — merging promised revisions; restoring identity and community acknowledgements; applying the extra-page allowance.
How do I install Naacl Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill naacl-camera-ready -a claude-code`. Or copy the skill folder (NAACL-Skills/skills/naacl-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/naacl-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Naacl Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill naacl-camera-ready -a codex`. Or copy the skill folder (NAACL-Skills/skills/naacl-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/naacl-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Naacl Camera Ready in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill naacl-camera-ready -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/naacl-camera-ready, .gemini/skills/naacl-camera-ready, .github/skills/naacl-camera-ready and .opencode/skills/naacl-camera-ready in your project.
What does Naacl Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Naacl Camera Ready is instructions for the agent only.
Does Naacl Camera Ready access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Naacl Camera Ready safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Naacl Camera Ready use?
Naacl Camera Ready is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Naacl Camera Ready use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Naacl Camera Ready?
Skills that share tags, products or a category with Naacl Camera Ready: Convert (remotion-dev/remotion, 63k stars), Find Release (flutter/flutter, 179k stars), QA Acceptance (paperclipai/paperclip, 99k stars) and Fd Find (penpot/penpot, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Naacl Camera Ready?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.