Skill UI

A comprehensive guide for developing rigorous theory for Information Systems Research (ISR) manuscripts. It outlines two primary theorizing modes—Behavioral (focusing on explicit causal mechanisms centered on the IT artifact) and Analytical (deriving propositions from economic/equilibrium models). The framework emphasizes making the theory sociotechnical by bridging traditional IS silos and ensuring the IT artifact is the load-bearing theoretical element, moving beyond simple correlation to mechanistic insight.

A comprehensive tool for sanity-checking research questions intended for Information Systems Research (ISR). It guides users to test the topic's fitness across four dimensions: IT-artifact centrality, sociotechnical framing, intradisciplinary potential, and level of analysis. It helps determine if the topic belongs in ISR or neighboring venues like MISQ or JMIS.

This skill acts as a comprehensive router for Information Systems Research (ISR) manuscripts. It guides users through the entire academic writing lifecycle, from initial topic selection and theory development to method application, drafting, and rebuttal. It ensures the manuscript adheres to the sociotechnical and intradisciplinary standards required by top-tier IS journals, helping authors identify the next logical step.

This guide provides a comprehensive framework for drafting authoritative author responses during academic conference reviews (e.g., ISSTA). It covers triage strategies, distinguishing between factual corrections and promised changes, and structuring a Major-Revision ledger. Learn how to address reviewer concerns strategically, maintain anonymity, and anchor all claims to evidence for maximizing acceptance chances.

This guide outlines the critical steps required after an academic paper has been accepted at a major conference. It details the process of converting an anonymous submission into the final, camera-ready version for publication in the ACM Digital Library. Key steps include de-anonymization (restoring author details, affiliations, and funding), completing ACM rights forms and metadata (ORCIDs, CCS), verifying the final layout integrity after template changes, and confirming presentation obligations.

This guide provides comprehensive guidelines for designing, conducting, and auditing empirical studies in software engineering. It emphasizes achieving scientific rigor by matching every claim to specific, measured evidence, ensuring fair baselining (equal budget), and applying appropriate advanced statistics (non-parametric tests, effect sizes). Essential reading for researchers submitting papers based on performance evaluations.

A guide for authors submitting research in software testing and analysis. It teaches how to structure the related work section to clearly demonstrate novelty and technical positioning. Authors must frame their contribution using a 'delta-first' approach, explicitly stating what the nearest existing technique lacks and how their work fills that gap, while also being vigilant about venue attribution and overlapping prior work.

Provides comprehensive guidelines for achieving high reproducibility and verifiability in academic research submissions, particularly for software analysis, fuzzing, and bug finding. It details the necessity of pinning substrates (like benchmark versions and program SHAs), fixing stochastic parameters (seeds and budgets), and mapping every empirical claim to verifiable evidence to meet stringent academic evaluation criteria.

A comprehensive guide for authors submitting research papers to ISSTA. It details critical steps such as adhering to ACM sigconf formatting, maintaining the 18-page limit, enforcing double-anonymous review, establishing the artifact plan, and managing HotCRP registration to prevent desk rejection.

Provides detailed guidelines for authors submitting technical research papers, clarifying how to split content between the main 18-page body and supplementary artifacts. It stresses that all decision-critical evidence, such as threat models and core results, must reside within the reviewed body to ensure reviewers can adequately evaluate the work without relying on accessing supplemental materials.

This guide helps researchers determine the optimal conference or journal venue for their software engineering contribution. It specifically addresses whether the core of the work is a testing or analysis technique evaluated on real subjects (ISSTA), or if it fits better within broader Software Engineering (ICSE/FSE), formal verification (PLDI/CAV), or applied domains.

A comprehensive guide for planning and executing a scientific paper submission for the ISSTA conference. It maps out all critical milestones, including venue fit, evidence locking, submission deadlines, major revisions, and artifact evaluation. The skill provides backward planning heuristics and identifies common failure modes to ensure timely and successful publication.