All authors
Claude Skills by brycewang-stanford
github.com/brycewang-stanford5,310 skills37 installs6,514 views
- Siggraph Writing StyleUse when structuring or revising a SIGGRAPH / TOG technical paper, covering the teaser figure, a results-first first page, the graphics contribution framing (technique + quality/performance), comparison-driven evaluation, honest limitations, and the acmart 7-page discipline for the conference track.Votes: 0GitHub stars: 1,052
- Sigir Artifact EvaluationUse when packaging code, run files, test collections, or judgments for a SIGIR submission — deciding between an artifact inside a full/short paper and a standalone Resources track paper, building reviewer-runnable IR repositories, run-file and qrels hygiene, licensing and datasheets, and single- vs double-anonymous handling.Votes: 0GitHub stars: 1,052
- Sigir Author ResponseUse when reviews arrive for a SIGIR submission and the authors must decide how to answer — triaging IR-reviewer objections (weak baselines, missing significance tests, collection choice), writing within whatever response mechanism the current SIGIR cycle actually offers, and planning the resubmission path if the answer is no.Votes: 0GitHub stars: 1,052
- Sigir Camera ReadyUse when an accepted SIGIR paper must become the ACM Digital Library version of record — de-anonymizing the sigconf source, CCS concepts and keywords, the e-rights form, TAPS source upload and proof checking, restoring real system and dataset names, and the April camera-ready window before the July conference.Votes: 0GitHub stars: 1,052
- Sigir ExperimentsUse when designing or auditing the empirical program of a SIGIR paper — choosing test collections that match the claim, metric-cutoff discipline, paired significance testing with multiple-comparison correction, baseline tuning symmetry, ablations that isolate mechanisms, efficiency reporting, and LLM-era evaluation pitfalls.Votes: 0GitHub stars: 1,052
- Sigir Related WorkUse when positioning a paper against the information-retrieval literature for SIGIR — tracing lineage through SIGIR/TOIS/TREC canon, contrasting mechanisms with the nearest recent SIGIR papers, avoiding venue misattribution (DPR is EMNLP, ANCE is ICLR, NCF is WWW), and handling arXiv-era concurrent work in a fast-moving field.Votes: 0GitHub stars: 1,052
- Sigir ReproducibilityUse when strengthening the reproducibility of a SIGIR paper or preparing a SIGIR Reproducibility track submission — pinning the retrieval pipeline, seeds and variance for neural rankers, documenting collection versions and index settings, and structuring a reproduction study of published IR results with honest divergence analysis.Votes: 0GitHub stars: 1,052
- Sigir Review ProcessUse when reasoning about how SIGIR evaluates submissions — the per-track OpenReview machinery, double-blind full/short review versus single-anonymous Resources review, the PC-member nomination duty, what IR reviewers score (evaluation validity above novelty claims), the ACM Peer Review Policy layer, and how decisions land.Votes: 0GitHub stars: 1,052
- Sigir SubmissionUse when auditing a SIGIR full or short paper before the deadline — the 9-page vs 4-page budgets with appendices counted inside, ACM sigconf anonymization, per-track OpenReview groups, the PC-member nomination duty, cross-track double-submission bans, AI-use disclosure, and desk-reject triage for the ACM SIGIR conference.Votes: 0GitHub stars: 1,052
- Sigir SupplementaryUse when deciding what goes inside a SIGIR paper's page budget versus the cited repository — SIGIR counts appendices inside the 9-page (full) and 4-page (short) limits with only references free, so overflow material must be re-homed into run files, repository docs, or cut, without hiding review-critical evidence outside the paper.Votes: 0GitHub stars: 1,052
- Sigir Topic SelectionUse when deciding whether a project belongs at SIGIR and in which of its tracks — testing whether retrieval is the contribution or the plumbing, forking across full/short/resources/reproducibility/perspectives/industry, and routing misfits to ECIR, CIKM, WSDM, CHIIR, ICTIR, RecSys, TheWebConf, or NLP/ML venues.Votes: 0GitHub stars: 1,052
- Sigir WorkflowUse when planning a SIGIR project calendar — backward-planning from the January-pattern abstract/paper deadlines to the July conference, sequencing evidence freeze, significance testing, and anonymization, coordinating multi-track decisions, and wiring the SIGIR/ECIR/CIKM/WSDM/SIGIR-AP fallback calendar into one pipeline.Votes: 0GitHub stars: 1,052
- Sigir Writing StyleUse when drafting or revising prose for a SIGIR paper — the IR register that leads with task, collection, and metric; claim sentences calibrated to significance results; first-page architecture for retrieval contributions; table-centric argumentation; and compressing into the 9-page budget without cutting soundness.Votes: 0GitHub stars: 1,052
- Sigmetrics Artifact EvaluationUse when packaging an ACM SIGMETRICS artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced), covering what performance-evaluation evaluators check first (does the simulation regenerate the figures and match the analysis?), DOI-issuing archives, evaluator-proof documentation, and confirming whether an artifact track runs this cycle.Votes: 0GitHub stars: 1,052
- Sigmetrics Author ResponseUse when responding to ACM SIGMETRICS reviews, covering any initial rebuttal and — distinctively — the one-shot revision response letter that must map every item on the reviewers' required-changes list to a concrete change in the revised POMACS paper, resubmitted to a subsequent rolling deadline and re-reviewed once by the original reviewers under double-anonymity.Votes: 0GitHub stars: 1,052
- Sigmetrics Camera ReadyUse when preparing an accepted ACM SIGMETRICS paper for its POMACS camera-ready, covering de-anonymization, the acmsmall template and POMACS journal metadata (DOI, ORCID, CCS concepts), incorporating the shepherd's required changes without scope creep, permanentizing artifact links, and the ACM artifact-badge handoff.Votes: 0GitHub stars: 1,052
- Sigmetrics ExperimentsUse when designing or auditing ACM SIGMETRICS evaluations, covering theorem-plus-validation rigor, stating and testing modeling assumptions, analysis-vs-simulation agreement, real workloads and traces, fairly tuned baselines, statistics and confidence intervals for stochastic systems, learning guarantees, measurement provenance, and matching evidence to the shape of each performance claim.Votes: 0GitHub stars: 1,052
- Sigmetrics Related WorkUse when positioning an ACM SIGMETRICS submission against the performance-evaluation literature across SIGMETRICS/POMACS, Performance Evaluation, QUESTA, TON, and the systems/learning/measurement neighbors (NSDI/OSDI, IMC, NeurIPS/ICML), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling concurrent and prior-version overlap.Votes: 0GitHub stars: 1,052
- Sigmetrics ReproducibilityUse when strengthening ACM SIGMETRICS reproducibility, covering proofs and their assumptions as reproducible artifacts, seeded simulators whose figures regenerate and match the analysis, measurement/trace provenance, claim-to-evidence mapping, honest degrees of reproducibility, and consistency between what the paper proves/measures and what the artifact contains.Votes: 0GitHub stars: 1,052
- Sigmetrics Review ProcessUse when reasoning about how an ACM SIGMETRICS submission is evaluated, covering the hybrid conference-journal model, double-anonymous review, the three first-round outcomes (Accept-with-shepherding / One-Shot Revision / Reject), the one-shot revision resubmitted to a subsequent rolling deadline, the 12-month resubmission bar, and how SIGMETRICS differs from IMC, SIGCOMM, and NSDI.Votes: 0GitHub stars: 1,052
- Sigmetrics SubmissionUse when auditing an ACM SIGMETRICS submission for HotCRP readiness, covering the choice among the three rolling deadlines (summer/fall/winter), the separate abstract-registration step, the 20-page single-column acmsmall budget plus unlimited references, double-anonymous review (and the Operational Systems Track exception), track selection, POMACS publication, and desk-reject triage before the AoE cutoff.Votes: 0GitHub stars: 1,052
- Sigmetrics SupplementaryUse when deciding what belongs in an ACM SIGMETRICS paper body versus its appendices and anonymized artifact, covering the 20-page single-column acmsmall budget, the rule that decision-critical claims (theorem statements, assumptions, headline validation) stay inside the reviewed pages, full proofs in appendices, double-anonymous supplementary material, and how to split a proof-plus-measurement paper.Votes: 0GitHub stars: 1,052
- Sigmetrics Topic SelectionUse when deciding whether a computer-systems performance project belongs at ACM SIGMETRICS or should be routed to IMC, SIGCOMM/NSDI/OSDI, INFOCOM, a learning venue (NeurIPS/ICML), or a performance journal (Performance Evaluation/TON/QUESTA), and when picking the right SIGMETRICS track (Theory / Measurement & Applied Modeling / Learning / Operational Systems).Votes: 0GitHub stars: 1,052
- Sigmetrics WorkflowUse when planning an ACM SIGMETRICS project timeline across the three rolling deadlines (summer/fall/winter), from venue fit through abstract registration, submission, shepherding, the one-shot revision round, POMACS publication, and presentation, with backward-planning offsets for a performance-evaluation paper and honest handling of the rolling-deadline cadence and the 12-month resubmission bar.Votes: 0GitHub stars: 1,052
- Sigmetrics Writing StyleUse when revising an ACM SIGMETRICS paper for a rigorously stated performance contribution on the first page, explicit modeling assumptions and their validity, theorems paired with numerical/empirical validation, evidence proportional to the claim, double-anonymous wording, and disciplined use of the 20-page single-column acmsmall budget.Votes: 0GitHub stars: 1,052
- Sigmod Artifact EvaluationUse when preparing a SIGMOD paper's code and data for the Availability & Reproducibility Initiative (ARI), covering the post-acceptance opt-in, HotCRP artifact registration, the Artifacts Available / Artifacts Evaluated / Results Reproduced badges, evaluator criteria, and the Best Artifact award path.Votes: 0GitHub stars: 1,052
- Sigmod Author ResponseUse when writing SIGMOD author feedback during a PACMMOD round or the revision letter after a major/minor-revision verdict, covering the mid-round feedback window, the four-page letter limit, per-reviewer change highlighting, the extra content page, and anonymity that must hold through resubmission.Votes: 0GitHub stars: 1,052
- Sigmod Camera ReadyUse when converting an accepted SIGMOD research paper into its PACMMOD journal version, covering the port from the ACM submission template to PACMMOD format, de-anonymization, per-round issue placement, ACM DL metadata, conference presentation logistics, and the post-acceptance artifact and ARI handoff.Votes: 0GitHub stars: 1,052
- Sigmod ExperimentsUse when designing or auditing the evaluation of a SIGMOD paper, covering workload realism and standard benchmark usage, baseline tuning fairness, scalability and tail-latency methodology, ablations that isolate the mechanism, and the setup disclosure a data-systems PC demands before trusting any speedup.Votes: 0GitHub stars: 1,052
- Sigmod Related WorkUse when positioning a SIGMOD submission against the data-management literature, covering coverage across SIGMOD/PACMMOD, PVLDB, ICDE, TODS, and PODS lines, decades-deep systems history, concurrent papers in rolling venues, industrial-system citations, and PACMMOD's substantial-overlap exclusivity rule.Votes: 0GitHub stars: 1,052
- Sigmod ReproducibilityUse when hardening the reproducibility story of a SIGMOD submission, covering PACMMOD's expectation that code, data, scripts, and notebooks be shared, experiment provenance from config to figure, dataset and workload disclosure, variance reporting for systems numbers, and alignment with later ARI badging.Votes: 0GitHub stars: 1,052
- Sigmod Review ProcessUse when reasoning about how a SIGMOD research paper moves through a PACMMOD round, covering double-anonymous CMT reviewing, the author feedback phase, accept/reject/revision verdicts, the one-month revision window, the 12-month rejection embargo, and how database PC members actually weigh evidence.Votes: 0GitHub stars: 1,052
- Sigmod SubmissionUse when readying a SIGMOD research-track submission for a PACMMOD round, covering the abstract-plus-COI pre-deadline, Microsoft CMT mechanics, the 12-page ACM-template limit, double-anonymous rules, the 10-paper author cap, the 12-month rejection embargo, and desk-reject hazards.Votes: 0GitHub stars: 1,052
- Sigmod SupplementaryUse when deciding what accompanies a SIGMOD submission beyond the 12 pages, covering extended technical reports, anonymized code and data links that survive multi-round review, appendix placement relative to the unlimited reference pages, and what reviewers actually open during a PACMMOD round.Votes: 0GitHub stars: 1,052
- Sigmod Topic SelectionUse when judging whether a project belongs at SIGMOD's research track, comparing it against PVLDB's rolling model, ICDE, PODS, KDD, CIDR, and TODS, weighing the industrial track for deployment papers, and testing whether the contribution is genuinely a data-management result rather than an application that touches data.Votes: 0GitHub stars: 1,052
- Sigmod WorkflowUse when planning a SIGMOD project calendar under the PACMMOD round system, covering round selection and hopping, backward planning from abstract and paper cutoffs, the feedback and revision windows, embargo-aware contingencies, and coordinating a systems-building team against quarterly deadlines.Votes: 0GitHub stars: 1,052
- Sigmod Writing StyleUse when revising a SIGMOD research paper's prose and structure, covering the data-management framing readers expect on page one, running examples and architecture figures, scoping systems claims to measured workloads, third-person anonymity phrasing, and fitting a systems argument into 12 ACM-template pages.Votes: 0GitHub stars: 1,052
- Soda Artifact EvaluationUse when deciding how code, computations, or data attach to a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — SODA itself runs no artifact track, so this skill covers computer-assisted proof evidence, implementation companions, and when to route the artifact to co-located ALENEX's formal artifact evaluation instead.Votes: 0GitHub stars: 1,052
- Soda Author ResponseUse when drafting the SODA (ACM-SIAM Symposium on Discrete Algorithms) rebuttal — the roughly three-day window between review release in early September and the response deadline, triaging referee misreadings versus real gaps, and writing terse theorem-anchored replies inside HotCRP without breaking lightweight double-blind rules.Votes: 0GitHub stars: 1,052
- Soda Camera ReadyUse when converting a SODA (ACM-SIAM Symposium on Discrete Algorithms) acceptance into a correct SIAM proceedings entry — following the October final-version instructions, condensing the no-limit submission into the proceedings version, restoring author identity, syncing the arXiv full version, and planning the January talk.Votes: 0GitHub stars: 1,052
- Soda ExperimentsUse when deciding whether and how experiments belong in a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — SODA's scope includes experimental validation but theorems carry the decision, so this skill designs supporting numerics honestly and routes implementation-led work to co-located ALENEX or to SEA.Votes: 0GitHub stars: 1,052
- Soda Related WorkUse when positioning a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper in the algorithms literature — tracing bound lineages across SODA/STOC/FOCS/ESA/ICALP and journals, handling arXiv-first priority culture, citing conference versus journal versions correctly, and self-citation under lightweight double-blind rules.Votes: 0GitHub stars: 1,052
- Soda ReproducibilityUse when hardening the verifiability of a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper, where reproducibility means checkable mathematics — complete proofs in the submitted full version, stable statement-proof correspondence, explicit constants and model assumptions, and certificates for any machine-checked step.Votes: 0GitHub stars: 1,052
- Soda Review ProcessUse when reasoning about how a SODA (ACM-SIAM Symposium on Discrete Algorithms) submission is evaluated — the per-edition program committee under joint ACM-SIAM sponsorship, HotCRP triage of a record-size submission pool, lightweight double-blind refereeing of full versions, the September rebuttal, and October decisions.Votes: 0GitHub stars: 1,052
- Soda SubmissionUse when preparing or auditing a SODA (ACM-SIAM Symposium on Discrete Algorithms) submission — the no-page-limit full-version norm, the title-page abstract, 11-point single-column letter format, lightweight double-blind rules, HotCRP entry, and the July AoE deadline with its summary-rejection triggers.Votes: 0GitHub stars: 1,052
- Soda SupplementaryUse when organizing the back matter of a SODA (ACM-SIAM Symposium on Discrete Algorithms) submission — there is no supplementary channel, so appendix architecture inside the single no-page-limit PDF does the supplement's job; covers front/back matter split, appendix ordering, and external-archive references.Votes: 0GitHub stars: 1,052
- Soda Topic SelectionUse when deciding whether a result is SODA-shaped (ACM-SIAM Symposium on Discrete Algorithms) — concrete algorithmic problems, data structures, and discrete mathematics with quantitative progress — versus routing to STOC/FOCS, ESA, ICALP, ITCS, SOSA, ALENEX, SoCG, or a journal, judged from SODA's algorithms-first identity.Votes: 0GitHub stars: 1,052
- Soda WorkflowUse when planning a SODA (ACM-SIAM Symposium on Discrete Algorithms) campaign end to end — backward-planning to the July AoE deadline, SODA's seat in the theory calendar between STOC and FOCS deadlines, the September rebuttal and October decision, satellite deadlines (ALENEX, SOSA), and the January conference.Votes: 0GitHub stars: 1,052
- Soda Writing StyleUse when writing or revising a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — headline bounds stated exactly, the title-page abstract that wins bidding, a first-ten-pages overview for triage readers, prior-bound comparison tables, and prose discipline for an uncapped full-version document.Votes: 0GitHub stars: 1,052
- Sosp Artifact EvaluationUse when preparing a SOSP artifact for the post-acceptance evaluation run by the sysartifacts community, registering within days of notification, packaging for the cooperative review process, and targeting the ACM badges — Artifacts Available, Artifacts Evaluated Functional, and Artifacts Evaluated Reusable.Votes: 0GitHub stars: 1,052