メニュー
このリポジトリの skills
SkillsMP は brycewang-stanford/Awesome-Journal-Skills から 3,969 件の skill を収集しています。skill を開くとソースと詳細を確認できます。
brycewang-stanford/Awesome-Journal-Skills収集済み skill 3,969 件中 40 件を表示しています。
Use when auditing an ACM CCS submission for HotCRP readiness, dual-cycle abstract registration and full-paper deadlines, the 12-page ACM sigconf body, anonymization, the ethics considerations appendix, artifact-availability posture, dual-submission policy,…
原文の言語: 英語
Use when preparing ACM CCS appendices and supplementary material, including the ethics considerations appendix, protocol transcripts, formal proofs, measurement tables, and anonymized supporting material under the 12-page body limit, anonymity, and…
原文の言語: 英語
Use when deciding whether a security project fits ACM CCS versus IEEE S&P, USENIX Security, NDSS, PETS, or a crypto/theory venue, identifying the security contribution type, and sharpening the threat model and attacker capability before writing begins.
原文の言語: 英語
Use when planning an ACM CCS project timeline across the two HotCRP review cycles, from venue fit through abstract registration, full-paper upload, rebuttal, notification, revision, artifact evaluation, ACM camera-ready, and in-person presentation, with…
原文の言語: 英語
Use when revising an ACM CCS paper for a precise threat model, calibrated attack/defense claims, 12-page ACM sigconf compression, double-blind wording, adaptive-evaluation honesty, and the security house style that survives an adversarial SIGSAC program…
原文の言語: 英語
Use when packaging the artifacts behind an ACM CHI paper — prototypes, study instruments, codebooks, datasets, analysis code — for anonymous review scrutiny and for post-acceptance archival release, in a venue with no formal artifact-evaluation committee…
原文の言語: 英語
Use when an ACM CHI paper receives a revise-and-resubmit invitation and the five-week window opens — planning the revision triage, making tracked changes reviewers can audit, and writing the response letter that carries the paper through round 2 and the PC…
原文の言語: 英語
Use when preparing an accepted ACM CHI paper for publication — the TAPS source upload, the PCS publication-ready package, mandatory accessibility work (alt text, screen-reader-friendly PDFs, table headers), video previews, ACM's open-access model, e-rights,…
原文の言語: 英語
Use when designing or auditing the studies behind an ACM CHI paper — matching evidence shape to contribution type, powering quantitative experiments, making qualitative work rigorous and auditable, reporting participants and ethics properly, and avoiding the…
原文の言語: 英語
Use when building the related-work section of an ACM CHI paper — covering the HCI venue family and the non-CS disciplines CHI draws on, positioning against the last few CHI cycles, keeping self-citation anonymous — in a venue where insufficient…
原文の言語: 英語
Use when strengthening research transparency for an ACM CHI paper — protocols, instruments, codebooks, analysis scripts, preregistration, and data availability under human-subjects constraints — so methods survive the ADR-Method screening and others can…
原文の言語: 英語
Use when interpreting the ACM CHI Papers review pipeline — 1AC and 2AC roles, the A/ARR/RR/RRX/X recommendation scale, desk-reject and rubric-based assisted desk-reject screening, the revise-and-resubmit threshold, round-2 PC decisions — and what each stage…
原文の言語: 英語
Use when auditing an ACM CHI Papers submission for PCS readiness, covering the September full-paper deadline, the anonymized single-column template, word-count norms instead of page limits, subcommittee designation, supplementary and video upload,…
原文の言語: 英語
Use when assembling supplementary materials for an ACM CHI submission — the video figure with mandatory closed captions, appendices, study instruments, code and data archives — all due with the paper on the single September deadline, anonymized end to end,…
原文の言語: 英語
Use when deciding whether a project belongs at ACM CHI, which of CHI's contribution types it makes, and which reviewing subcommittee should judge it — or whether the work is better routed to UIST, CSCW, DIS, IUI, ASSETS, IMWUT, or TOCHI before any drafting…
原文の言語: 英語
Use when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the TAPS and publication-ready chain, and the May conference — with owners and risk…
原文の言語: 英語
Use when drafting or revising the prose of an ACM CHI paper — contribution statements, structure for mixed reviewer audiences, participant voice, calibrated claims, accessible and bias-free writing, and length discipline in a venue that reviews words against…
原文の言語: 英語
Use when preparing an artifact for the ICSE Artifact Evaluation track after paper acceptance, covering the ACM badge system (Available, Reusable, Results Reproduced/Replicated), evaluator-proof packaging, archival requirements, open licensing, and the…
原文の言語: 英語
Use when drafting an ICSE author response or executing a Major Revision, covering criterion-targeted replies to research-track reviews, the September response window, the four-week revision sprint to the November deadline, response-letter structure, and…
原文の言語: 英語
Use when converting an accepted ICSE research-track paper into its final published form, covering the extra camera-ready page, de-anonymization order, finalizing the Data Availability section with archival DOIs, IEEE-template production checks, and…
原文の言語: 英語
Use when designing or auditing the evaluation of an ICSE research-track paper, covering subject and benchmark selection, baseline fairness, statistical tests and effect sizes as SE reviewers expect them, qualitative-methods rigor, ablations for AI-based…
原文の言語: 英語
Use when building the related-work and positioning sections of an ICSE research-track paper, covering the literature lanes SE reviewers check, searching ACM DL, IEEE Xplore and dblp across the flagship venues, staying current in fast-moving areas like LLM4SE,…
原文の言語: 英語
Use when building the verifiability story of an ICSE research-track paper, covering the open-science policy's sharing-by-default expectation, the Data Availability section, anonymized replication packages at review time, provenance pinning for mining and LLM…
原文の言語: 英語
Use when reasoning about how an ICSE research-track submission is evaluated, covering double-anonymous PC review, the four posted criteria, the Accept / Major Revision / Reject decision model, the revision-and-final-decision timeline, and what recent ICSE…
原文の言語: 英語
Use when auditing an ICSE research-track submission for HotCRP readiness, covering the mandatory abstract deadline, the 10-page-plus-2-reference-page IEEE format, double-anonymous rules, the open-science Data Availability section, supplementary uploads, and…
原文の言語: 英語
Use when deciding what goes into the 10-page body versus the replication package of an ICSE research-track submission, covering the no-unlimited-appendix page model, anonymized supplementary links and HotCRP uploads, package organization for reviewer…
原文の言語: 英語
Use when deciding whether a software-engineering project belongs in the ICSE research track or should be routed to FSE, ASE, ISSTA, MSR, ICSME, EMSE/TSE/TOSEM, or an ICSE co-located track such as NIER, SEIP, SEIS, or Demonstrations, based on contribution…
原文の言語: 英語
Use when planning an ICSE research-track campaign end to end, covering the single-cycle calendar from the June abstract deadline through September response, October decisions, the November revision sprint, artifact evaluation, camera-ready, and the April…
原文の言語: 英語
Use when writing or revising an ICSE research-track paper, covering empirical-SE paper anatomy, research questions as the load-bearing structure, the threats-to-validity section the community expects, practitioner-grounded motivation, calibrated claims, and…
原文の言語: 英語
Use when preparing an IEEE S&P (Oakland) artifact-evaluation submission after acceptance, including choosing among the Available, Functional, and Results Reproduced badges, DOI-backed deposits, packaging exploits and malware-adjacent code responsibly, and…
原文の言語: 英語
Use when drafting the IEEE S&P (Oakland) rebuttal for second-round papers or the response plan for a Revise decision, including triaging reviews under the ~5-day window, answering adaptive-attack and threat-model objections, handling ethics questions with…
原文の言語: 英語
Use when converting an IEEE S&P (Oakland) acceptance into a final paper, including working the shepherd against the draft meta-review's concern list, adding the ethics section, de-anonymizing and restoring disclosure specifics, IEEE compsoc and Xplore…
原文の言語: 英語
Use when designing or auditing the evaluation of an IEEE S&P (Oakland) paper, including end-to-end attack demonstration, adaptive-adversary evaluation of defenses, measurement sampling and validity, baselines and ablations, statistical reporting of attack…
原文の言語: 英語
Use when positioning an IEEE S&P (Oakland) paper against prior literature, including coverage across the four security flagships, concurrent-work and arXiv norms, the 40% resubmission-overlap disclosure, verifying venue attribution via dblp and IEEE Xplore,…
原文の言語: 英語
Use when hardening the reproducibility of an IEEE S&P (Oakland) paper's evidence before submission, including environment pinning for exploits and side channels, seed and trial reporting for probabilistic attacks, measurement snapshotting of live systems, and…
原文の言語: 英語
Use when reasoning about IEEE S&P (Oakland) peer review, including the rounds inside each cycle, early-reject notices, the rebuttal for second-round papers, the Accept/Revise/Reject decision set, the Research Ethics Committee, shepherding of accepted papers,…
原文の言語: 英語
Use when auditing an IEEE S&P (Oakland) submission for HotCRP readiness, including the registration freeze with ORCID matching, the 13-page/18-page compsoc format, anonymization, the Ethics Considerations field, SoK checkbox, conflict declarations, and the…
原文の言語: 英語
Use when deciding what goes in an IEEE S&P (Oakland) paper's appendix versus the 13-page body, including the 5-page references-and-appendices allowance, the rule that reviewers need not read appendices, marking requirements past page 13, and what must never…
原文の言語: 英語
Use when deciding whether a security or privacy project belongs at IEEE S&P (Oakland), including the threat-model test, SoK fit, routing among USENIX Security, CCS, NDSS, PETS, and CRYPTO, and whether the one-year resubmission embargo or the 40% overlap rule…
原文の言語: 英語
Use when planning an IEEE S&P (Oakland) submission calendar across the two-cycle year, including registration-versus-paper deadlines, the early-reject and rebuttal windows, Revise resubmission timing, the one-year embargo clock, and choosing which cycle a…
原文の言語: 英語