stoc-skills

Plugin stoc-skills from marketplace awesome-journal-skills in brycewang-stanford/Awesome-Journal-Skills. Commands read from the repo's manifest — 1 month ago.

Skills (12)

• stoc-artifact-evaluation

  Use when deciding what evidence objects a STOC (ACM Symposium on Theory of Computing) paper must ship, given that STOC runs no artifact-evaluation track — the durable artifact is the public full version on arXiv/ECCC, plus verifiable certificates whenever a proof leans on computation, and optional m

• stoc-author-response

  Use when planning author-side communication for a STOC (ACM Symposium on Theory of Computing) submission, where no standing rebuttal phase exists — covering pre-emptive writing that answers objections in advance, chair-mediated technical clarifications if the PC asks, and the FOCS resubmission lette

• stoc-camera-ready

  Use when converting a STOC (ACM Symposium on Theory of Computing) acceptance into publishable form — the ACM proceedings version, de-anonymization, rights forms, the CFP-level expectation that the full paper with proofs goes public on arXiv or ECCC by the camera-ready deadline, and TheoryFest talk p

• stoc-experiments

  Use when judging whether computation belongs in a STOC (ACM Symposium on Theory of Computing) paper at all — STOC accepts on theorems, with no empirical-evaluation expectation — and when it does, scoping it as certified proof computation, constructive search, or clearly labeled illustration rather t

• stoc-related-work

  Use when positioning a STOC (ACM Symposium on Theory of Computing) paper against the theory literature — tracing bound-improvement lineages, citing conference/journal/preprint version pairs correctly, handling concurrent arXiv and ECCC work, and keeping self-citation double-blind-safe.

• stoc-reproducibility

  Use when hardening a STOC (ACM Symposium on Theory of Computing) paper so its results can be independently checked — proof completeness across the extended-abstract/full-version split, single-source builds that prevent statement drift between the two documents, and determinism for any computation a

• stoc-review-process

  Use when reasoning about how a STOC (ACM Symposium on Theory of Computing) submission is evaluated — the SIGACT program-committee model with external subreviewers, HotCRP mechanics, double-blind conflicts, the November-to-February decision arc, and what best-paper designation and rejection each actu

• stoc-submission

  Use when auditing a STOC (ACM Symposium on Theory of Computing) submission for HotCRP readiness — the abstract + table-of-contents + first-12-pages reading rule, single-column 11-point format, double-blind hygiene, the SIGACT prior/simultaneous-publication policy, and deadline-week sequencing before

• stoc-supplementary

  Use when architecting everything beyond the first twelve pages of a STOC (ACM Symposium on Theory of Computing) submission — the discretionary-read appendix, the reviewed table of contents, theorem-to-proof pointer discipline, and the division of labor between the submission appendix and the arXiv/E

• stoc-topic-selection

  Use when deciding whether a result belongs at STOC (ACM Symposium on Theory of Computing) — testing for broad theory-of-computation significance versus routing to FOCS, SODA, CCC, ITCS, COLT, CRYPTO, PODC, SoCG, EC, or a journal like JACM/SICOMP when the fit is specialized, conceptual, or empirical.

• stoc-workflow

  Use when planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline, the STOC/FOCS alternating two-deadline year that theory groups schedule around, full-version and camera-ready milestones, and the June TheoryFest endpoint.

• stoc-writing-style

  Use when drafting or revising a STOC (ACM Symposium on Theory of Computing) paper — the theorem-forward first page, informal/formal statement pairing, the technical-overview section that carries acceptance, notation economy for a cross-area committee, and prose that survives the twelve guaranteed pa

Similar plugins