Skill UI

This guide provides a rigorous methodology for achieving scientific reproducibility in technical and user experience papers (e.g., UIST). It details three essential 'ledgers': the Build Ledger (pinning software, hardware, and environment dependencies), the Measurement Ledger (defining precise protocols for metrics like latency and accuracy), and the Study Ledger (documenting human evaluation tasks). Following these protocols ensures that external researchers can accurately rebuild the artifact and validate reported results.

A comprehensive guide for researchers determining if their Human-Computer Interaction (HCI) project contribution is an 'interface artifact' suitable for UIST, or if it belongs to a different venue like CHI or CSCW. It employs the 'artifact-subtraction test' to distinguish between technical system novelty and empirical user findings, ensuring proper conference submission routing.

A comprehensive guide for authors submitting interactive system papers to UIST. It details the required narrative arc (walkthrough before mechanism), emphasizes technical specificity in implementation details, and provides rules for designing figures and structuring the argument within strict page limits.

A specialized guide for authors aiming to submit to the Conference on Uncertainty in Artificial Intelligence (UAI). It provides expert advice on framing the core contribution—such as probabilistic reasoning, causal inference, and uncertainty modeling—and calibrating the manuscript for highly technical, statistical ML reviewers. Use this skill to refine your submission strategy, identify evidence gaps, and properly position your work relative to other top-tier AI venues like AISTATS and IJCAI.

A comprehensive guide for optimizing computer science manuscripts targeting the USENIX Annual Technical Conference (ATC). It covers core systems research fields (OS, networking, storage, security), defining the required evidence bar (built artifacts, clean evaluation), and re-framing the paper's contribution to align with top-tier systems venue expectations.

A comprehensive guide detailing the mandatory and optional evaluation phases for academic security artifacts, such as those required for USENIX Security. It covers Phase-1 (availability) checks and Phase-2 (functionality, reproducibility) requirements. Provides best practices for structuring code, managing technical hazards (e.g., dangerous-by-default behavior), and ensuring verifiable, reproducible results for peer review.

This guide provides comprehensive instructions for authors responding to peer reviews and engaging with a shepherd during major security symposium cycles (like USENIX Security). It details the technical mechanics of writing effective rebuttals, addressing compliance gaps (e.g., ethics/disclosure), and managing limited revisions during the post-acceptance shepherding phase.

This detailed guide helps researchers determine the optimal top-tier venue (e.g., USENIX Security, IEEE S&P, ACM CCS) for their security research paper. It emphasizes that venue selection must be based on the committee's core expertise and the existence of reusable artifacts, measurements, or systems evidence, ensuring the work has the necessary technical depth to succeed.

A rigorous guide for drafting high-stakes, technical security papers for the USENIX Security Symposium. It mandates a threat-model-first structure, requiring authors to quantify all security claims with measurable data to avoid hyperbole. The guide also details integrating responsible disclosure narratives and adhering to strict academic formatting rules.

This guide provides a comprehensive framework for authors responding to major conference reviews (like IEEE VIS). It details the distinct strategies for both first-round rebuttals and mandatory second-round revisions (conditional accept). Learn how to structure summaries of changes, address technical critiques, maintain anonymity, and turn reviewer skepticism into acceptance.

This comprehensive guide outlines the rigorous, multi-step process required for authors to finalize and submit their accepted papers for VLDB proceedings. It covers essential technical compliance points, including using the correct volume template, ensuring PDF/A compliance with embedded fonts, adhering to figure legibility rules, and detailing the permanent storage of research artifacts (DOI-backed). It also outlines the associated conference presentation obligations.

A comprehensive guide for designing and presenting highly rigorous technical evaluations for database or system papers. It covers establishing baseline necessity, proving mechanism causality through ablation, testing scalability across data sizes, and mandating the disclosure of loss cases to satisfy skeptical academic reviewers.