Acm Sigcomm
franklee16/academic-research-skills
A skill your agent uses when targeting ACM SIGCOMM (SIGCOMM) or deciding whether a computer-science manuscript fits this venue.
A skill your agent uses when planning an ACM SIGCOMM project timeline around the single yearly deadline — venue fit, evidence lock, abstract registration and paper upload in February, the…
MITAuto-check passed
Install Sigcomm Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/SIGCOMM-Skills/skills/sigcomm-workflow .claude/skills/sigcomm-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sigcomm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-workflow into .claude/skills/sigcomm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/SIGCOMM-Skills/skills/sigcomm-workflow .agents/skills/sigcomm-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sigcomm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-workflow into .agents/skills/sigcomm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/SIGCOMM-Skills/skills/sigcomm-workflow .cursor/skills/sigcomm-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sigcomm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-workflow into .cursor/skills/sigcomm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path SIGCOMM-Skills/skills/sigcomm-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/SIGCOMM-Skills/skills/sigcomm-workflow .gemini/skills/sigcomm-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sigcomm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-workflow into .gemini/skills/sigcomm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/SIGCOMM-Skills/skills/sigcomm-workflow .github/skills/sigcomm-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sigcomm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-workflow into .github/skills/sigcomm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/SIGCOMM-Skills/skills/sigcomm-workflow .opencode/skills/sigcomm-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sigcomm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-workflow into .opencode/skills/sigcomm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sigcomm-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 566 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an ACM SIGCOMM project timeline around the single yearly deadline — venue fit, evidence lock, abstract registration and paper upload in February, the…
- Planning an ACM SIGCOMM project timeline around the single yearly deadline — venue fit
- SKILL.md covers Milestones, Backward plan from the…, The year has two halves, not… and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Abstract registration and paper upload in February
What it does
Sigcomm Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACM SIGCOMM project timeline around the single yearly deadline — venue fit, evidence lock, abstract registration and paper upload in February, the early-reject/rebuttal/one-shot-revision review pipeline, shepherd-run camera-ready, TAPS proceedings, artifact evaluation, and forward planning for the next edition.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Planning an ACM SIGCOMM project timeline around the single yearly deadline — venue fit
- Abstract registration and paper upload in February
- The early-reject/rebuttal/one-shot-revision review pipeline
- Shepherd-run camera-ready
Example prompts
- “/sigcomm-workflow”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sigcomm Workflow loads about 1.2k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 566 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 566 words, ~1,210 tokens.
Download SKILL.mdSave it as
.claude/skills/sigcomm-workflow/SKILL.md (or your agent's skills folder).- name
- sigcomm-workflow
- description
- Use when planning an ACM SIGCOMM project timeline around the single yearly deadline — venue fit, evidence lock, abstract registration and paper upload in February, the early-reject/rebuttal/one-shot-revision review pipeline, shepherd-run camera-ready, TAPS proceedings, artifact evaluation, and forward planning for the next edition.
SIGCOMM Workflow
Use this as the project-management skill for a SIGCOMM campaign. The defining constraint is one main-track deadline per year feeding one August conference: there is no fall gate, so the plan is a year-long backward schedule from February, not a two-shot hedge. Replace every date with the current official timetable.
SIGCOMM is a conference, not a journal: it has no standing editor-in-chief and no article-processing charge. The rotating leadership is the per-edition General Chairs and Program Committee Co-Chairs (the 2026 roster was not retrievable on 2026-07-09 — 待核实), and the cost model is registration, not APCs; proceedings publish through ACM TAPS into the ACM Digital Library. Chairs rotate yearly, so re-check the current organization page.
Milestones
- Venue fit and track: confirm a networking-stack mechanism and pick research vs. experience.
- Evidence lock: freeze the testbed, traces, workloads, baselines, measurement methodology, and the tail metrics before writing hardens.
- Abstract registration: real title, authors, topics, conflicts on HotCRP.
- Full-paper upload: anonymous PDF, 12 single-spaced pre-reference pages, ACM template.
- Review release: triage across correctness, novelty, evaluation realism, and clarity.
- Rebuttal: for papers reaching the discussion phase, a concise anonymous reply.
- Decision: accept, one-shot revision, or reject (early or formal).
- Revision (if issued): resubmit ~a month later under a shepherd against the issue list.
- Camera-ready: shepherd sign-off, TAPS final PDF plus source, de-anonymization.
- Artifact evaluation and presentation: AEC badges, public release, August talk.
Backward plan from the February paper deadline
| Weeks out (heuristic) | Systems/measurement milestone |
|---|---|
| 14+ | Mechanism designed; testbed or trace pipeline standing and repeatable |
| 10 | Core evaluation runs producing stable tails across repeated trials |
| 7 | Baselines that fight back implemented and tuned fairly |
| 5 | Full draft in ACM two-column format, figures counting against 12 pages |
| 3 | Internal mock review by a networking-minded reader; break-point experiment added |
| 2 | Reproducibility ledger and artifact skeleton assembled |
| 1 | Anonymity sweep, HotCRP fields, abstract registered |
| 0 | Full paper uploaded AoE; receipt re-read |
These offsets are planning heuristics — anchor each to the current official timetable, never to a previous edition's calendar.
Show full SKILL.md (234 more words)Show less
The year has two halves, not one deadline
Because the deadline is annual, the calendar after submission matters as much as before it. As of 2026-07-09 the SIGCOMM 2026 cycle is in its live post-decision phase: the February deadline passed, decisions issued, and the work now is camera-ready finalization, shepherd sign-off, artifact evaluation, and the August presentation — while the next edition's February deadline is already the horizon for new work. Plan both halves: the run-up to the single deadline, and the shepherd-to-proceedings tail that follows acceptance.
Failure modes by stage
- Evidence still moving at week 5 forces last-minute metric changes nobody has re-run — the classic evaluation-realism reject in the making.
- Leaving ACM two-column conversion to the final week surfaces figure-driven overflow late, because figures count against the 12 pages.
- Skipping the mock review forfeits the only chance to hear "your baseline is a straw man" from a friend instead of a reviewer.
- Treating a one-shot revision as optional polish rather than a shepherd-graded contract is how a revision that dodged the issue list gets rejected.
- Deferring the artifact until after acceptance loses the reproducibility evidence that a clean rebuild would have surfaced.
Coordination notes
- Assign one named owner for the reproducibility ledger and another for the anonymity sweep; shared ownership is how both slip.
- Archive the exact submitted PDF and every logged run, since rebuttal and revision replies must quote them precisely.
Output format
[Current stage] idea / evaluation / writing / abstract / submission / rebuttal / revision / accepted
[Next official deadline] <date and source, or unknown>
[Critical path] <three tasks that determine readiness>
[Risk register] <format / anonymity / evaluation realism / reproducibility / shepherd>
[Owner map] <task -> person or role>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in SIGCOMM-Skills/skills/sigcomm-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sigcomm Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sigcomm Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Acm Sigcommfranklee16/academic-research-skills | 223 | 1 repos | ~1.9k | Automated safety check: Pass | None | |
| Project Timeline Reportthedotmack/claude-mem | 99k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| GSAP Timelinegreensock/gsap-skills | 16k | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Building Incident Timeline With Timesketchmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.4k | Automated safety check: Notes | Apache-2.0 | |
| Generating Forensic Timelines With Hayabusamukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Project Timeline Report
thedotmack/claude-mem
Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.
GSAP Timeline
greensock/gsap-skills
Teaches the GSAP timeline API for sequencing animations: gsap.timeline(), the position parameter, labels, defaults, nesting and playback control.
Building Incident Timeline With Timesketch
mukul975/Anthropic-Cybersecurity-Skills
Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data (including Plaso output) for attack chain reconstruction and investigation…
Generating Forensic Timelines With Hayabusa
mukul975/Anthropic-Cybersecurity-Skills
Run Hayabusa against collected Windows EVTX files to apply Sigma detection rules and produce a prioritized, chronological CSV/JSON timeline with severity levels, MITRE ATT&CK mappings, and…
Performing Timeline Reconstruction With Plaso
mukul975/Anthropic-Cybersecurity-Skills
Builds comprehensive forensic super-timelines using Plaso (log2timeline and psort) to correlate events across file system metadata, event logs, browser history, and registry artifacts into a unified…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Sigcomm Workflow
What does Sigcomm Workflow do?
A skill your agent uses when planning an ACM SIGCOMM project timeline around the single yearly deadline — venue fit, evidence lock, abstract registration and paper upload in February, the…. Sigcomm Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACM SIGCOMM project timeline around the single yearly deadline — venue fit, evidence lock, abstract registration and paper upload in February, the early-reject/rebuttal/one-shot-revision review pipeline, shepherd-run camera-ready, TAPS proceedings, artifact evaluation, and forward planning for the next edition.
When should I use Sigcomm Workflow?
Sigcomm Workflow fits situations like: planning an ACM SIGCOMM project timeline around the single yearly deadline — venue fit; abstract registration and paper upload in February; the early-reject/rebuttal/one-shot-revision review pipeline; shepherd-run camera-ready.
How do I install Sigcomm Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-workflow -a claude-code`. Or copy the skill folder (SIGCOMM-Skills/skills/sigcomm-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sigcomm-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Sigcomm Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-workflow -a codex`. Or copy the skill folder (SIGCOMM-Skills/skills/sigcomm-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sigcomm-workflow in your project. Codex loads it when a task matches its description.
Can I use Sigcomm Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sigcomm-workflow, .gemini/skills/sigcomm-workflow, .github/skills/sigcomm-workflow and .opencode/skills/sigcomm-workflow in your project.
What does Sigcomm Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Sigcomm Workflow is instructions for the agent only.
Does Sigcomm Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Sigcomm Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sigcomm Workflow use?
Sigcomm Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sigcomm Workflow use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sigcomm Workflow?
Skills that share tags, products or a category with Sigcomm Workflow: Acm Sigcomm (franklee16/academic-research-skills, 223 stars), Project Timeline Report (thedotmack/claude-mem, 99k stars), GSAP Timeline (greensock/gsap-skills, 16k stars) and Building Incident Timeline With Timesketch (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sigcomm Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.