sosp-review-process
Use when reasoning about how a SOSP submission is evaluated — double-blind HotCRP reviewing, staged review rounds, PC-chair-audited conflicts, the pre-PC-meeting author response, the single-track PC meeting where every decision is argued live, notification, and shepherded acceptance outcomes.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-review-process --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.
# SOSP Review Process Use this to model what happens to a SOSP paper between the April upload and the July decision, and to time author-side actions to the phases that actually move outcomes. Anchors below are from the 2026-cycle CFP and the `sosp26.hotcrp.com` schedule (checked 2026-07-08): submission April 2026, author response ahead of the PC meeting, notification **July 3, 2026**. ## The pipeline | Phase | Who acts | What authors can do | |---|---|---| | Conflict screening (from abstract registration) | PC chairs audit declared conflicts, add or **remove** entries | Declare defensibly; chairs treat strategic conflicts as misconduct-adjacent | | Early reviewing | A subset of the PC reads every paper | Nothing — the paper speaks alone | | Later-round reviewing | Papers still alive draw additional, often more senior, reviews | Nothing; round structure and counts vary by year (待核实 per cycle) | | Author response | Authors correct factual errors, answer posed questions | The one sanctioned intervention (see `sosp-author-response`) | | PC meeting | Full committee discusses candidates live, single track | Nothing — but the response was written for this room | | Decision + shepherd assi
- The pipeline
- Reading SOSP reviews
- Confidentiality and integrity edges
- Calibrating expectations
- Output format
What does the sosp-review-process skill do?
Use when reasoning about how a SOSP submission is evaluated — double-blind HotCRP reviewing, staged review rounds, PC-chair-audited conflicts, the pre-PC-meeting author response, the single-track PC meeting where every decision is argued live, notification, and shepherded acceptance outcomes.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-review-process --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.