icalp-related-work
Use when writing the related-work and positioning of an ICALP (EATCS) theory paper — comparing against the best known bounds in the TCS literature, crediting the right prior venues (STOC/FOCS/SODA/LICS/CCC and TCS journals), stating the delta precisely, and keeping self-citations third-person under lightweight double-blind.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icalp-related-work --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.
# ICALP Related Work At ICALP, related work is where you prove your result is **new and better**, not where you list adjacent papers. A theory referee arrives already knowing the best bound for your problem; your job is to state **exactly how your result compares** and to credit the lineage correctly. Vague or missing positioning is a top rejection cause even for correct proofs. ## The comparison is the point - Name the **best known prior bound** for your exact problem and setting, and state your improvement in the same sentence. "Prior work achieved X under assumption A; we achieve Y, removing A" is the contract. - If your result is **incomparable** to prior work (different regime, different parameter), say so explicitly and give the reader the axis of comparison — do not let them assume you missed a stronger result. - Distinguish **unconditional** from **conditional** results (and which assumption: SETH, 3SUM, APSP, etc.). A conditional lower bound compared against an unconditional one is a category error referees catch instantly. ## Cover the right literature lanes For a Track A paper, the lanes are typically: the **algorithmic** line (best upper bounds), the **hardness** line (
- The comparison is the point
- Cover the right literature lanes
- Credit the right venues
- Lightweight double-blind self-citation
- Positioning patterns that work
- Anti-patterns
- Output format
What does the icalp-related-work skill do?
Use when writing the related-work and positioning of an ICALP (EATCS) theory paper — comparing against the best known bounds in the TCS literature, crediting the right prior venues (STOC/FOCS/SODA/LICS/CCC and TCS journals), stating the delta precisely, and keeping self-citations third-person under lightweight double-blind.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icalp-related-work --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.