Individual skill
sosp-writing-style
Use when drafting or revising SOSP prose — leading with a design principle rather than a feature list, building the intro's problem-to-insight arc, budgeting 12 dense two-column pages across design and evaluation, writing figures that argue, and keeping claims inside what the measurements support.
SOSP-Skills/skills/sosp-writing-style/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- 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,409
- 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
- writing 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
# SOSP Writing Style
Use this at drafting and revision time for a SOSP paper. The format constants (2026
cycle, checked 2026-07-08 against the official author guidelines): at most 12 pages
of technical content in submission, 10-point font on 12-point leading, a 7 x 9 inch
text block in two columns, references uncounted. Those pages are read first by a
skeptical fast pass and later defended live at a PC meeting — the prose must arm an
advocate, not just inform a reader.
## Lead with the principle, not the artifact
The recurring identity question at this venue is "what is the *principle*?" A SOSP
paper is remembered as an idea with a system attached, not a system with features
attached. Concretely: