菜单
这个仓库中的 skills
SkillsMP 已收集 brycewang-stanford/Awesome-Journal-Skills 中的 3,969 个 Skill。打开任一 Skill 可查看来源和详情。
brycewang-stanford/Awesome-Journal-Skills已展示 40 / 3,969 个已收集 Skill。
Use when revising a USENIX FAST paper for a storage contribution on the first page, a design/mechanism narrative a storage reviewer can follow, an evaluation framed as the storage cost it changes (write amplification, tail latency, endurance, crash…
原文语言：英语
Use to understand why ICALP (EATCS) has no artifact-evaluation track or badge scheme, and what plays the equivalent role for a pure-theory paper — the full version with complete proofs, reproducible computational certificates, and optional machine…
原文语言：英语
Use when writing an ICALP (EATCS) Track B rebuttal in response to initial reviews, or when handling a Track A correctness query — correcting reviewer misreadings of a proof, pointing to the exact lemma or step that answers an objection, conceding real gaps…
原文语言：英语
Use when preparing an accepted ICALP (EATCS) paper for the LIPIcs open-access camera-ready — converting to the lipics-v2021 document class, de-anonymizing (restoring authors, affiliations, ORCIDs, acknowledgements, and funding), completing LIPIcs metadata…
原文语言：英语
Use when matching the argument of an ICALP (EATCS) theory paper to its claim — choosing the proof strategy for an upper or lower bound, deciding when supporting computation (SAT/SMT-verified base cases, computer-assisted case analysis, exhaustive small-case…
原文语言：英语
Use when writing the related-work and positioning of an ICALP (EATCS) theory paper — comparing against the best known bounds in the TCS literature, crediting the right prior venues (STOC/FOCS/SODA/LICS/CCC and TCS journals), stating the delta precisely, and…
原文语言：英语
Use when making an ICALP (EATCS) theory result independently checkable — writing complete, self-contained proofs in the appendix and a full version (arXiv/ECCC/HAL), pinning any computational steps to reproducible certificates, and (optionally) formalizing…
原文语言：英语
Use when reasoning about how an ICALP (EATCS) submission is evaluated, covering lightweight double-blind review, the separate Track A and Track B program committees, the asymmetric author interaction (Track B rebuttal vs Track A correctness-only contact),…
原文语言：英语
Use when auditing an ICALP (EATCS) Track A or Track B submission for HotCRP readiness, covering the correct-track submission server, abstract registration before the full-paper deadline, the 15-page extended-abstract page budget with a clearly labelled…
原文语言：英语
Use when splitting an ICALP (EATCS) theory paper between the 15-page main body and the clearly labelled appendix / full version — deciding what a referee must see in the body versus what may be deferred, ensuring every deferred proof is actually present and…
原文语言：英语
Use when deciding whether a theoretical computer science result belongs at ICALP (EATCS) and, if so, whether it is a Track A (algorithms, complexity, games) or Track B (automata, logic, semantics, theory of programming) paper, and when distinguishing ICALP…
原文语言：英语
Use when planning an ICALP (EATCS) campaign backward from its single annual February deadline, through abstract registration, the anonymous submission, the Track B rebuttal window, the April notification, and the LIPIcs camera-ready and presentation, and when…
原文语言：英语
Use when shaping the exposition of an ICALP (EATCS) theory paper — stating the model before the theorem, putting a legible theorem statement and its improvement over prior bounds on the first page, structuring the 15-page body around the argument while full…
原文语言：英语
Use when packaging an IEEE PerCom sensing artifact and dataset for reproducibility and any badging (IEEE Open Research Objects / Results Reproduced, IEEE DataPort or Zenodo deposit), covering what a ubicomp evaluator checks first for human-subjects sensing…
原文语言：英语
Use when drafting an IEEE PerCom rebuttal after being invited following the initial reviews, covering the bounded single-round reply that answers explicit reviewer questions, corrects misreadings, points to evidence already in the paper without promising new…
原文语言：英语
Use when preparing an accepted IEEE PerCom paper for its IEEE Xplore camera-ready, covering de-anonymization, the IEEEtran compsocconf template and page budget, IEEE Xplore metadata (PDF eXpress, eCopyright, ORCID, index terms), integrating reviewer-required…
原文语言：英语
Use when designing or auditing IEEE PerCom empirical evaluations, covering real human subjects, leave-one-subject-out / cross-subject evaluation, F1 and event-level metrics on imbalanced activity classes, deployment realism (free-living vs. lab), fair…
原文语言：英语
Use when positioning an IEEE PerCom submission against the pervasive/ubiquitous-computing literature across PerCom, ACM UbiComp/IMWUT, MobiCom, MobiSys, SenSys, and IPSN, writing delta-first contrast rather than a citation catalog, keeping self-citations…
原文语言：英语
Use when strengthening IEEE PerCom reproducibility and open-data evidence for human-subjects sensing, covering the dataset-availability statement, de-identified datasets with IRB/consent handling, sensing provenance (devices, sampling, labeling),…
原文语言：英语
Use when reasoning about how an IEEE PerCom research submission is evaluated, covering double-blind review, the three-TPC-member model, the early-rejection stage, the single-round bounded rebuttal gated by a "weak accept," the accept/reject decision, and how…
原文语言：英语
Use when auditing an IEEE PerCom research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the IEEEtran 9+1 two-column page budget, double-blind anonymization, the open-data / human-subjects plan, IEEE Xplore publication,…
原文语言：英语
Use when deciding what belongs in an IEEE PerCom paper body versus its dataset/artifact and any appendix, covering the tight IEEEtran 9+1 page budget, the rule that decision-critical evidence stays inside the reviewed pages, double-blind supplementary…
原文语言：英语
Use when deciding whether a pervasive-computing project belongs at IEEE PerCom or should be routed to ACM UbiComp/IMWUT, MobiCom, MobiSys, SenSys, or IPSN, and when distinguishing PerCom's human-centric ubicomp focus from networked-sensor-systems venues by…
原文语言：英语
Use when planning an IEEE PerCom project timeline from venue fit through paper registration, the September submission, the early-rejection gate, the bounded rebuttal, the IEEE Xplore camera-ready, and in-person presentation, with backward-planning offsets for…
原文语言：英语
Use when revising an IEEE PerCom paper for a pervasive-computing contribution on the first page, cross-subject claims stated precisely, a limitations section that argues rather than recites, evidence proportional to the claim, double-blind wording, and…
原文语言：英语
Use when an author expects an artifact-evaluation or badge track at ACM PODC and needs redirecting — PODC has NO artifact track and no ACM badges. This skill converts artifact-culture instincts into what PODC actually evaluates: proof-appendix completeness,…
原文语言：英语
Use when writing an ACM PODC rebuttal/author response, if the cycle runs one — covering how to correct a proof misreading, supply a missing lemma or bound within the anonymity envelope, prioritize soundness questions over taste, and behave correctly given…
原文语言：英语
Use when preparing an accepted ACM PODC paper for the proceedings — de-anonymizing after lightweight double-blind, compressing to the 10-page two-column ACM proceedings format without losing the proof map, completing ACM rights/eRights metadata and CCS…
原文语言：英语
Use when building the evidence for an ACM PODC paper — where "evidence" is a proof, not a benchmark. Covers matching upper and lower bounds, tightness arguments, model and assumption stress-tests, adversary-strength calibration, and the honest,…
原文语言：英语
Use when writing the related-work and positioning of an ACM PODC paper — covering the distributed-computing literature lanes (PODC/DISC/SPAA and the JACM / Distributed Computing journals), writing a model-and-bound-precise delta over prior results,…
原文语言：英语
Use when making an ACM PODC paper's result independently checkable — reproducibility for a proofs venue, not an artifact venue. Covers a self-contained proof appendix, an explicit and checkable model/assumption box, honest handling of any optional simulation,…
原文语言：英语
Use when reasoning about how an ACM PODC submission is evaluated — covering lightweight double-blind review, a program committee that reads proofs, the accept/reject decision with no journal-style revision round, the Brief Announcements track's lighter bar,…
原文语言：英语
Use when auditing an ACM PODC submission for HotCRP readiness, covering the two-step abstract-registration then full-paper deadline, the ACM Master template with the 10-page-merits budget and unbounded full version, lightweight double-blind anonymization, the…
原文语言：英语
Use when deciding what goes in the first 10 read-guaranteed pages of an ACM PODC submission versus the full version / appendix, and when choosing between a regular paper and a Brief Announcement — so that nothing which decides acceptance lives past page 10…
原文语言：英语
Use when deciding whether a distributed-computing result belongs at ACM PODC or should be routed to DISC, SPAA, OPODIS/SIROCCO/SSS, STOC/FOCS/SODA, a systems venue (ICDCS/DSN/OSDI/NSDI), a blockchain-theory venue (AFT/FC), or a journal (JACM / Distributed…
原文语言：英语
Use when planning an ACM PODC campaign end to end — running the single annual cycle backward from the February deadline through abstract registration, lightweight double-blind review, the late-April notification, the May camera-ready, and the arXiv full…
原文语言：英语
Use when drafting or revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box, the result stated as a theorem up front, a proof architecture the reader can navigate, and the 10-page-merits discipline) so the…
原文语言：英语
Use when packaging a PPoPP artifact for the post-acceptance, CGO-shared artifact-evaluation track, covering PPoPP's specific badge policy (Functional or Reusable plus Results Reproduced, no "Results Replicated"; Available granted by the publisher from a…
原文语言：英语
Use when writing a PPoPP author-response rebuttal, covering the short fixed word-capped window, answering the recurring "does it scale?" and "what about baseline X?" questions with pre-run numbers, correcting factual misreadings of a concurrency argument,…
原文语言：英语
Use when preparing a PPoPP camera-ready, covering systematic de-anonymization, ACM rights/eRights and CCS concepts metadata, restoring the named hardware and acknowledgements, permanentizing the artifact DOI and any earned badges, and passing ACM production…
原文语言：英语