itcs-supplementary
Use when splitting an ITCS paper's content between the body, the appendix, and the arXiv/ECCC/ePrint full version — deciding by what a reviewer must verify, so no central proof lives only in a preprint the PC is not obligated to read, while keeping the first-10-pages merits window clean.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-supplementary --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ITCS Supplementary ITCS gives you three places to put content — the **body**, the **appendix** (part of the submitted PDF), and the **full version** on arXiv/ECCC/ePrint — and the split is governed by one rule: **anything a reviewer must read to judge the paper lives inside the submitted PDF.** Because ITCS has **no hard page limit** and **no rebuttal**, the appendix is generous but load-bearing: you cannot promise "details in the full version" for a proof that decides acceptance, and you cannot answer later if a reviewer cannot follow. This skill decides what goes where. ## The governing principle: decision-criticality Sort every piece of content by whether a reviewer needs it to *decide*: - **Body (first ~10 pages):** everything needed to grasp the contribution and judge its novelty — the model, the motivation, the main theorem statements, proof *ideas*, and the novelty delta. This is the merits window the PC actually reads (see [`itcs-writing-style`](../itcs-writing-style/SKILL.md)). - **Appendix (same PDF):** the **complete proofs** of central claims, full definitions, and any technical development too long for the body. This is *not* optional reading — it is where the "compl
- The governing principle: decision-criticality
- The rule that trips people up
- Use the no-page-limit generously but honestly
- Content-placement table
- Anonymity and the full version
- Output format
What does the itcs-supplementary skill do?
Use when splitting an ITCS paper's content between the body, the appendix, and the arXiv/ECCC/ePrint full version — deciding by what a reviewer must verify, so no central proof lives only in a preprint the PC is not obligated to read, while keeping the first-10-pages merits window clean.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-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.