Agent skill · Code Review & Quality

icalp-supplementary

Use when splitting an ICALP (EATCS) theory paper between the 15-page main body and the clearly labelled appendix / full version — deciding what a referee must see in the body versus what may be deferred, ensuring every deferred proof is actually present and findable, and keeping the split consistent with lightweight double-blind review.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icalp-supplementary --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: ICALP-Skills/skills/icalp-supplementary/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# ICALP Supplementary (the body / appendix / full-version split) ICALP gives you a **15-page body** (excluding references and a clearly labelled appendix) plus an appendix that may hold omitted proofs or a **full version**, read **at the program committee's discretion**. The whole game is deciding **what goes where**: the body must let a referee *judge and follow* the paper; the appendix must let them *verify* it. Getting this split wrong — either cramming proofs into the body or hiding the substance in an unread appendix — is a common, avoidable weakness. ## The governing principle > The body earns the referee's belief; the appendix earns their verification. - The **body** contains the model, the theorem statements, the main ideas, the key lemmas, and enough of the central proof that a referee can see **why it is true** and **that it is nontrivial**. - The **appendix / full version** contains the **complete proofs**, routine cases, and technical details a referee consults to confirm correctness. - "At the PC's discretion" means the appendix is **not guaranteed** to be read — so nothing whose *significance* the referee must weigh may live only there. ## What must be in the body - T

What's inside
Steps it walks through
  1. The governing principle
  2. What must be in the body
  3. What may be deferred to the appendix / full version
  4. The two failure modes
  5. Completeness and findability
  6. Double-blind consistency
  7. Worked split: a two-theorem paper
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the icalp-supplementary skill do?

Use when splitting an ICALP (EATCS) theory paper between the 15-page main body and the clearly labelled appendix / full version — deciding what a referee must see in the body versus what may be deferred, ensuring every deferred proof is actually present and findable, and keeping the split consistent with lightweight double-blind review.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icalp-supplementary --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.

Keep going