socc-writing-style
Use when revising an ACM SoCC paper for a cloud-scale problem an operator recognizes on the first page, a contribution at the systems-and-data intersection, evidence measured on a real or realistic deployment with tail latency and cost as first-class, dual-anonymous wording, and disciplined use of the acmart 12-page budget.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-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.
# SoCC Writing Style Use this when revising the main paper. SoCC papers are read by a joint **SIGMOD+SIGOPS** audience, so they need a **cloud-scale problem stated in operator terms on the first page** and evidence a skeptic from *either* community trusts. The failure this skill prevents is a paper that reads like a pure-OS result with a cloud title glued on, or a benchmark with no systems contribution. ## Revision rules - **Lead with the cloud problem, in cost and tail terms:** the problem an operator or platform team recognizes, why current systems are inadequate *at scale*, the contribution (mechanism and/or measurement), the measured evidence, and what changes for cloud practice. - **Situate the contribution at the systems-and-data intersection.** Say explicitly what is new: a mechanism, a measurement, a benchmark, a deployment lesson, or a cost model. SoCC's twin communities both want to see themselves in the paper. - **Make tail latency and cost first-class.** Report p95/p99 (and p99.9 where it bites) and a concrete cost model, not just averages. A cloud paper that reports only the mean signals it has not been stress-tested the way an operator would. - **Pair every claim with
- Revision rules
- Cloud-systems paper skeleton
- Sentence-level rewrites
- Tail-and-cost discipline
- Vignette: compressing an over-scoped systems paper
- Output format
What does the socc-writing-style skill do?
Use when revising an ACM SoCC paper for a cloud-scale problem an operator recognizes on the first page, a contribution at the systems-and-data intersection, evidence measured on a real or realistic deployment with tail latency and cost as first-class, dual-anonymous wording, and disciplined use of the acmart 12-page budget.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-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.