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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-writing-style --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.
# 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". 3. The insight: the one idea that unlocks the design. 4. What was built, and the two or three numbers that prove the idea carries. 5. Contributions as verifiable statements, each pointing at a section. A reader who stops after page one should be able to state your insight in a sentence. If the insight sentence does not exist, the problem is the research framing, not the writing (route to `eurosys-topic-selection`). ## Page budget that survives review | Section | Share of 12 pages | Failure mode when misallocated | |---|---|---| | Int
- The load order of a EuroSys introduction
- Page budget that survives review
- Design sections that reviewers can retell
- Evaluation prose discipline
- Sentence surgery
- Revision passes that pay at this venue
- Double-blind voice
- Output format
What does the eurosys-writing-style skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-writing-style --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.