All authors
Claude Skills by brycewang-stanford
github.com/brycewang-stanford5,310 skills37 installs6,514 views
- Usenixsec SubmissionUse when finalizing a USENIX Security Symposium submission — the per-cycle HotCRP site, the registration deadline a week before the paper deadline, the 13-page body plus mandatory Ethical Considerations and Open Science appendices, double-blind sweeps, and the early-reject exposure of a weak upload.Votes: 0GitHub stars: 1,052
- Usenixsec SupplementaryUse when deciding what goes where in a USENIX Security Symposium paper — the 13-page body, the two mandatory one-page appendices (Ethical Considerations, Open Science), optional appendices after the references, and external artifacts — so nothing decision-critical lands where reviewers won't look.Votes: 0GitHub stars: 1,052
- Usenixsec Topic SelectionUse when deciding whether a project belongs at the USENIX Security Symposium or a sibling venue — routing among USENIX Security, IEEE S&P, ACM CCS, NDSS, and specialty venues (PETS, SOUPS, RAID, WOOT), and confirming the work has the artifact/measurement/systems evidence USENIX Security rewards.Votes: 0GitHub stars: 1,052
- Usenixsec WorkflowUse when planning a USENIX Security Symposium project end to end — choosing between the two annual cycles, mapping the registration-to-camera-ready calendar for a chosen cycle, sequencing artifact and ethics work early, and coordinating a team across the multi-deadline Big-Four calendar.Votes: 0GitHub stars: 1,052
- Usenixsec Writing StyleUse when drafting or revising prose for a USENIX Security Symposium paper — threat-model-first structure, calibrated security claims, disclosure narrative woven into the text, 13-page discipline in the USENIX template, and the plain systems-security register this program committee rewards.Votes: 0GitHub stars: 1,052
- Vis Artifact EvaluationUse when packaging an IEEE VIS artifact for the Graphics Replicability Stamp Initiative (GRSI) / TVCG Replicability Stamp and the IEEE VIS Open Practices program, covering what an independent GRSI volunteer reproduces first, DOI-issuing archives, evaluator-proof documentation for visualization code and data, and how VIS reproducibility differs from ACM-style artifact badges.Votes: 0GitHub stars: 1,052
- Vis Author ResponseUse when drafting IEEE VIS author responses across the two-phase review, covering the first-round reviewer discussion, and — distinctively — the conditional-accept second-round revision with its summary-of-changes that maps every required change to a concrete edit and is re-read by the same primary, secondary, and external reviewers under the IEEE TVCG process.Votes: 0GitHub stars: 1,052
- Vis Camera ReadyUse when preparing an accepted IEEE VIS paper for its IEEE TVCG camera-ready, covering de-anonymization, the VGTC/TVCG template and journal metadata (DOI, ORCID, IEEE keywords/index terms), integrating the second-round required changes without scope creep, permanentizing open-materials links, the Open Practices disclosure form, and the Graphics Replicability Stamp handoff.Votes: 0GitHub stars: 1,052
- Vis ExperimentsUse when designing or auditing IEEE VIS evaluations, covering how to match evidence to the contribution type (perceptual study, controlled user study, algorithm benchmark, design-study validation, qualitative work), controlled experiment design with power and effect sizes, CVD-safe and perceptually grounded encoding choices, task taxonomies, and provenance so a TVCG reviewer trusts the result.Votes: 0GitHub stars: 1,052
- Vis Related WorkUse when positioning an IEEE VIS submission against the visualization literature across TVCG, the six VIS areas, EuroVis/CGF, PacificVis, and adjacent HCI/graphics venues, writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind when opted in, and handling concurrent, preprint, and prior-version overlap for a TVCG journal article.Votes: 0GitHub stars: 1,052
- Vis ReproducibilityUse when strengthening IEEE VIS reproducibility and open-practices evidence, covering the open-materials statement, anonymized-but-runnable code and stimuli, preregistration of perceptual and user studies, provenance for datasets and rendering pipelines, claim-to-figure mapping, honest degrees of reproducibility, and consistency between what the TVCG paper says and what the supplemental archive contains.Votes: 0GitHub stars: 1,052
- Vis Review ProcessUse when reasoning about how an IEEE VIS full-paper submission is evaluated, covering the two-phase review that mirrors IEEE TVCG, the primary/secondary/external (and 2026 student) reviewer roles, the six-area routing through Area Paper Chairs, the conditional-accept second round, and how VIS's journal-integrated process differs from a single accept/reject conference and from CHI/CVPR.Votes: 0GitHub stars: 1,052
- Vis SubmissionUse when auditing an IEEE VIS full-paper submission for PCS readiness, covering the abstract-then-paper two-deadline structure under the VGTC society, the IEEE VGTC/TVCG 9+2 page budget, author-optional double-blind anonymization, the supplemental-material one-week window, and desk-reject triage before the AoE cutoff for a paper that will publish in IEEE TVCG.Votes: 0GitHub stars: 1,052
- Vis SupplementaryUse when deciding what belongs in an IEEE VIS paper body versus its supplemental materials, covering the VGTC/TVCG 9+2 page budget, the supplemental video that VIS reviewers routinely watch, the one-week supplemental deadline extension, double-blind supplemental anonymization, and how to split a visualization paper between the reviewed pages and the archive.Votes: 0GitHub stars: 1,052
- Vis Topic SelectionUse when deciding whether a project belongs at IEEE VIS or should be routed to EuroVis, PacificVis, CHI, a graphics venue, or the IEEE TVCG journal track, and when choosing among the six VIS areas (Theoretical & Empirical, Applications, Systems & Rendering, Representations & Interaction, Data Transformations, Analytics & Decisions) by contribution type and evidence maturity.Votes: 0GitHub stars: 1,052
- Vis WorkflowUse when planning an IEEE VIS project timeline from area fit through the abstract and full-paper deadlines, the two-phase review, the conditional-accept second round, the IEEE TVCG camera-ready, the Graphics Replicability Stamp, and presentation, with backward-planning offsets for a visualization paper and honest handling of the annual cycle and the second-round revision window.Votes: 0GitHub stars: 1,052
- Vis Writing StyleUse when revising an IEEE VIS paper for a task-grounded visualization contribution on the first page, a design rationale that ties each visual encoding and interaction to a task, evaluation matched to the contribution type, honest limitations, and disciplined use of the VGTC/TVCG 9+2 page budget for a paper that will be read as an IEEE TVCG journal article.Votes: 0GitHub stars: 1,052
- Vldb Artifact EvaluationUse when preparing a PVLDB artifact for the pVLDB Reproducibility Evaluation or the ACM availability badge, covering the mandatory participation rule for EA&B papers, the four artifact surfaces evaluators rebuild, packaging for a rerun by strangers, and positioning for the Best Reproducible Paper Award at VLDB.Votes: 0GitHub stars: 1,052
- Vldb Author ResponseUse when a PVLDB paper receives a revision verdict and the response package must be built, covering the one-shot revision rule, the three-month window, reading the reviewers' required-changes list, planning new experiments against the clock, and writing the change document that VLDB reviewers re-evaluate against.Votes: 0GitHub stars: 1,052
- Vldb Camera ReadyUse when producing the final PVLDB version of an accepted VLDB paper, covering the volume-specific template, PDF/A compliance and font embedding, figure legibility floors, the availability paragraph and artifact URL, proceedings file naming and copyright steps, and planning presentation at the matching VLDB conference.Votes: 0GitHub stars: 1,052
- Vldb ExperimentsUse when designing or auditing the evaluation of a VLDB paper, covering workload and dataset realism at scale, competitor tuning fairness, scalability curves versus single points, tail-latency and throughput reporting, ablations that isolate the mechanism, and the loss-case disclosure PVLDB reviewers look for first.Votes: 0GitHub stars: 1,052
- Vldb Related WorkUse when positioning a PVLDB submission against prior literature, covering the deep database canon back to the 1980s VLDB proceedings, the SIGMOD/ICDE/CIDR neighborhood, concurrent work under rolling monthly deadlines, industrial and open-source systems as citable prior art, and overlap declarations for extended versions.Votes: 0GitHub stars: 1,052
- Vldb ReproducibilityUse when engineering reproducibility into a VLDB paper before submission, covering hardware and configuration disclosure, dataset and workload provenance, run-to-run variance in systems measurements, competitor-version pinning, figure-to-raw-data traceability, and the disclosure floor PVLDB reviewers apply to performance claims.Votes: 0GitHub stars: 1,052
- Vldb Review ProcessUse when reasoning about how PVLDB reviewing actually works, covering the rolling monthly pipeline, the roughly six-week review turnaround, the accept/revise/reject outcome space, the one-shot revision's odds, single-blind dynamics, the volume review board, and how a VLDB decision differs from batch-deadline venues.Votes: 0GitHub stars: 1,052
- Vldb SubmissionUse when auditing a PVLDB submission before a monthly deadline, covering the mandatory abstract on the 25th, the CMT window, the 1st-of-month 5:00 PM Pacific cutoff, category and page-budget choice, single-blind cover-page requirements, the per-month and per-year author caps, and desk-reject hazards specific to VLDB.Votes: 0GitHub stars: 1,052
- Vldb SupplementaryUse when deciding what lives outside a PVLDB paper's page budget, covering the rule that appendices count against the limit, the extended technical report on arXiv under single-blind review, proof and algorithm placement, artifact repositories as the extra-results home, and keeping the paper self-contained for VLDB reviewers.Votes: 0GitHub stars: 1,052
- Vldb Topic SelectionUse when deciding whether a project belongs at VLDB and in which PVLDB category, applying the data-management-primitive test, choosing among Regular, EA&B, Scalable Data Science, and Vision papers, and routing against SIGMOD, ICDE, CIDR, EDBT, PODS, KDD, systems venues, and The VLDB Journal.Votes: 0GitHub stars: 1,052
- Vldb WorkflowUse when planning a VLDB project on the PVLDB rolling calendar, covering month-picking strategy, the volume-to-conference mapping and acceptance cutoff, budgeting a possible three-month revision, coordinating author caps across a group, and backward planning from the 25th-abstract / 1st-paper rhythm.Votes: 0GitHub stars: 1,052
- Vldb Writing StyleUse when revising a PVLDB paper's prose, covering the page-one contract for systems readers, scoping performance claims to measured regimes, stating design trade-offs instead of hiding them, terminology and notation discipline across a 12-page budget, and the tone VLDB's builder-reviewers reward.Votes: 0GitHub stars: 1,052
- Wacv Artifact EvaluationUse when packaging code, data, and models for a WACV paper, covering the anonymous review artifact versus the public post-acceptance release, reproducing constraint-based applications claims (latency, power, robustness) not just accuracy, dataset licensing and release, and keeping the artifact in sync across the two-round Revise-and-Resubmit lap.Votes: 0GitHub stars: 1,052
- Wacv Author ResponseUse when responding to WACV reviews, covering the optional one-page Round 1 rebuttal and, separately, the Revise-and-Resubmit change summary that carries a revised paper into the no-rebuttal Round 2, including how to triage three reviews for the area chair, what a rebuttal can and cannot claim, and keeping every response double-blind.Votes: 0GitHub stars: 1,052
- Wacv Camera ReadyUse when preparing a WACV camera-ready after acceptance, covering de-anonymization, IEEE Xplore plus CVF open-access dual publication, IEEE copyright and PDF checks, the dataset and code release obligation, per-paper registration, and preparing the winter-conference talk or poster once a paper clears Round 1 or Round 2.Votes: 0GitHub stars: 1,052
- Wacv ExperimentsUse when designing or auditing WACV experiments, covering Applications-track systems evidence (latency, power, robustness under real constraints) versus Algorithms-track matched-baseline novelty, comparative assessment under the deployed condition, uncertainty over seeds and sessions, ablations, and evidence that survives the two-round review.Votes: 0GitHub stars: 1,052
- Wacv Related WorkUse when writing or auditing a WACV related-work section, covering how to position an applications or algorithms contribution against fast-moving vision literature, sibling-venue (CVPR/ICCV/ECCV) and arXiv concurrency, application-domain literature, double-blind self-citation, and verifying that cited "WACV papers" are actually WACV papers.Votes: 0GitHub stars: 1,052
- Wacv ReproducibilityUse when strengthening the reproducibility of a WACV paper, covering the recipe ledger for constraint-aware systems, benchmark and split hygiene, seed and session honesty, device and power reporting for applications claims, and keeping the reproduction package in sync with the paper across the two-round Revise-and-Resubmit lap.Votes: 0GitHub stars: 1,052
- Wacv Review ProcessUse when reasoning about how WACV decides a paper, covering the two-round model, the Round 1 Accept / Revise-and-Resubmit / Reject recommendations, the optional Round 1 rebuttal, the no-rebuttal Round 2, area-chair consolidation, double-blind confidentiality, and where author leverage actually exists across the two rounds.Votes: 0GitHub stars: 1,052
- Wacv SubmissionUse when auditing a WACV submission before an OpenReview round deadline, covering the Round 1 vs Round 2 choice, the Applications vs Algorithms track field, the 8-page-including-figures limit, double-blind anonymity and OpenReview-profile requirements, the anonymized supplement, dual submission, and desk-reject triage.Votes: 0GitHub stars: 1,052
- Wacv SupplementaryUse when organizing WACV supplementary material, covering what belongs in the anonymized supplement versus the 8-page body, packaging qualitative videos and extra results without breaking double-blind, keeping the supplement consistent with the paper across the two-round revision, and honoring WACV's no-author-identifying-links rule.Votes: 0GitHub stars: 1,052
- Wacv Topic SelectionUse when deciding whether a project belongs at WACV or should route elsewhere, covering WACV's applications-first identity within the CVF's CVPR/ICCV/ECCV/WACV calendar, the Applications-vs-Algorithms track choice, whether the two-round winter timing fits your schedule, and routing to CVPR, ICCV, ECCV, 3DV, or a journal.Votes: 0GitHub stars: 1,052
- Wacv WorkflowUse when planning a WACV campaign calendar across the two-round model, from track and round choice through the Round 1 submission, rebuttal, and Accept/Revise-and-Resubmit/Reject decision, into the Round 2 revision and decision, camera-ready, and the winter conference — with the branch points that a single-deadline plan misses.Votes: 0GitHub stars: 1,052
- Wacv Writing StyleUse when revising a WACV paper's prose and first page, covering how to write for the chosen Applications or Algorithms track, leading with the real-world constraint or the method, self-contained figure captions inside the 8-page-including-figures budget, scoped claims, and a first page that pre-empts the Revise-and-Resubmit question.Votes: 0GitHub stars: 1,052
- Wsdm Artifact EvaluationUse when packaging code, data, and models as evidence for a WSDM paper - anonymous repositories cited in the PDF, the proprietary-log dilemma of web-scale research, public-benchmark substitution tiers, WSDM Cup datasets, and what credible artifact release looks like at a venue without a formal badge process.Votes: 0GitHub stars: 1,052
- Wsdm Author ResponseUse when planning author-side communication for WSDM, a venue that historically runs no rebuttal - covers preemptive objection engineering inside the submitted PDF, the narrow legitimate channels to chairs after submission, reading reviews you cannot answer, and converting a rejection into a stronger next-cycle or sibling-venue submission.Votes: 0GitHub stars: 1,052
- Wsdm Camera ReadyUse when preparing a WSDM camera-ready after acceptance - de-anonymization order, ACM rights and TAPS production into the Digital Library proceedings, CCS concepts and keywords, page-allowance verification, artifact link restoration, and registration/presentation duties at a single-track winter conference.Votes: 0GitHub stars: 1,052
- Wsdm ExperimentsUse when designing or auditing the evaluation of a WSDM paper - offline ranking and recommendation metrics with bias controls, temporal-split protocols for interaction logs, baseline selection from recent WSDM/SIGIR/KDD editions, ablations that isolate the mechanism, efficiency reporting, and online-evidence framing.Votes: 0GitHub stars: 1,052
- Wsdm Related WorkUse when positioning a paper against prior literature for WSDM - locating the work inside WSDM's own research lineages (click models, unbiased LTR, sequential recommendation, community detection), contrasting against SIGIR/KDD/WWW/CIKM/RecSys neighbors, venue-misattribution traps, and compressing the section for the tight page budget.Votes: 0GitHub stars: 1,052
- Wsdm ReproducibilityUse when hardening the reproducibility of a WSDM paper built on logs, graphs, or user-interaction data - provenance of behavioral datasets, temporal split discipline, click-bias assumptions, seed and variance reporting, privacy-preserving release, and honesty tiers for results no outsider can rerun.Votes: 0GitHub stars: 1,052
- Wsdm Review ProcessUse when reasoning about how WSDM reviews and decides papers - the hybrid single/double-blind architecture with Associate-Chair metadata visibility, at-least-three PC reviews plus senior PC assessment, the absence of a rebuttal phase, the August-to-October window, and what ~17% selectivity at a single-track venue implies.Votes: 0GitHub stars: 1,052
- Wsdm SubmissionUse when auditing a WSDM submission before the August deadlines - EasyChair setup, the abstract-then-paper week, the appendix-inclusive page budget, the required ethical-considerations section, anonymization that survives Associate-Chair metadata visibility, and desk-reject exposure at a no-rebuttal venue.Votes: 0GitHub stars: 1,052
- Wsdm SupplementaryUse when deciding what goes where in a WSDM submission whose appendices count inside the page cap - triage between the 9-page body, the uncounted references and ethics section, and the cited external repository; compression tactics for proofs, prompts, and hyperparameter tables under WSDM's historically tight budget.Votes: 0GitHub stars: 1,052