Ieee Paper Reader
CloudWave818/ieee-skills
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.
A skill your agent uses when positioning an ACM SIGCOMM submission against the networking literature — sweeping SIGCOMM, NSDI, MobiCom, CoNEXT, IMC, and SIGMETRICS plus journals, proving each…
Install Sigcomm Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-related-work --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-related-work .claude/skills/sigcomm-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-related-work into .claude/skills/sigcomm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-related-work", 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-related-workType 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-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-related-work --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-related-work .agents/skills/sigcomm-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-related-work into .agents/skills/sigcomm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-related-work", 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-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-related-work --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-related-work .cursor/skills/sigcomm-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-related-work into .cursor/skills/sigcomm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-related-work", 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-related-work--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-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-related-work --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-related-work .gemini/skills/sigcomm-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-related-work into .gemini/skills/sigcomm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-related-work", 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-related-workInstalls 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-related-work -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-related-work .github/skills/sigcomm-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-related-work into .github/skills/sigcomm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-related-work", 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-related-work -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-related-work --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-related-work .opencode/skills/sigcomm-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-related-work into .opencode/skills/sigcomm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-related-work", 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-related-work- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 423 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when positioning an ACM SIGCOMM submission against the networking literature — sweeping SIGCOMM, NSDI, MobiCom, CoNEXT, IMC, and SIGMETRICS plus journals, proving each…
- Positioning an ACM SIGCOMM submission against the networking literature — sweeping SIGCOMM
- SKILL.md covers Positioning checks, Venue-coverage table, The misattribution guard and Positioning vignette, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- SIGMETRICS plus journals
What it does
Sigcomm Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an ACM SIGCOMM submission against the networking literature — sweeping SIGCOMM, NSDI, MobiCom, CoNEXT, IMC, and SIGMETRICS plus journals, proving each placement via dblp and the ACM Digital Library, distinguishing main-track papers from CCR editorials, handling concurrent work, and keeping self-citation double-blind-safe.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Literature review, Citation management and Positioning and messaging. 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
- Positioning an ACM SIGCOMM submission against the networking literature — sweeping SIGCOMM
- SIGMETRICS plus journals
- Proving each placement via dblp and the ACM Digital Library
- Distinguishing main-track papers from CCR editorials
Example prompts
- “/sigcomm-related-work”
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 Related Work loads about 1k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 423 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). 423 words, ~1,046 tokens.
Download SKILL.mdSave it as
.claude/skills/sigcomm-related-work/SKILL.md (or your agent's skills folder).- name
- sigcomm-related-work
- description
- Use when positioning an ACM SIGCOMM submission against the networking literature — sweeping SIGCOMM, NSDI, MobiCom, CoNEXT, IMC, and SIGMETRICS plus journals, proving each placement via dblp and the ACM Digital Library, distinguishing main-track papers from CCR editorials, handling concurrent work, and keeping self-citation double-blind-safe.
SIGCOMM Related Work
Use this to audit novelty and placement. SIGCOMM is the broad networking flagship, so a paper is read against the strongest prior work in its exact subarea — and against results scattered across sibling venues. Reopen the current CFP for concurrent-submission and anonymity rules before advising.
Positioning checks
- Separate the mechanism you contribute from engineering polish: a new protocol, transport signal, forwarding architecture, measurement-driven design, or programmable-data-plane technique.
- Sweep the whole networking literature, not just SIGCOMM: the nearest prior work may sit in NSDI, MobiCom, CoNEXT, IMC, SIGMETRICS, INFOCOM, or a journal like IEEE/ACM Transactions on Networking. A bibliography that cites only SIGCOMM signals a narrow read.
- Prove each placement. Verify the venue and year on dblp and the ACM DL before you assert it; do not rely on memory for where a famous result appeared.
- Distinguish main-track proceedings from CCR editorial notes — OpenFlow's famous CCR note is not a SIGCOMM conference paper, and citing it as one is a checkable error.
- Handle concurrent and prior versions honestly, and keep every self-citation phrased so double-blind review survives.
Venue-coverage table
| Literature lane | Typical venues | What SIGCOMM reviewers check |
|---|---|---|
| Networking design flagships | SIGCOMM, NSDI, CoNEXT | Whether the nearest deployed mechanism is compared or distinguished |
| Wireless / mobile | MobiCom, SIGMOBILE venues | Whether relevant PHY/mobility work is acknowledged when adjacent |
| Measurement | IMC | Whether the motivating measurement rests on the right prior characterizations |
| Performance analysis | SIGMETRICS | Whether known models/bounds are credited |
| Archival journals | IEEE/ACM ToN, JSAC | Whether classical results are not being rediscovered |
A missing state-of-the-art comparison from the right venue is a recognizable SIGCOMM reject pattern that benchmark strength alone does not repair.
Show full SKILL.md (153 more words)Show less
The misattribution guard
Before citing "X appeared at SIGCOMM YYYY":
1. Find it on dblp.org/db/conf/sigcomm/ -> confirm the edition and page range
2. Confirm ACM DL lists it in the SIGCOMM conference proceedings, not CCR editorial
3. Rule out the sibling: Hedera is NSDI, RED is ToN, BBR is CACM
4. If unresolved -> mark 待核实 and do not assert the venuePositioning vignette
A paper proposes a data-center transport that schedules flows in the fabric. Its nearest neighbors: an earlier SIGCOMM congestion-signal paper (DCTCP), a fabric-scheduling paper in the same lineage (pFabric), and an NSDI flow-scheduling system that is often confused with it. The novelty sentence should name all three contrasts — a different signal than the first, a different scheduling granularity than the second, and a design rather than the deployed-system framing of the NSDI neighbor — with each venue verified.
Concurrent-work judgment calls
- Independently concurrent work at another venue: cite neutrally, state the technical difference, and avoid priority claims reviewers cannot verify under blinding.
- Your own prior workshop or preprint version: cite in a blind-safe third person and confirm the current CFP's stance on overlap before relying on it.
- When a venue's archival status is unclear, declare the overlap in the submission rather than gambling on a chair's reading.
Output format
[Eligibility] clear / needs declaration / risky
[Closest venues] <SIGCOMM / NSDI / MobiCom / CoNEXT / IMC / journal>
[Nearest 3 works] <work -> distinction, each venue verified>
[Misattribution risk] <CCR-vs-main-track / sibling-venue traps checked>
[Novelty sentence] <SIGCOMM-ready mechanism contrast>© 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-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sigcomm Related Work 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 Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Ieee Paper ReaderCloudWave818/ieee-skills | 359 | — | ~591 | Automated safety check: Pass | MIT | |
| Gec Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~855 | Automated safety check: Pass | None | |
| Jpe Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
Gec Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when positioning a Global Environmental Change (GEC) manuscript against the relevant literatures.
Jpe Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when writing or repairing the introduction and related-work framing for a Journal of Political Economy (JPE) manuscript — situating the contribution in the economics…
Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
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…
Related
Categories
Questions about Sigcomm Related Work
What does Sigcomm Related Work do?
A skill your agent uses when positioning an ACM SIGCOMM submission against the networking literature — sweeping SIGCOMM, NSDI, MobiCom, CoNEXT, IMC, and SIGMETRICS plus journals, proving each…. Sigcomm Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an ACM SIGCOMM submission against the networking literature — sweeping SIGCOMM, NSDI, MobiCom, CoNEXT, IMC, and SIGMETRICS plus journals, proving each placement via dblp and the ACM Digital Library, distinguishing main-track papers from CCR editorials, handling concurrent work, and keeping self-citation double-blind-safe.
When should I use Sigcomm Related Work?
Sigcomm Related Work fits situations like: positioning an ACM SIGCOMM submission against the networking literature — sweeping SIGCOMM; SIGMETRICS plus journals; proving each placement via dblp and the ACM Digital Library; distinguishing main-track papers from CCR editorials.
How do I install Sigcomm Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-related-work -a claude-code`. Or copy the skill folder (SIGCOMM-Skills/skills/sigcomm-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sigcomm-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Sigcomm Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-related-work -a codex`. Or copy the skill folder (SIGCOMM-Skills/skills/sigcomm-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sigcomm-related-work in your project. Codex loads it when a task matches its description.
Can I use Sigcomm Related Work 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-related-work -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-related-work, .gemini/skills/sigcomm-related-work, .github/skills/sigcomm-related-work and .opencode/skills/sigcomm-related-work in your project.
What does Sigcomm Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Sigcomm Related Work is instructions for the agent only.
Does Sigcomm Related Work 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 Related Work 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 Related Work use?
Sigcomm Related Work 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 Related Work use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Related Work?
Skills that share tags, products or a category with Sigcomm Related Work: Ieee Paper Reader (CloudWave818/ieee-skills, 359 stars), Gec Literature Positioning (franklee16/academic-research-skills, 223 stars), Jpe Literature Positioning (franklee16/academic-research-skills, 223 stars) and Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sigcomm Related Work?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.