Individual skill
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.
SoCC-Skills/skills/socc-writing-style/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- 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,404
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- finance Derived category
- writing Derived category
- data Derived category
- devops Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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