EuroSys Skills

A 12-skill depth pack for EuroSys submissions: venue fit, the dual spring/fall deadline calendar, HotCRP submission checks, rebuttal and one-shot revision strategy, ACM camera-ready, sysartifacts artifact evaluation with badges, reproducibility, writing style, related work, experiments, and workflow. Grounded in the EuroSys 2027 CFP, HotCRP sites, sysartifacts pages, and eurosys.org, checked on 20

by @brycewang-stanford 12 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/eurosys-skills

One command, no setup. In Claude Code it lands as a managed plugin you can enable, disable or remove with /plugin. On any other agent it installs the 12 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-eurosys-skills@skillmd

Adds the marketplace once; later plugins need the second line only.

Or install by hand

Download the plugin and unzip its skills/ folder into your agent's skills directory. Works with every agent, no CLI needed.

Download plugin Paths per agent

Just the markdown? SKILL.md files only.

This plugin

skills: 12
authors: 1

Published by a registry member. Review its skills before installing.

Skills in this plugin

▌
Eurosys Workflow · brycewang-stanford
Use when planning a EuroSys campaign end to end — choosing between the spring and fall gates of an edition, backward-scheduling system building and evaluation from the abstract deadline, handling the notification-to-revision-to-resubmission pipeline, and landing camera-ready, artifacts, and April travel for the conference.

1k repo stars
▌
Eurosys Submission · brycewang-stanford
Use when auditing a EuroSys submission before a HotCRP upload — abstract registration versus full-paper gates, the 12-page technical-content budget with free references, the acmart sigplan review/anonymous template and text block, double-blind hygiene, and the CFP warning that formatting or anonymization violations are not reviewed.

1k repo stars
▌
Eurosys Experiments · brycewang-stanford
Use when designing or auditing the evaluation of a EuroSys paper — choosing workloads that earn the word realistic, tuning baselines beyond their defaults, decomposing end-to-end wins into per-mechanism gains, measuring overheads and worst cases, and sizing experiments to the claims the paper actually makes.

1k repo stars
▌
Eurosys Camera Ready · brycewang-stanford
Use when converting an accepted EuroSys paper into its ACM proceedings version — flipping acmart out of review/anonymous mode, restoring authors and acknowledgments, completing ACM rights and metadata steps, attaching sysartifacts badges, and meeting the single camera-ready date that serves both the spring and fall cohorts.

1k repo stars
▌
Eurosys Related Work · brycewang-stanford
Use when positioning a EuroSys submission in the systems literature — mapping the SOSP/OSDI/NSDI/ATC/ASPLOS neighbor space plus EuroSys's own two-decade proceedings line, handling concurrent arXiv and workshop versions under double-blind rules, and declaring overlap with earlier submissions of the same work.

1k repo stars
▌
Eurosys Supplementary · brycewang-stanford
Use when deciding what lives outside a EuroSys paper's 12 technical pages — free reference pages, whether the current round permits appendices or supplementary uploads, anonymized artifact repositories linked from the submission, and extended technical reports — without moving decision-critical evidence out of the reviewed pages.

1k repo stars
▌
Eurosys Writing Style · brycewang-stanford
Use when drafting or revising EuroSys prose — building the problem-to-mechanism arc systems reviewers expect, budgeting the 12 technical pages across design and evaluation, writing figure-first evaluation sections, keeping claims measurement-scoped, and maintaining double-blind voice in the acmart sigplan format.

1k repo stars
▌
Eurosys Review Process · brycewang-stanford
Use when reasoning about how EuroSys decides papers — the two independent yearly rounds feeding one April conference, HotCRP double-blind reviewing, the accept/revise/reject outcome triple, the same-season resubmission ban after rejection, and community structures like the Shadow PC that shape who reviews.

1k repo stars
▌
Eurosys Author Response · brycewang-stanford
Use when writing a EuroSys rebuttal or managing a one-shot revision — reading reviews against the three possible outcomes (accept, revise, reject), answering systems reviewers' measurement and design objections, and turning a revision offer's condition list into a resubmission plan for the next EuroSys deadline.

1k repo stars
▌
Eurosys Reproducibility · brycewang-stanford
Use when hardening the reproducibility story of a EuroSys paper — recording hardware and software provenance for every number, taming performance variance with repeated runs and dispersion reporting, versioning workloads and traces, and writing an availability statement that survives both double-blind review and the sysartifacts AEC.

1k repo stars
▌
Eurosys Topic Selection · brycewang-stanford
Use when deciding whether a systems project belongs at EuroSys — the ACM SIGOPS-Europe flagship spanning OS, distributed systems, storage, cloud, virtualization, security, and ML systems — or routes better to SOSP, OSDI, NSDI, ASPLOS, ATC, FAST, or SoCC, and how the April slot and dual deadlines affect that call.

1k repo stars
▌
Eurosys Artifact Evaluation · brycewang-stanford
Use when preparing a EuroSys artifact for the sysartifacts-run evaluation — choosing among the Available, Functional, and Reproduced badges, timing the post-notification artifact submission, building for an evaluator on foreign hardware, and aiming at the Gilles Muller Best Artifact Award rather than a minimal pass.

1k repo stars