usenixsec-workflow
Use when planning a USENIX Security Symposium project end to end — choosing between the two annual cycles, mapping the registration-to-camera-ready calendar for a chosen cycle, sequencing artifact and ethics work early, and coordinating a team across the multi-deadline Big-Four calendar.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-workflow --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 Workflow USENIX Security runs two independent submission cycles per year, so "when do we submit?" is a real strategic choice, not a fixed date. This skill turns a target cycle into a dated backward plan and assigns owners to the venue-specific risks. Dates below are the '26/'27 cycle values read on 2026-07-08 (via search renderings; usenix.org direct fetch 403'd) — reconfirm against the live CFP. ## Step 1: pick the cycle | Consideration | Favors the earlier cycle | Favors the later cycle | |---|---|---| | Readiness | Evaluation truly done now | Needs one more experiment done right | | Conference lead time | Cycle-1 accepts publish ~7 months pre-symposium | Cycle-2 accepts closer to the event | | Competing deadlines | Avoids clashing with a CCS/S&P/NDSS date | Room to route a reject to the next venue | | Resubmission runway | Reject still leaves the same-year second cycle open* | Reject pushes to next year | \*Subject to the cycle's resubmission-restriction text — the '26 CFP delegated Cycle-2 reject restrictions to the '27 chairs, so verify before assuming a reject can re-enter (see `usenixsec-review-process`). Reference calendar (verify per cycle): | Milestone |
- Step 1: pick the cycle
- Step 2: backward-plan from the registration date
- Step 3: assign the venue-specific risks
- Step 4: run the post-submission and post-decision phases
- Coordinating across the Big-Four calendar
- Reverify each cycle
- Output format
What does the usenixsec-workflow skill do?
Use when planning a USENIX Security Symposium project end to end — choosing between the two annual cycles, mapping the registration-to-camera-ready calendar for a chosen cycle, sequencing artifact and ethics work early, and coordinating a team across the multi-deadline Big-Four calendar.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-workflow --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.