Individual skill

eurosys-writing-style

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.

EuroSys-Skills/skills/eurosys-writing-style/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# EuroSys Writing Style

Use this on the manuscript itself. A EuroSys paper succeeds when a broad
systems PC — kernel people, distributed-systems people, cloud and security
people — can each extract the same mechanism and believe the same numbers
within one reading. The two-column `acmart[sigplan]` format and the 12-page
technical budget (EuroSys 2027 CFP, rendered 2026-07-08) reward density that
stays legible, not compression that hides.

## The load order of a EuroSys introduction

1. The operational pain, stated concretely enough to measure.
2. Why the existing abstraction or mechanism structurally cannot fix it —
   named systems, not "prior approaches".
Back to top