socc-submission
Use when auditing an ACM SoCC (Symposium on Cloud Computing) research-paper submission for HotCRP readiness, covering the two-round abstract+paper deadlines, the acmart/sigconf 12-page (full) or 6-page (short) budget with unlimited references, dual-anonymous review, the systems-and-data reproducibility posture, and desk-reject triage before the AoE cutoff.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-submission --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# SoCC Submission Run this audit before uploading to the SoCC HotCRP site (`socc26.hotcrp.com` for the 2026 cycle). SoCC — the ACM Symposium on Cloud Computing — is the only venue **jointly sponsored by SIGMOD and SIGOPS**, so your paper is read by both systems and data-management reviewers and must satisfy both. Every number below was read from the SoCC 2026/2025 calls on 2026-07-09 via search renderings of the `acmsocc.org` URLs (see `resources/official-source-map.md`); treat them as a one-cycle snapshot and reopen the live call first. ## The two-round calendar (the distinctive SoCC deadline) SoCC runs **two review rounds per year**, each with its own abstract, submission, author-response, and notification dates. For SoCC 2026: - **Round 1:** abstract 6 Feb 2026, paper 13 Feb 2026, response 12-14 Apr 2026, notify 29 Apr 2026. - **Round 2:** abstract 7 Jul 2026, paper 14 Jul 2026 (AoE), response 10-12 Sep 2026, notify 26 Sep 2026. Two consequences to internalize: - **Abstract registration precedes the paper by ~a week within the round.** Register the real title and abstract; the abstract drives reviewer bidding. - **A Round-1 reject cannot be resubmitted to Round 2** of the same y
- The two-round calendar (the distinctive SoCC deadline)
- Format and page budget
- Dual-anonymous sweep
- Reproducibility posture at submission time
- Desk-risk triage
- Final-week order of operations
- Reverify each cycle
- Output format
Mechanical pass on the submission PDF and any released artifact archive pdfinfo paper.pdf | grep -Ei 'author|creator|producer' pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|zenodo\.org/record|our (cluster|company|team|deployment)|acknowledg|grant' | head unzip -l artifact.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/|internal' | head
What does the socc-submission skill do?
Use when auditing an ACM SoCC (Symposium on Cloud Computing) research-paper submission for HotCRP readiness, covering the two-round abstract+paper deadlines, the acmart/sigconf 12-page (full) or 6-page (short) budget with unlimited references, dual-anonymous review, the systems-and-data reproducibility posture, and desk-reject triage before the AoE cutoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-submission --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.