Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use when hardening an ICRA paper's reproducibility — specifying robot platform, firmware, ROS and driver versions, control rates, and sensor calibration; logging rosbags and seeds; separating what others can rerun (code, sim) from what they can only audit (your hardware trials); and writing honest availability statements.
Use when designing or auditing the evaluation of an ICSE research-track paper, covering subject and benchmark selection, baseline fairness, statistical tests and effect sizes as SE reviewers expect them, qualitative-methods rigor, ablations for AI-based techniques, and threats-driven study design.
Use when building the related-work and positioning sections of an ICSE research-track paper, covering the literature lanes SE reviewers check, searching ACM DL, IEEE Xplore and dblp across the flagship venues, staying current in fast-moving areas like LLM4SE, and keeping self-citations double-anonymous.
Use when reasoning about how an ICSE research-track submission is evaluated, covering double-anonymous PC review, the four posted criteria, the Accept / Major Revision / Reject decision model, the revision-and-final-decision timeline, and what recent ICSE acceptance statistics imply for strategy.
Use when designing or auditing IEEE ICSME empirical evaluations, covering real evolving subject systems, mining-software-repositories provenance, fair baselines, SE-standard statistics and effect sizes, change-history and survivorship confounds, qualitative rigor, contamination-aware LLM ablations, and matching evidence to the shape of each maintenance/evolution claim.
Use when reasoning about how an IEEE ICSME research submission is evaluated, covering double-anonymous review, the early-decision cut that issues Accept/Reject before the rebuttal, the "Response Recommended" author-response period, the single-round accept/reject model with no Major Revision, and how ICSME's process differs from FSE's journal-style round and ICSE's cycles.
Use when deciding whether a software-engineering project belongs at IEEE ICSME (maintenance, evolution, reverse engineering, program comprehension, technical debt, refactoring, mining software repositories) or should be routed to ICSE, FSE, ASE, ISSTA, MSR, SANER, SCAM, or an SE journal (TSE/EMSE), and when to use ICSME's Journal-First, Registered Reports, or RENE tracks instead of the research track.
Use when targeting IEEE Conference on Virtual Reality and 3D User Interfaces (IEEE VR) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for virtual reality.
Use when targeting IEEE INFOCOM (INFOCOM) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for networking.
Use when targeting IEEE International Conference on Automation Science and Engineering (CASE) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for automation.