Skill UI

A comprehensive guide for researchers deciding the best venue for their machine learning manuscript. It helps evaluate whether a paper is a strong fit for ICML, or if it should be rerouted to specialized tracks, other top-tier conferences (NeurIPS, ICLR), or academic journals based on its core contribution type (theory, method, application) and novelty.

This guide provides a structured methodology for handling reviewer comments across various academic publishing channels, including camera-ready revisions, formal journal response letters, and resubmission memos. It teaches researchers how to move beyond simple rebuttal by focusing on technical honesty, evidence-based arguments, and disciplined revision processes required by top conferences (ICRA/IROS) and journals (RA-L).

A comprehensive guide for authors preparing the 'Related Work' section for top-tier robotics conferences like ICRA. It details how to conduct thorough literature reviews across multiple research 'lanes,' handle concurrent work (arXiv), properly self-cite under double-anonymous rules, and position the novelty against both academic rivals and commercial systems.

A comprehensive guide detailing the end-to-end annual submission and presentation cycle for the IEEE ICRA conference. It covers critical milestones—from paper deadlines and video attachments to camera-ready submissions—and provides structured backward planning, fallback strategies (RA-L, IROS), and tips for navigating the academic timeline in robotics research.

This guide details the rigorous process of preparing research artifacts for formal evaluation at major academic conferences like ICSE. It covers achieving ACM badges (Available, Reusable, Reproduced/Replicated) by ensuring proper DOI archiving, open licensing, robust documentation, and verifiable reproducibility for external reviewers, transforming raw research into publishable, trustworthy assets.

A comprehensive guide for authors converting an accepted research paper into its final, published camera-ready form. This checklist covers critical steps including de-anonymization, restoring author metadata (ORCIDs, DOIs), strategically utilizing extra page content, and ensuring strict production quality (IEEE templates, references, and availability statements) required for major academic proceedings.

A comprehensive guide for designing, executing, and reporting high-stakes research studies in Software Engineering (SE), tailored to meet the stringent standards of top academic conferences like ICSE. It covers best practices for evidence-claim matching, advanced statistical rigor (non-parametric tests, effect sizes), handling AI model ablations, and implementing threats-driven design to ensure findings are robust, valid, and maximally reproducible.

A comprehensive guide detailing the academic standards for ensuring research reproducibility at ICSE. Covers open-science policies, mandatory data availability statements, techniques for pinning provenance (especially for mining and LLMs), and best practices for maintaining verifiability while ensuring anonymity. Essential for academic submissions.

A comprehensive guide for authors submitting to major academic conferences (e.g., ICSE). It details the strict rules for differentiating mandatory core content (the 10-page limit) from supporting evidence, such as extended proofs, scripts, and raw data, which must be placed in an anonymized supplementary package. Learn the 'summarize-and-point' discipline to ensure verifiability and maintain reviewer trust.

This guide helps software engineering researchers determine the most appropriate academic conference or journal venue for their work. It provides comprehensive fit tests based on contribution type, empirical evidence maturity, and potential impact on industry practice. Authors learn to evaluate their research against criteria like novelty, rigor, and real-world relevance, ensuring proper routing to specialized tracks (e.g., ISSTA, ASE, ICSE).

A comprehensive, single-cycle master calendar and workflow guide for major academic conferences like ICSE. It details the entire ten-month journey, covering mandatory milestones from abstract submission and full paper drafting to author response, revision sprints, and final camera-ready preparation. This guide helps research teams plan backward, mitigate timeline risks, and manage complex project dependencies.

This guide provides detailed structuring advice for writing empirical software engineering (SE) research papers for top-tier conferences like ICSE. It focuses on adopting the required academic rigor, including using Research Questions (RQs) as the core skeleton, mastering the 'Threats to Validity' section, and calibrating claims for verifiability. Learn how to structure the abstract, compress content into a 10-page limit, and address reviewer expectations in the SE community.