Individual skill

podc-writing-style

Use when drafting or revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box, the result stated as a theorem up front, a proof architecture the reader can navigate, and the 10-page-merits discipline) so the merits case lands within the first 10 pages a PODC committee is guaranteed to read.

PODC-Skills/skills/podc-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

# PODC Writing Style

Write for a reader who will check your proof. A PODC paper is a **mathematical argument** about a
**distributed model**, and the committee decides on the **first 10 pages after the title page** (the
merits budget). The house style is therefore front-loaded: fix the model, state the result, then
prove it — with the proof organized so a reviewer can find and verify each step.

## The first-page arc

Lead with the result inside its model, in this order (see the worked example in
`resources/worked-examples/01-introduction.md`):

1. **The problem inside a fixed model** — network (message-passing / shared memory), timing
   (synchronous / asynchronous / partial synchrony), fault model (crash / Byzantine /
Back to top