メニュー
このリポジトリの skills
SkillsMP は brycewang-stanford/Awesome-Journal-Skills から 3,969 件の skill を収集しています。skill を開くとソースと詳細を確認できます。
brycewang-stanford/Awesome-Journal-Skills収集済み skill 3,969 件中 40 件を表示しています。
Use when reasoning about how a NAACL decision actually gets made — the division of labor between ACL Rolling Review (reviews, meta-review) and the NAACL program committee (commitment-stage acceptance into Main or Findings), where author leverage exists at…
原文の言語: 英語
Use when a paper aimed at NAACL is about to be uploaded to an ACL Rolling Review cycle — verifying that the chosen cycle can still reach the next NAACL edition, that the PDF passes ARR's format and anonymization gates, and that every declaration on the…
原文の言語: 英語
Use when deciding what goes into the content pages, the uncounted sections, the appendix, and the optional uploads of a NAACL-bound ARR submission — allocating material by what reviewers are actually obliged to read, and keeping glossed language examples and…
原文の言語: 英語
Use when deciding whether a project should target NAACL rather than ACL, EMNLP, EACL, AACL, LREC-COLING, TACL, or an ML venue — weighing the chapter's Nations-of-the-Americas identity, theme tracks, timing across skipped years, and whether the paper's…
原文の言語: 英語
Use when planning a research project's calendar toward NAACL — handling the chapter's skipped-year rhythm, choosing an ARR cycle when the edition's feeding cycles are not yet announced, backward-planning data and annotation work, and keeping a decision tree…
原文の言語: 英語
Use when revising the prose of a NAACL submission — scoping every claim to the languages and varieties actually tested, presenting non-English examples with glosses that carry the argument, writing a Limitations section that anticipates reviewers, and cutting…
原文の言語: 英語
Use when preparing an NDSS artifact for evaluation after conditional acceptance — targeting the Available, Functional, and Reproduced badges, packaging attacks and measurements responsibly, writing the 2-page artifact appendix, and handling dangerous or…
原文の言語: 英語
Use when writing an NDSS rebuttal and working the interactive discussion phase — triaging Round-2 reviews under a short window, answering adaptive-attack and ethics objections with pointable evidence, and negotiating toward Accept or a well-scoped Minor/Major…
原文の言語: 英語
Use when converting an accepted NDSS paper into the final open-access version — satisfying Minor/Major Revision conditions, de-anonymizing, restoring disclosure specifics, adding earned artifact badges, and meeting the Internet Society proceedings and…
原文の言語: 英語
Use when designing or auditing the evaluation of an NDSS paper — attack demonstrations, defense evaluations under adaptive adversaries, and Internet measurements — choosing between testbed, emulation, and live experiments and meeting NDSS's deployment-realism…
原文の言語: 英語
Use when positioning an NDSS submission against prior literature — sweeping the security big four plus the specialist venues, writing precise deltas, verifying every citation against NDSS's open proceedings and dblp, and keeping self-reference double-blind.
原文の言語: 英語
Use when making an NDSS paper's results reconstructible — snapshotting live-network observations, pinning testbeds and toolchains, scrubbing traces that carry identities, and writing honest availability statements when ethics or vendor embargoes limit release.
原文の言語: 英語
Use when interpreting where an NDSS submission stands — the two-round pipeline inside each cycle, the early reject with Round-1 reviews, rebuttal and interactive discussion, the Accept / Minor Revision / Major Revision decision set, and the Ethics Review…
原文の言語: 英語
Use when performing the final pre-upload audit of an NDSS submission — HotCRP fields, the AoE deadline, NDSS template and 13-page compliance, double-blind sweep, ethics readiness, the six-per-author cap, overlap rules, and desk-reject triage in the last week.
原文の言語: 英語
Use when dividing an NDSS paper between the 13-page body, the Ethics Considerations section, references, and appendices — deciding what reviewers must see in-body, what the page-limit exclusions really buy, and how the camera-ready gains a 2-page artifact…
原文の言語: 英語
Use when deciding whether a security project belongs at NDSS — the Network and Distributed System Security Symposium — or should route to IEEE S&P, USENIX Security, CCS, PETS, IMC, or ACSAC, applying NDSS's networked-adversary and deployment-realism tests…
原文の言語: 英語
Use when planning an NDSS submission calendar — choosing between the summer and fall cycles, backward-planning from the AoE deadline through early-reject, rebuttal, notification, camera-ready, and the Seoul symposium, and placing NDSS honestly inside the…
原文の言語: 英語
Use when drafting or revising an NDSS paper's prose — building the first page around a capability-bounded networked adversary, sizing claims to evidence, weaving the ethics signal into the narrative, and fitting the argument into NDSS's 13-page body ahead of…
原文の言語: 英語
Use when preparing an accepted NSDI paper's artifact for badge evaluation — packaging code, traces, and testbed recipes for the AEC, choosing which badges to pursue, meeting Zenodo-style permanence expectations, and timing public release to stay eligible for…
原文の言語: 英語
Use when answering NSDI reviewers through the channel the venue actually provides — executing a one-shot revision against the required-issues list, writing the change memo and highlighted diff for the same reviewers, and pre-empting objections inside the…
原文の言語: 英語
Use when converting an NSDI acceptance into a published, presented paper — de-anonymizing within the same 12-page cap, meeting the final-papers deadline that also gates Community Award eligibility, designating the presenter, and landing in USENIX's…
原文の言語: 英語
Use when designing or auditing the evaluation of an NSDI submission — choosing traces, testbeds, and deployment evidence, sizing scale and failure-injection experiments, picking baselines that fight back, and reporting tail behavior so networked-systems…
原文の言語: 英語
Use when positioning an NSDI submission against the networked-systems literature — covering the NSDI/SIGCOMM/OSDI/SOSP lanes plus both accepted-paper cohorts of the current edition, verifying venues against dblp and open-access USENIX proceedings, and…
原文の言語: 英語
Use when making an NSDI paper's results reconstructible — capturing testbed topology, trace provenance, and configuration while experiments run, planning which datasets can ship publicly, and keeping the paper and artifact from drifting apart so badge…
原文の言語: 英語
Use when interpreting where an NSDI submission stands — the per-deadline PC pipeline, the three-way outcome space of accept, one-shot revision, and reject, the cross-deadline resubmission ban, reviewer continuity across revisions, and what each decision…
原文の言語: 英語
Use when running the final pre-upload audit of an NSDI submission — the abstract-then-paper week on the per-deadline HotCRP site, 11:59 pm US Eastern cutoffs, the 12-page cap with references and appendices outside it, track-dependent anonymization, the…
原文の言語: 英語
Use when splitting NSDI material across the 12-page body, the appendix pages the CFP allows beyond references, HotCRP auxiliary-material uploads for critical online content, and the one-shot-revision packet — deciding what reviewers must see in-body versus…
原文の言語: 英語
Use when judging whether a project belongs at NSDI, picking among its research, operational-systems, and frontiers tracks, or re-routing to SIGCOMM, OSDI, SOSP, FAST, or SIGMETRICS — testing the networking-stack contribution, the CFP's out-of-scope lines, and…
原文の言語: 英語
Use when planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates, notification waits, one-shot revision windows, artifact evaluation, and the May symposium — so a networked-systems project always knows which of the…
原文の言語: 英語
Use when drafting or revising NSDI prose — building the operational-pain-to-design-principle arc, fitting argument and figures into 12 pages with references and appendices outside the cap, calibrating claims to trace and testbed evidence, and writing for…
原文の言語: 英語
Use when packaging a PLDI artifact for the post-acceptance evaluation — earning the Functional, Reusable, and Available badges, archiving a DOI-stamped snapshot on Zenodo, containerizing toolchains and benchmark suites, and writing a README an evaluator can…
原文の言語: 英語
Use when drafting a PLDI author response inside the short February window — triaging reviewer objections about soundness, baselines, and benchmark validity, correcting factual errors with pointers into the submitted PDF, and committing to feasible revisions…
原文の言語: 英語
Use when turning an accepted PLDI paper into its PACMPL Issue PLDI article — de-anonymization, acmsmall journal formatting, ACM rights and open-access handling, delivering every author-response commitment, and coordinating the Zenodo artifact and June…
原文の言語: 英語
Use when designing or auditing a PLDI evaluation — choosing defensible benchmark suites and baseline compiler configurations, measuring runtime, compile time, and memory with warmup and variance discipline, running ablations that isolate the claimed…
原文の言語: 英語
Use when positioning a PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line, covering the last few PLDI/POPL/OOPSLA/ICFP cycles, citing PACMPL-era papers in journal form, and verifying every venue attribution…
原文の言語: 英語
Use when hardening a PLDI paper's measurements against the SIGPLAN Empirical Evaluation Guidelines — warmup and steady-state discipline, variance and confidence reporting, principled benchmark choice, pinned toolchains, cross-platform validity, and a…
原文の言語: 英語
Use when interpreting PLDI's review pipeline — double-blind HotCRP reviewing by a PL-implementor PC, the February author-response window, March notification, up-to-10% Distinguished Paper selection, and how post-acceptance artifact evaluation and PACMPL…
原文の言語: 英語
Use when auditing a PLDI submission for HotCRP readiness — the single annual November deadline, the 20-pages-of-text-excluding-bibliography cap in single-column acmsmall format, double-blind hygiene across tool names and repositories, dual-submission rules,…
原文の言語: 英語
Use when deciding what accompanies a PLDI submission beyond the 20 text pages — full proofs, extended benchmark data, anonymized code — and how to keep every extra byte double-blind, optional for reviewers, and consistent with the main PDF under…
原文の言語: 英語
Use when deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence — or better routed inside the PACMPL family to POPL, OOPSLA, or ICFP, or outward to ASPLOS, CGO, CAV, ICSE/FSE, or a systems venue, based on where the…
原文の言語: 英語