usenixsec-camera-ready
Use when preparing final papers for the USENIX Security Symposium after acceptance — de-anonymizing, keeping the Ethical Considerations and Open Science appendices current, clearing the mandatory Phase-1 artifact availability check before finals are due, and meeting USENIX's open-access publication and presentation obligations.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-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.
# USENIX Security Camera-Ready Acceptance at USENIX Security starts a short, condition-laden runway: in the '26 cycles, final papers were due about six weeks after notification (Cycle 1: notified Dec 4, 2025, finals Jan 15, 2026; Cycle 2: notified May 14, 2026, finals Jun 11, 2026), and during that same window the **mandatory artifact-availability check had to pass**. The camera-ready is therefore not a formatting chore — part of the acceptance itself is still pending. ## What is actually conditional Under the '26 Open Science policy, acceptance is conditional on the artifact evaluation committee verifying, before finals are due, that the artifacts named in the paper's Open Science appendix are genuinely available — or that the appendix carries a justified explanation for withholding them. Plan the runway backwards from that: | Week after notification | Camera-ready lane | Artifact lane | |---|---|---| | 1 | Ingest decision + shepherd requests | Move artifacts from anonymous mirror to permanent home | | 2–3 | Apply required edits; shepherd sign-off | Submit availability materials; respond to AE contact | | 4 | De-anonymize; final template pass | Availability verified (Phase-1 compl
- What is actually conditional
- De-anonymization done in the right order
- Mechanical pass before upload
- Publication model: open access, no author fee
- Badge and visibility follow-through
- Reverify each cycle
- Output format
Final-paper checks
pdftotext final.pdf - | grep -nEi 'anonym|under submission|double.blind' | head
pdftotext final.pdf - | grep -noE 'https?://[^ ]+' | sort -u > urls.txt
while read -r n url; do curl -sIL --max-time 10 "${url#*:}" -o /dev/null \
pdffonts final.pdf | awk 'NR>2 && $4!="yes"' # any non-embedded font lines = fixWhat does the usenixsec-camera-ready skill do?
Use when preparing final papers for the USENIX Security Symposium after acceptance — de-anonymizing, keeping the Ethical Considerations and Open Science appendices current, clearing the mandatory Phase-1 artifact availability check before finals are due, and meeting USENIX's open-access publication and presentation obligations.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-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.