Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use when auditing an IEEE INFOCOM main-conference submission for EDAS readiness, covering the two-step abstract-then-paper registration, the IEEEtran two-column 10-page/9-page-of-text budget, double-blind anonymization of the PDF and metadata, the five-papers-per-author cap, and desk-reject triage before the AoE cutoff.
Use when deciding what fits inside an IEEE INFOCOM paper's tight IEEEtran budget, covering the rule that appendices count toward the nine pages of text, the absence of a separate supplementary channel at review time, double-blind handling of any released material, and how to split an analytical or systems networking paper between the body and an optional external release.
Use when auditing an INTERSPEECH submission before the CMT deadline — the strict 4-page-plus-references format, double-anonymous rules and the pre-deadline anonymity period, scientific-area and metadata choices, the post-deadline paper-update window, dual-submission policy, and the desk-reject triggers specific to ISCA's flagship.
Use when deciding what accompanies an INTERSPEECH paper beyond its 4 pages — audio sample pages and multimedia for listening-based judgment, what reviewers may ignore versus must see, the references-and-acknowledgments page's strict scope, and packaging extra analyses when no reviewed appendix exists.
Use when building tables and figures for an International Organization (IO) manuscript so exhibits are self-contained, accessible, reproducible, and count toward the word budget correctly. IO word limits include tables, figures, and notes (but exclude the bibliography), and exhibits must survive IO's pre-publication result verification. Designs exhibits; it does not run the analysis.
Use when preparing the replication/transparency materials for an International Organization (IO) manuscript. IO's signature requirement is verification BEFORE final acceptance — the editorial staff request data and code at conditional acceptance, IO staff re-run quantitative results and check proofs of formal models, and editors withhold final acceptance until all reported results are confirmed; materials then deposit to the IO Dataverse with a DOI and a Data Availability Statement. Prepares the package; it does not waive requirements.
Use when preparing an accepted IPSN-lineage paper for camera-ready, covering de-anonymization, the ACM Primary Article Template and the dual ACM/IEEE metadata (CCS concepts, ORCID, DOI, IEEE PDF eXpress/e-copyright), integrating required changes without scope creep, permanentizing dataset/firmware links, and the artifact-award handoff.
Use when deciding what belongs in an IPSN-lineage paper body versus its artifact, appendix, and demo/poster track, covering the ≤12-page ACM two-column budget, the rule that decision-critical evidence stays inside the reviewed pages, double-blind supplementary material, dataset release, and how to split a sensor-systems paper between body and package.
Use when preparing the IROS video attachment as evidence — the 60-second/10 MB limit, its own deadline, storyboarding uncut real trials and labeled failures, showing playback speed honestly, anonymizing footage under the double-anonymous cycle, and compensating for the fact that IROS provides no supplementary PDF.
Use when converting an accepted ISCA paper into its published form — de-anonymizing authors, acknowledgments, and artifact links; satisfying the edition's publisher workflow under the alternating ACM/IEEE arrangement; integrating shepherd requirements and badges; and preparing the June talk and attendance logistics.