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.
Install / Use
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-camera-readyInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
CommunicationSupported Platforms
Our assessment of asplos-camera-ready
asplos-camera-ready scores 90/100 on our quality scale, 235th of 430 Communication skills we index.
Its SKILL.md is 6.5 KB long, well organised into 10 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.
Maintenance, license and trust
- The repository was last updated 21 days ago, so asplos-camera-ready is actively maintained.
- 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.
asplos-camera-ready compared with similar skills
All 4 of these similar skills score higher than asplos-camera-ready; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| asplos-camera-ready (this skill)by brycewang-stanford | 90 | 1.2k | 21d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 92.1k | 20d ago | CLAUDE.md |
| algorithmic-artby anthropics | 100 | 177.9k | 13d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 13d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 130.2k | 15d ago | SKILL.md |
Frequently asked questions
- How do I install asplos-camera-ready?
- Run
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-camera-ready. The install tabs above show the steps for each supported agent. - Which AI agents does asplos-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 asplos-camera-ready safe to use?
- 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 asplos-camera-ready still maintained?
- The repository was last updated 21 days ago, so asplos-camera-ready is actively maintained.
Skill content
View source on GitHubname: asplos-camera-ready description: 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.
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 describes deltas relative to the previous revision, per the CFP's revision-counts-as-submission rule.
De-anonymization, done as a diff
Reversing double-blind is not just adding an author block. Work from the submission-time anonymity sweep, inverting each entry:
- Restore author names, affiliations, and emails in the ACM template's format.
- Convert third-person self-citations back to natural first-person where it reads better — and check none of them still says "the authors of [12]" about yourself.
- Restore acknowledgments and grant numbers; keep the GenAI disclosure placed per ACM policy (immediately before References when in Acknowledgments).
- Re-point anonymized supplemental citations to their real, now-citable targets.
- Replace neutralized infrastructure descriptions with the real testbed identity where confidentiality allows.
# 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
ACM-specific obligations
- The rights form drives the copyright block: complete it early, because the generated rights text must be pasted into the paper before the final build, and DOI/ISBN metadata follows from it.
- Verify title and author-list exact match between the rights form, the PDF, and the submission system — mismatches stall Digital Library ingestion and corrupt citation records for years.
- ASPLOS proceedings publish in the ACM DL in multiple volumes per edition under the multi-cycle model; your cycle determines your volume. Production workflow details (TAPS or classic, camera-ready page allowance) for 2027: å¾…æ ¸å®ž with the acceptance instructions.
Artifact integration
Camera-ready is when artifact evaluation converges with the paper
(asplos-artifact-evaluation):
- The Artifact Appendix is finalized against the actual archived artifact — its dependency list is a promise readers will act on.
- Badges earned (Available / Functional / Reproducible) are attached by the authors or ACM; confirm placement follows the 2027 instructions rather than copying a previous year's badge layout.
- The archival deposit (DOI-issuing repository) must be public before the paper claims it; a dead artifact link in the DL is permanent embarrassment.
Six-week sequence
- Day 0-2: read the decision letter twice; extract every instruction and deadline into a checklist; identify track (accept vs revision).
- Week 1: rights form; template migration; de-anonymization diff.
- Weeks 2-4: shepherd/letter-required edits; final artifact deposit; appendix sync. For revisions: the required experiments, and nothing speculative.
- Week 5: full residue sweep; metadata check; co-author read of the exact PDF.
- Week 6: upload with margin; confirm the system shows the final version; archive the tagged source.
Presentation and registration obligations for 2027 (who must attend Heraklion, April 11-15, 2027; fees; remote options) were å¾…æ ¸å®ž at pack-check time — read the acceptance email's requirements before booking or skipping travel.
Final-build quality gate
Run on the exact PDF going to production, not the working draft:
- Fonts embedded; figures vector where possible; colors legible in grayscale (the DL's print-view and many readers' printers are unforgiving).
- Every cross-reference resolves — a "Figure ??" in the published record is permanent, unlike in a submission.
- The bibliography still satisfies the full-name/DOI rules after camera-ready additions (new "since submission" citations arrive malformed by default).
- Appendix/artifact pointers updated from submission-time wording ("anonymous supplemental material") to their published targets.
- Title capitalization, author ordering, and affiliation strings match what co-authors expect to see indexed — this is the last moment ordering disputes can be resolved quietly.
After publication: the unglamorous checklist
- Verify the DL landing page within days of proceedings release: PDF correct, authors ordered, badges displayed, artifact link resolving. Ingestion errors fixed early are emails; fixed late they are erratum processes.
- Keep the archived artifact's README pointing at the DOI-versioned release, and route post-publication fixes to a new tagged version rather than mutating the evaluated one — the badge attaches to what the committee evaluated.
- Record the edition's ordinal and volume in your own records; ASPLOS's multi-volume-per-edition publishing makes later citation reconstruction error-prone without it.
Output format
[Track] accepted-final / major-revision
[Letter checklist] items: N · addressed: N · pointers recorded: Y/N
[De-anonymization] diff complete · residue sweep clean: Y/N
[ACM forms] rights done · title/author exact-match verified: Y/N
[Artifact] deposit public + DOI minted · appendix synced · badges per instructions
[å¾…æ ¸å®ž] camera-ready date / page allowance / shepherding / attendance rules
Related Skills
Agent-Reach
92.1kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
130.2kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
