Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use when positioning an ISCA submission against prior art — covering five decades of architecture literature across ACM DL, IEEE Xplore, and dblp, differentiating by mechanism rather than metric, handling self-citations and arXiv preprints under double-blind rules, and exploiting ISCA's unlimited reference pages.
Use when reasoning about how an ISCA submission is evaluated — the two-round review structure with December and February reviewer waves, what the combined rebuttal-and-revision window means for decisions, PC-meeting dynamics at a flagship architecture venue, and how to read the eventual outcome.
Use when deciding whether a project belongs at ISCA, the ACM/IEEE flagship architecture symposium — testing whether the machine itself is the contribution, choosing between ISCA's November gate and the MICRO, HPCA, and ASPLOS seats in the architecture year, and weighing the main track against the industry track.
Use when executing and reporting the analysis for an Information Systems Research (ISR) manuscript — identification and validity for empirical work, proof discipline and comparative statics for analytical work, and rigorous evaluation for design-science work, with overflow routed to the electronic companion. Runs and reports the analysis; it does not design the study (isr-methods) or frame the contribution (isr-contribution-framing).
Use when choosing and stress-testing the research design for an Information Systems Research (ISR) manuscript — matching the genre (behavioral empirical, analytical-economic modeling, design-science, or multimethod) to the question, and ensuring the design can actually support the IS contribution. Designs the study; it does not execute the estimation/derivation (isr-data-analysis) or frame the contribution (isr-contribution-framing).
Use when building or refining the mechanism for an Information Systems Research (ISR) manuscript — deriving behavioral hypotheses for empirical work or analytical propositions/equilibrium predictions for modeling work, always centered on the IT artifact and the sociotechnical interplay across levels of analysis. Builds the theory; it does not test it (isr-methods, isr-data-analysis).
Use when explaining or planning around ISSTA peer review, covering double-anonymous reviewing, at least three PC reviews, the Accept/Major-Revision/Reject outcome model, the phase-two major-revision resubmission, the named evaluation criteria, how the decision is actually synthesized, and how earlier editions ran multiple rolling deadlines.
Use when deciding whether a project is a strong ISSTA fit versus ICSE, FSE, ASE, ICST, PLDI/CAV, or an SE journal, identifying whether the contribution is a testing/analysis technique, characterizing its evaluation shape, and sharpening the framing before writing begins.
Use when deciding what counts as evidence for an ITCS theory claim — proofs as the primary evidence, worked examples and separations that make a model concrete, and the rare, well-scoped illustrative computation or simulation — and how to keep any computational content checkable and subordinate to the mathematics.
Use to model the ITCS reviewing pipeline — a program committee plus external reviewers, conceptual-novelty weighting, lightweight double-blind, no author-response/rebuttal phase, and a single accept/reject decision — and to understand where the (limited) author leverage actually is.