Individual skill

icalp-writing-style

Use when shaping the exposition of an ICALP (EATCS) theory paper — stating the model before the theorem, putting a legible theorem statement and its improvement over prior bounds on the first page, structuring the 15-page body around the argument while full proofs live in the appendix/full version, and meeting the correctness-and-clarity bar of Track A and Track B referees.

ICALP-Skills/skills/icalp-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,400
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

# ICALP Writing Style

Build the ICALP skeleton: **model → theorem → improvement → technique → complete proof**. ICALP
referees are subject experts who will *check* the mathematics, so the writing has two jobs at once —
make the contribution **legible on the first page**, and make the proofs **verifiable** in the body,
appendix, and full version. The 15-page body is a hard budget; exposition, not omission, is how you
fit.

## The first-page arc

1. **State the model, then the theorem.** Fix the exact setting — the computational model, the
   complexity measure, the class of objects — *before* the claim. "Fully dynamic, deterministic,
   worst-case update time" comes before "n^{o(1)}."
2. **Put a legible theorem statement in the abstract.** A specialist should read the abstract and know
Back to top