sigmetrics-submission
Use when auditing an ACM SIGMETRICS submission for HotCRP readiness, covering the choice among the three rolling deadlines (summer/fall/winter), the separate abstract-registration step, the 20-page single-column acmsmall budget plus unlimited references, double-anonymous review (and the Operational Systems Track exception), track selection, POMACS publication, and desk-reject triage before the AoE cutoff.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmetrics-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.
# SIGMETRICS Submission Run this audit before uploading to the per-deadline SIGMETRICS HotCRP site. SIGMETRICS research papers are published as **journal articles in POMACS** (Proceedings of the ACM on Measurement and Analysis of Computing Systems), submitted on a **three-deadlines-per-year rolling model**, so the submission is judged like a journal manuscript that also earns a conference slot. Every number below was read from the SIGMETRICS 2026/2027 calls on 2026-07-09 via search renderings (see `resources/official-source-map.md`); treat them as a one-cycle snapshot and reopen the live call first. ## Choose the deadline first SIGMETRICS has **three deadlines a year** — summer, fall, winter — each on its own HotCRP site. This is the biggest departure from a single-annual-deadline conference: - Every deadline feeds the same POMACS journal; there is no "main" deadline. - Papers accepted from the **summer and fall** deadlines appear in POMACS **before** the conference; a winter acceptance publishes in the following issue. Pick the deadline whose notification and publication timing fits your goals (graduation, a job-market cycle, the conference you want to present at). - 2026-cycle da
- Choose the deadline first
- The two-step deadline
- Track selection
- Format and page budget
- Double-anonymous sweep
- Desk-risk triage
- Final-week order of operations
- Reverify each cycle
- Output format
Mechanical pass on the submission PDF and any anonymized artifact archive pdfinfo paper.pdf | grep -Ei 'author|creator|producer' pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|our (system|prior) work|acknowledg|grant|university of' | head unzip -l artifact.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/' | head
What does the sigmetrics-submission skill do?
Use when auditing an ACM SIGMETRICS submission for HotCRP readiness, covering the choice among the three rolling deadlines (summer/fall/winter), the separate abstract-registration step, the 20-page single-column acmsmall budget plus unlimited references, double-anonymous review (and the Operational Systems Track exception), track selection, POMACS publication, and desk-reject triage before the AoE cutoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmetrics-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.