sosp-artifact-evaluation
Use when preparing a SOSP artifact for the post-acceptance evaluation run by the sysartifacts community, registering within days of notification, packaging for the cooperative review process, and targeting the ACM badges — Artifacts Available, Artifacts Evaluated Functional, and Artifacts Evaluated Reusable.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-artifact-evaluation --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 Artifact Evaluation Use this once a SOSP paper is accepted and the artifact-evaluation (AE) invitation arrives. SOSP's AE is optional, runs **after** acceptance (so it never threatens the paper decision), and is operated through the shared systems-community infrastructure at `sysartifacts.github.io` with its own HotCRP instance (for 2025: `sysartifacts.github.io/sosp2025/`, `sosp25ae.hotcrp.com`; verified 2026-07-08). The CFP describes the clock plainly: a few days after notification to **register** the artifact, then a few more days to polish it before evaluation begins. ## The process is cooperative — plan to be online SOSP AE is explicitly interactive: evaluators report problems, authors fix them during the window, and reasonable response time is an expectation, not a courtesy. The strongest predictor of a failed evaluation is not code quality; it is an author team that treated submission as fire-and-forget during the same weeks the camera-ready and conference logistics were competing for attention. - Name an AE owner who is not the shepherd-thread owner. - Watch the AE HotCRP for evaluator comments daily during the window. - Fixes during evaluation are legitimate; ship t
- The process is cooperative — plan to be online
- Badge targeting
- Packaging for an OS-adjacent artifact
- Kick-the-tires discipline
- What AE cannot do
- Output format
What does the sosp-artifact-evaluation skill do?
Use when preparing a SOSP artifact for the post-acceptance evaluation run by the sysartifacts community, registering within days of notification, packaging for the cooperative review process, and targeting the ACM badges — Artifacts Available, Artifacts Evaluated Functional, and Artifacts Evaluated Reusable.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-artifact-evaluation --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.