itcs-submission
Use when auditing an ITCS submission for HotCRP readiness — the early-September abstract-then-paper deadlines, single-column >= 11pt format with no hard page limit, the first-10-pages merits window, complete proofs of all central claims, the lightweight double-blind sweep, and the archival-prior-publication check.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-submission --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 Submission Run this audit before uploading to the ITCS HotCRP site. ITCS papers publish **open access in LIPIcs** and are reviewed **lightweight double-blind with no rebuttal**, so the submitted PDF has to be complete, self-defending, and correctly anonymized on the first and only try. Every rule below was read from the ITCS 2026/2025 calls on 2026-07-09 via search renderings of the `itcs2026.hotcrp.com` and `itcs-conf.org` URLs (see [`../../resources/official-source-map.md`](../../resources/official-source-map.md)); treat them as a one-cycle snapshot and reopen the live call first. ## The two-step deadline ITCS separates the **abstract/registration** from the **full-paper submission**, and the abstract cutoff is *earlier*: - **Abstract / registration** locks title, abstract, authors, and conflicts (ITCS 2026: **4 September 2025**, 7:59:59 PM EDT). The abstract drives PC bidding — register the *real* title and abstract, not a placeholder. - **Full-paper submission** uploads the anonymized PDF with complete proofs (ITCS 2026: **6 September 2025**, 7:59:59 PM EDT). Miss the registration and no submission slot exists. ## Format and page policy - **Single column, font size at le
- The two-step deadline
- Format and page policy
- Lightweight double-blind sweep
- Prior-publication and dual-submission check
- Desk-risk triage
- Final-week order of operations
- Reverify each cycle
- Output format
Mechanical pass on the submission PDF pdfinfo paper.pdf | grep -Ei 'author|creator|producer' # scrub metadata identity pdftotext paper.pdf - | grep -nEi 'thank|acknowledg|grant|supported by|our (previous|prior|earlier) (work|paper)' | head pdftotext paper.pdf - | grep -nEi '\\bwe (previously|earlier) (showed|proved)\\b' | head
What does the itcs-submission skill do?
Use when auditing an ITCS submission for HotCRP readiness — the early-September abstract-then-paper deadlines, single-column >= 11pt format with no hard page limit, the first-10-pages merits window, complete proofs of all central claims, the lightweight double-blind sweep, and the archival-prior-publication check.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-submission --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 984 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.