Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use when planning an IEEE S&P (Oakland) submission calendar across the two-cycle year, including registration-versus-paper deadlines, the early-reject and rebuttal windows, Revise resubmission timing, the one-year embargo clock, and choosing which cycle a project can realistically hit.
Use when planning an ACM IMC campaign end to end, covering the choice between the two annual deadlines, backward planning from the target cutoff, the registration step, the One-Shot-Revision path across deadlines, availability shepherding, the camera-ready and dataset release, and the Replicability Track calendar.
Use when planning an IROS project timeline from venue fit through the spring paper deadline, the separate video deadline, the summer review silence, the June notification, the July camera-ready, IEEE Xplore publication, registration, and presentation, with backward-planning offsets for a real-robot paper on the fall IEEE/RSJ calendar.
Use when deciding which jacs-* sub-skill to invoke next, or when sequencing a Journal of the American Chemical Society (JACS) manuscript from scope check through revision. Routes — it does not replace — the specialized skills.
Use when navigating the Journal of Financial Intermediation (JFI) editorial process — the active desk-rejection policy, single-anonymized (single-blind) review with at least one expert referee when sent out, the tightly limited appeal path, and the option to choose the Managing Editor. It sets expectations; it does not draft content.
Use when deciding which jms-* sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Journal of Management Studies (JMS) submission. Routes — it does not replace — the specialized skills.
Use when deciding which mgsci-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Management Science (INFORMS) manuscript. Routes — it does not replace — the specialized skills, and helps pick the right Department lane (analytical vs empirical).
Use when explaining or planning around MobiSys peer review — the two-round process with an early-reject cut after round 1, the round-2 rebuttal window, double-blind HotCRP mechanics, the systems-and-services reviewer pool, and decision criteria for on-device claims, so response strategy fits how MobiSys decides.
Use when planning a MobiSys project timeline backward from the single early-December paper deadline through registration, two-round review with an early-reject cut, the rebuttal, notification, artifact evaluation, camera-ready, and the June conference — with device-experiment lead time built in and the one-deadline-per-year risk made explicit.
Use when planning or managing a full OSDI cycle — the December title-registration and submission deadlines on HotCRP, the silent no-rebuttal review window, March notification, the May artifact deadline, June shepherded final papers, and the July conference — including rejection retargeting to SOSP or NSDI.