osdi-submission
Use when running the final pre-upload audit of an OSDI submission on HotCRP — the December registration and full-paper deadlines at 2:59 pm PST, the 12-page/no-appendix check, institution-level double-blind rules, the renamed-system requirement, track choice, and the eight-submission author cap.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-submission --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.
# OSDI Submission Run this audit before touching the HotCRP upload form. Every rule below is the OSDI '26 cycle as read on 2026-07-08 (`osdi26.usenix.hotcrp.com` plus the CFP); treat the numbers as one year's snapshot and reopen the current CFP before acting. ## The two December gates, in Pacific time OSDI '26 split the deadline in two, and both were **2:59 pm PST** — USENIX's local afternoon convention, not AoE midnight: - **Registration (Dec 4, 2025):** title, abstract, authors, and **track** (Research or Operational Systems) created in HotCRP. Unregistered papers cannot be submitted a week later, full stop. - **Full submission (Dec 11, 2025):** the final anonymized PDF uploaded and marked complete. HotCRP "complete" status is the state that counts — a draft sitting in the form is not a submission. Convert 2:59 pm PST to every coauthor's time zone in writing. It is 10:59 pm in London, 6:59 am *the next day* in Beijing — the single most common OSDI logistics error is an AoE reflex from ML venues. ## Format gate (rejection-grade) | Check | OSDI '26 rule | |---|---| | Body length | ≤ 12 pages, single-spaced, **including figures and tables** | | References | Unlimited extra pages | |
- The two December gates, in Pacific time
- Format gate (rejection-grade)
- Anonymity gate: OSDI's two distinctive rules
- Policy gate
- HotCRP field hygiene
- Why this audit is terminal at OSDI
- Final sequence
- Output format
Mechanical sweep on the exact PDF you will upload pdftotext paper.pdf - | grep -nEi 'OLDNAME|github\.com|gitlab|acknowledg|grant' | head pdfinfo paper.pdf | grep -Ei 'author|creator|producer' # metadata identity pdffonts paper.pdf | head # embedded, expected fonts figures often embed usernames in paths: check figure sources too grep -rnEi 'home/|Users/|OLDNAME' figures/ *.tex | head
What does the osdi-submission skill do?
Use when running the final pre-upload audit of an OSDI submission on HotCRP — the December registration and full-paper deadlines at 2:59 pm PST, the 12-page/no-appendix check, institution-level double-blind rules, the renamed-system requirement, track choice, and the eight-submission author cap.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-submission --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.