SIGMETRICS Skills

A 12-skill depth pack for ACM SIGMETRICS submissions published in POMACS (Proceedings of the ACM on Measurement and Analysis of Computing Systems): venue routing among the performance-evaluation venues, the three-cycles-per-year rolling deadlines (summer/fall/winter), the hybrid conference-journal review with its one-shot revision and mandatory shepherding, double-anonymous acmsmall submission, th

by @brycewang-stanford 12 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/sigmetrics-skills

One command, no setup. In Claude Code it lands as a managed plugin you can enable, disable or remove with /plugin. On any other agent it installs the 12 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-sigmetrics-skills@skillmd

Adds the marketplace once; later plugins need the second line only.

Or install by hand

Download the plugin and unzip its skills/ folder into your agent's skills directory. Works with every agent, no CLI needed.

Download plugin Paths per agent

Just the markdown? SKILL.md files only.

This plugin

skills: 12
authors: 1

Published by a registry member. Review its skills before installing.

Skills in this plugin

▌
Sigmetrics Workflow · brycewang-stanford
Use when planning an ACM SIGMETRICS project timeline across the three rolling deadlines (summer/fall/winter), from venue fit through abstract registration, submission, shepherding, the one-shot revision round, POMACS publication, and presentation, with backward-planning offsets for a performance-evaluation paper and honest handling of the rolling-deadline cadence and the 12-month resubmission bar.

1k repo stars
▌
Sigmetrics Submission · brycewang-stanford
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.

1k repo stars
▌
Sigmetrics Experiments · brycewang-stanford
Use when designing or auditing ACM SIGMETRICS evaluations, covering theorem-plus-validation rigor, stating and testing modeling assumptions, analysis-vs-simulation agreement, real workloads and traces, fairly tuned baselines, statistics and confidence intervals for stochastic systems, learning guarantees, measurement provenance, and matching evidence to the shape of each performance claim.

1k repo stars
▌
Sigmetrics Camera Ready · brycewang-stanford
Use when preparing an accepted ACM SIGMETRICS paper for its POMACS camera-ready, covering de-anonymization, the acmsmall template and POMACS journal metadata (DOI, ORCID, CCS concepts), incorporating the shepherd's required changes without scope creep, permanentizing artifact links, and the ACM artifact-badge handoff.

1k repo stars
▌
Sigmetrics Related Work · brycewang-stanford
Use when positioning an ACM SIGMETRICS submission against the performance-evaluation literature across SIGMETRICS/POMACS, Performance Evaluation, QUESTA, TON, and the systems/learning/measurement neighbors (NSDI/OSDI, IMC, NeurIPS/ICML), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling concurrent and prior-version overlap.

1k repo stars
▌
Sigmetrics Supplementary · brycewang-stanford
Use when deciding what belongs in an ACM SIGMETRICS paper body versus its appendices and anonymized artifact, covering the 20-page single-column acmsmall budget, the rule that decision-critical claims (theorem statements, assumptions, headline validation) stay inside the reviewed pages, full proofs in appendices, double-anonymous supplementary material, and how to split a proof-plus-measurement paper.

1k repo stars
▌
Sigmetrics Writing Style · brycewang-stanford
Use when revising an ACM SIGMETRICS paper for a rigorously stated performance contribution on the first page, explicit modeling assumptions and their validity, theorems paired with numerical/empirical validation, evidence proportional to the claim, double-anonymous wording, and disciplined use of the 20-page single-column acmsmall budget.

1k repo stars
▌
Sigmetrics Review Process · brycewang-stanford
Use when reasoning about how an ACM SIGMETRICS submission is evaluated, covering the hybrid conference-journal model, double-anonymous review, the three first-round outcomes (Accept-with-shepherding / One-Shot Revision / Reject), the one-shot revision resubmitted to a subsequent rolling deadline, the 12-month resubmission bar, and how SIGMETRICS differs from IMC, SIGCOMM, and NSDI.

1k repo stars
▌
Sigmetrics Author Response · brycewang-stanford
Use when responding to ACM SIGMETRICS reviews, covering any initial rebuttal and — distinctively — the one-shot revision response letter that must map every item on the reviewers' required-changes list to a concrete change in the revised POMACS paper, resubmitted to a subsequent rolling deadline and re-reviewed once by the original reviewers under double-anonymity.

1k repo stars
▌
Sigmetrics Reproducibility · brycewang-stanford
Use when strengthening ACM SIGMETRICS reproducibility, covering proofs and their assumptions as reproducible artifacts, seeded simulators whose figures regenerate and match the analysis, measurement/trace provenance, claim-to-evidence mapping, honest degrees of reproducibility, and consistency between what the paper proves/measures and what the artifact contains.

1k repo stars
▌
Sigmetrics Topic Selection · brycewang-stanford
Use when deciding whether a computer-systems performance project belongs at ACM SIGMETRICS or should be routed to IMC, SIGCOMM/NSDI/OSDI, INFOCOM, a learning venue (NeurIPS/ICML), or a performance journal (Performance Evaluation/TON/QUESTA), and when picking the right SIGMETRICS track (Theory / Measurement & Applied Modeling / Learning / Operational Systems).

1k repo stars
▌
Sigmetrics Artifact Evaluation · brycewang-stanford
Use when packaging an ACM SIGMETRICS artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced), covering what performance-evaluation evaluators check first (does the simulation regenerate the figures and match the analysis?), DOI-issuing archives, evaluator-proof documentation, and confirming whether an artifact track runs this cycle.

1k repo stars