Menu
Skills in this repository
SkillsMP has collected 3,969 skills from brycewang-stanford/Awesome-Journal-Skills. Open a skill to review its source and details.
brycewang-stanford/Awesome-Journal-SkillsShowing 40 of 3,969 collected skills.
Use when hardening a CVPR paper's reproducibility story, covering the Compute Reporting Form's hardware and compute sections, training-recipe disclosure, benchmark protocol and split hygiene, seed and variance reporting for vision experiments, and closing the…
Use when reasoning about how CVPR review actually works at 16,000-submission scale, covering the OpenReview pipeline and timeline, reviewer-duty enforcement and desk rejects, the reviewer LLM ban, AC and discussion dynamics, oral/highlight/poster decision…
Use when auditing a CVPR submission before the OpenReview deadline, covering abstract registration and profile requirements, the 8-page limit including figures and tables, the Compute Reporting Form, anonymity and external-link bans, dual-submission…
Use when deciding what belongs in a CVPR supplementary upload versus the 8-page body, covering the one-week-later supplement deadline, video and qualitative-result norms in computer vision, anonymous code packaging, the no-external-links rule, and keeping…
Use when deciding whether a project belongs at CVPR or should route elsewhere, covering what counts as a vision contribution at the field's flagship, fit tests for methods, datasets, and application papers, realistic odds at 25% acceptance and 16k…
Use when planning a CVPR submission campaign end to end, covering the November abstract/paper/supplement deadline chain, coauthor reviewer-duty scheduling, the January rebuttal sprint, February decisions, camera-ready and June conference logistics, and the…
Use when writing or revising a CVPR paper's prose and figures, covering the 8-page budget where figures and tables count against the limit, the page-1 teaser figure convention, benchmark-table craft, claim calibration for a skeptical vision audience, and…
Use 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,…
Use 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…
Use 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…
Use 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…
Use 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…
Use 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…
Use 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…
Use 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…
Use 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…
Use when packaging datasets, models, or code for the Web Conference (WWW) Artifacts Available badge or for reviewer scrutiny, covering archival-repository choice, the light-verification bar, web-data licensing and takedown realities, anonymized artifacts…
Use when drafting the Web Conference (WWW) rebuttal inside its one-week window, triaging reviews from the venue's mixed systems/mining/social-science reviewer pool, answering misread-track objections, protecting anonymity, and deciding what can honestly be…
Use when preparing a Web Conference (WWW) camera-ready after acceptance, covering the uniform 12-page/8-content proceedings budget, de-anonymization and restored acknowledgements, ACM e-rights and TAPS production, ACM Open cost exposure, author registration,…
Use when designing or auditing the empirical section of a Web Conference (WWW) paper — matching evidence to the claim's scale, choosing datasets with provenance and freshness, blocking temporal and popularity leakage, running honest baselines from the sibling…
Use when positioning a Web Conference (WWW) submission against prior literature — tracing lineage through three decades of WWW proceedings, contrasting with the WSDM/CIKM/SIGIR/KDD sibling circuit, handling the venue's preprint-non-citation rule, and…
Use when hardening the reproducibility of a Web Conference (WWW) paper whose evidence rests on crawls, platform APIs, live systems, or user logs — covering dataset decay, temporal snapshots, seed and environment reporting, the reproducibility appendix inside…
Use when reasoning about how the Web Conference (WWW) evaluates papers — track-scoped double-blind review, the rebuttal-to-notification pipeline, how the ten research tracks shape reviewer expectations, main versus companion proceedings outcomes, and what…
Use when auditing a Web Conference (WWW) research-tracks submission before the abstract or full-paper deadline, covering track choice among the ten research tracks, the single-PDF 8+references+appendix page arithmetic within 12 pages, EasyChair profile…
Use when deciding what belongs in the Web Conference (WWW) appendix versus the 8 main pages versus an external artifact, under the single-PDF 12-page ceiling where references and appendix share the tail, reviewers need not read past page 8, and no separate…
Use when deciding whether a project belongs at the Web Conference (WWW) at all, which of the ten research tracks should review it, whether the short-paper or Web4Good lane fits better, and when the work should instead route to WSDM, SIGIR, CIKM, KDD, ICWSM,…
Use when planning a team's calendar around the Web Conference (WWW) annual cycle — the autumn abstract/paper deadlines, the holiday-week rebuttal, January decisions, the short-paper and Web4Good fallback windows inside the same edition, venue-volatility…
Use when drafting or revising a Web Conference (WWW) paper's prose — building the web-native framing that answers "why is this a WWW paper" on page one, writing for a mixed computing/social-science/economics readership, compressing into 8 self-contained…
Use 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…
Use 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,…
Use 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…
Use 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…
Use 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,…
Use 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…
Use 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…
Use 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,…
Use 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…
Use when deciding whether a project belongs at WSDM or a neighbor - tests for the web/social-data core and the practical-yet-principled bar, scope coverage from web search and recommendation to social networks and responsible web AI, routing against SIGIR,…
Use when planning the calendar for a WSDM submission - the single annual cycle from August abstract and paper deadlines through October notification to the February conference, backward milestone planning, the September short-paper fallback, alternate…
Use when drafting or revising prose for a WSDM paper - the practical-yet-principled register, user-and-platform-grounded framing, self-containment writing for a no-rebuttal review, ethical-considerations craft, limitation sentences that protect borderline…