focs-camera-ready
Use when converting a FOCS (IEEE Symposium on Foundations of Computer Science) acceptance into its deliverables — the IEEE proceedings version with copyright and de-anonymization steps, the public arXiv/ECCC full version the CFP expects, the New York talk, and award-eligibility hygiene.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-camera-ready --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# FOCS Camera-Ready Acceptance at FOCS creates two publication duties with different owners of truth: a proceedings version, produced to IEEE specifications and published via IEEE Xplore and the IEEE Computer Society Digital Library, and a public full version with complete proofs that the CFP expects on arXiv, ECCC, or an equivalent open host by the camera-ready deadline (2026 CFP, checked 2026-07-08; the 2026 camera-ready date and format instructions were not public at check time — the acceptance packet is the controlling source, 待核实). This skill sequences both. ## The two deliverables | | Proceedings version | Public full version | |---|---|---| | Publisher | IEEE (Xplore + CS Digital Library) | You (arXiv / ECCC) | | Role | Citable record of the FOCS acceptance | Record of correctness — the document experts actually read | | Length | Per acceptance packet (待核实) | Unlimited; all proofs | | Rights | IEEE copyright/publication form (electronic; exact form 待核实) | You retain arXiv license choice | | Deadline | Camera-ready date (待核实) | CFP expectation: same date | | Failure cost | Paper dropped from proceedings | Community reads a proofless announcement; reputational, and real | Trea
- The two deliverables
- De-anonymization, done completely
- Consistency audit before the deadline
- The November talk and the awards file
- Working with IEEE production
- Endgame sequence
same extractor as focs-reproducibility; both sources, post-edits hashes must match: no theorem statement may differ between the document people cite and the document people check then verify the cross-pointers resolve: grep -o 'arXiv:[0-9v.]*' proceedings-src/*.tex # correct ID, correct version
What does the focs-camera-ready skill do?
Use when converting a FOCS (IEEE Symposium on Foundations of Computer Science) acceptance into its deliverables — the IEEE proceedings version with copyright and de-anonymization steps, the public arXiv/ECCC full version the CFP expects, the New York talk, and award-eligibility hygiene.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-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 984 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.