Agent skill · Design & Presentation

asplos-camera-ready

Use when converting an ASPLOS acceptance or Major Revision decision into a publishable ACM paper within the six-week window — de-anonymization, ACM rights and template obligations, the revision change note, artifact-appendix integration and badge placement, and Digital Library metadata checks.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-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: 7 KB
Bundled scripts: none
Path: ASPLOS-Skills/skills/asplos-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

# ASPLOS Camera-Ready The camera-ready deadline at ASPLOS 2027 sits roughly **six weeks after notification** — verified indirectly, via the CFP's statement that Major Revisions are resubmitted "at the camera ready deadline (6 weeks from notification)" (checked 2026-07-08; the exact date and page allowance for camera-ready are 待核实 and arrive with the acceptance email). The window is shared by two very different tasks, so the first step is knowing which track you are on. ## Two tracks through the same deadline | Track | What is due | Judged by | |---|---|---| | **Accepted paper** | Final, de-anonymized, ACM-formatted PDF + forms | Publication staff + shepherd if assigned (shepherding for 2027: 待核实) | | **Major Revision** | The *revised submission* — still a reviewed document | The program committee, as a submission on record | Do not apply camera-ready instincts to a Major Revision: it stays within submission rules (anonymity unless told otherwise — confirm in the decision letter), and its companion document is a **change note keyed to the decision letter**, item by item, with pointers to where each required change landed. If this revision follows an earlier revision, the note descri

What's inside
Steps it walks through
  1. Two tracks through the same deadline
  2. De-anonymization, done as a diff
  3. ACM-specific obligations
  4. Artifact integration
  5. Six-week sequence
  6. Final-build quality gate
  7. After publication: the unglamorous checklist
  8. Output format
Commands it runs
residue sweep on the final PDF
pdftotext final.pdf - | grep -niE 'anonym|blind|supplemental material \[|placeholder' | head
pdfinfo final.pdf | grep -iE 'author|creator'   # metadata now SHOULD name you
More from Awesome-Journal-Skills
All skills →
About this skill
What does the asplos-camera-ready skill do?

Use when converting an ASPLOS acceptance or Major Revision decision into a publishable ACM paper within the six-week window — de-anonymization, ACM rights and template obligations, the revision change note, artifact-appendix integration and badge placement, and Digital Library metadata checks.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-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