sosp-submission
Use when auditing a SOSP submission for HotCRP readiness, covering the abstract-registration and full-paper deadlines, the 12-page technical-content limit with references excluded, the 7x9-inch two-column format, double-blind rules with paper-ID substitution, conflict declaration under PC-chair audit, and desk-reject triage.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-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.
# SOSP Submission Run this audit before anything is uploaded to the SOSP HotCRP instance. Every number below is a 2026-cycle anchor verified on 2026-07-08 against the official CFP and author guidelines at `sigops.org/s/conferences/sosp/2026/` and the `sosp26.hotcrp.com` deadlines page. SOSP re-issues these rules each year; treat the current cycle's pages as controlling and this file as the map of
What does the sosp-submission skill do?
Use when auditing a SOSP submission for HotCRP readiness, covering the abstract-registration and full-paper deadlines, the 12-page technical-content limit with references excluded, the 7x9-inch two-column format, double-blind rules with paper-ID substitution, conflict declaration under PC-chair audit, and desk-reject triage.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-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.