Agent skill · Code Review & Quality

corl-camera-ready

Use when converting an accepted CoRL paper into its final form — the 9-page camera-ready main text with the extra page for review feedback, the final-mode corl LaTeX template, appendix merged into one PDF, de-anonymization, external hosting for videos because PMLR accepts none, and the October deadline into the PMLR volume.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill corl-camera-ready --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: CoRL-Skills/skills/corl-camera-ready/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# CoRL Camera-Ready Acceptance converts the paper from a review object into a permanent PMLR record — alongside, at CoRL, the *public release of its reviews and rebuttal*. The camera-ready pass is therefore three jobs: absorb what the review process demanded, de-anonymize cleanly, and stand up the external artifact surface that the proceedings pipeline cannot host. The 2026 rules below were read from corl.org author instructions on 2026-07-08; the deadline was October 12, 2026, 23:59 AoE. ## What changes at camera-ready (2026 cycle) | Dimension | Submission | Camera-ready | |---|---|---| | Main-text pages | 8 (Limitations included) | **9** — the added page exists to accommodate review feedback | | Template mode | anonymous review mode | `\usepackage[final]{corl_2026}` | | Identity | double-anonymous | authors, affiliations, acknowledgments restored | | Appendix | same PDF, optional | included at the **end of the camera-ready PDF**, not a separate file | | Video | supplementary upload (≤ 250 MB) | **not accepted by PMLR** — host externally, link from the main text / project page | | Audience | reviewers + AC | permanent open-access record, reviews attached | ## Spend the ninth page

What's inside
Steps it walks through
  1. What changes at camera-ready (2026 cycle)
  2. Spend the ninth page on the reviewers' record
  3. De-anonymization sweep
  4. The external artifact surface (the PMLR no-video rule)
  5. PMLR metadata discipline
  6. Registration, presentation, and the November venue
  7. Exit checklist
Commands it runs
Final-PDF gate, run on the actual upload candidate
grep -c 'usepackage\[final\]{corl_2026}' main.tex          # exactly 1
pdftotext final.pdf - | head -40                            # author block present & correct
pdftotext final.pdf - | grep -nEi 'anonym|under review|paper #' # expect no hits
pdfinfo final.pdf | grep -i pages                           # 9pp body + refs + appendix merged
pdftotext final.pdf - | grep -oE 'https?://[^ ]+' | sort -u # every URL: live, permanent, deliberate
More from Awesome-Journal-Skills
All skills →
About this skill
What does the corl-camera-ready skill do?

Use when converting an accepted CoRL paper into its final form — the 9-page camera-ready main text with the extra page for review feedback, the final-mode corl LaTeX template, appendix merged into one PDF, de-anonymization, external hosting for videos because PMLR accepts none, and the October deadline into the PMLR volume.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill corl-camera-ready --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going