osdi-topic-selection
Use when deciding whether a systems project fits OSDI, choosing between its Research and Operational Systems tracks, or routing the work to SOSP, NSDI, FAST, EuroSys, or the post-USENIX ATC instead — applying the built-and-measured test before a December deadline is spent on a misfit.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-topic-selection --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 Topic Selection Decide venue months before writing, not days. Everything below reflects the OSDI '26 pages as read on 2026-07-08; the scope paragraph and track structure are re-issued in every CFP, so reopen `usenix.org/conference/osdi<yy>/call-for-papers` before committing a project to the December deadline. ## The built-and-measured test OSDI's identity is in its name: design **and implementation**. Before anything else, answer three questions honestly: 1. **Does the system exist?** Not a simulator of the idea — the artifact itself, runnable under load. A design argued only from simulation or analysis is fighting the venue's instincts. 2. **Has it been measured against something that fights back?** A mature baseline, a production-derived workload, a deployment. Microbenchmarks alone signal a workshop paper. 3. **Is there an idea that survives the implementation?** Name the abstraction, mechanism, or principle a different team could reuse. If the honest answer is "we engineered X to be faster," the contribution is engineering, and OSDI reviewers will say so. Failing question 1 or 2 does not kill the project — it re-times it. Both OS flagships now run annually (OSDI since 20
- The built-and-measured test
- Is it in scope?
- Two tracks, one deadline
- Routing against the sibling venues
- Timing snapshot for the routing decision
- Signals you are about to misfire
- Output format
What does the osdi-topic-selection skill do?
Use when deciding whether a systems project fits OSDI, choosing between its Research and Operational Systems tracks, or routing the work to SOSP, NSDI, FAST, EuroSys, or the post-USENIX ATC instead — applying the built-and-measured test before a December deadline is spent on a misfit.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-topic-selection --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.