Browse reusable Agent Skills, each with a clear purpose and practical guidance.
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.
Use when preparing an accepted ICASSP paper for IEEE Xplore publication, covering the final 4+1 PDF, IEEE PDF eXpress validation, the IEEE electronic copyright form, integrating reviewer-requested fixes without changing the accepted claim, registration and in-person presentation, and choosing open-access options for the proceedings paper.
Use when revising an ICASSP paper into the IEEE two-column four-page house style — leading with the signal-processing contribution and mechanism, naming the task-matched metric on the first page, compressing method and results into 4+1 pages without a reviewed appendix, and writing math-forward claims that survive a subfield-expert reviewer.
Use when auditing an ICDM (IEEE International Conference on Data Mining) submission for readiness, covering Research-vs-Applied track choice and its anonymity regime, the triple-blind sweep, the 10-page IEEE all-inclusive cap, the single June deadline, in-paper artifact references, and the desk-level triggers that get an ICDM paper rejected without review.
Use when organizing supplementary and appendix material for an ICDM (IEEE International Conference on Data Mining) paper - deciding what belongs in the body, in an appendix that counts inside the single 10-page IEEE cap, or in an external anonymized repository, plus planning the compression if the paper is accepted as a short paper.
Use when preparing the "artifact" of an ICDT (International Conference on Database Theory) paper, which at a pure-theory venue is the complete-proofs full version rather than a code package — covering why ICDT has no ACM-style artifact-badging or code-artifact track, what the marked appendix and the archived arXiv full version must contain, and (only for the rare algorithmic paper) how any code should be handled.
Use when preparing the final LIPIcs camera-ready for an accepted ICDT (International Conference on Database Theory) paper — the lipics-v2021 final document, mandatory ACM CCS concepts and keywords, author ORCIDs, de-anonymization, complete proofs and the full-version link, CC-BY licensing, and passing the Dagstuhl/DROPS production checks that mint the DOI.
Use when deciding how to split an ICDT (International Conference on Database Theory) paper between the 15-page lipics-v2021 body and the clearly-marked appendix that referees read at their discretion, given that online/external appendices are not allowed and every proof needed to certify the result must live inside the single submitted PDF.
Use when organizing ICLR appendices, supplementary files, anonymous code/data, revised PDFs, private links, and discussion-period updates under OpenReview rules. Use when deciding what stays in the main text versus the appendix, how to label a discussion-period revision so reviewers find changes fast, or how to package anonymous artifacts that remain part of the permanent public record after acceptance.
Use when preparing accepted ICML papers for camera-ready upload, PMLR agreement, public OpenReview record, lay summary, conflict disclosure, registration/presentation choices, format checker, and post-conference revision.