Linux Networking
RightNow-AI/openfang
Linux networking expert for iptables, nftables, routing, DNS, and network troubleshooting
Agent skill
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when deciding whether a networking project belongs at IEEE INFOCOM or should be routed to SIGCOMM, NSDI, MobiCom, ICNP, or an IEEE/ACM networking journal (ToN, JSAC)…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-topic-selection --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/INFOCOM-Skills/skills/infocom-topic-selection .claude/skills/infocom-topic-selection && 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 "infocom-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-topic-selection into .claude/skills/infocom-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-topic-selection", 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/INFOCOM-Skills/skills/infocom-topic-selectionType 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 infocom-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-topic-selection --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/INFOCOM-Skills/skills/infocom-topic-selection .agents/skills/infocom-topic-selection && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "infocom-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-topic-selection into .agents/skills/infocom-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-topic-selection", 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 infocom-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-topic-selection --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/INFOCOM-Skills/skills/infocom-topic-selection .cursor/skills/infocom-topic-selection && 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 "infocom-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-topic-selection into .cursor/skills/infocom-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-topic-selection", 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 INFOCOM-Skills/skills/infocom-topic-selection--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 infocom-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-topic-selection --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/INFOCOM-Skills/skills/infocom-topic-selection .gemini/skills/infocom-topic-selection && 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 "infocom-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-topic-selection into .gemini/skills/infocom-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-topic-selection", 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 infocom-topic-selectionInstalls 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 infocom-topic-selection -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/INFOCOM-Skills/skills/infocom-topic-selection .github/skills/infocom-topic-selection && 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 "infocom-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-topic-selection into .github/skills/infocom-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-topic-selection", 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 infocom-topic-selection -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 infocom-topic-selection --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/INFOCOM-Skills/skills/infocom-topic-selection .opencode/skills/infocom-topic-selection && 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 "infocom-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-topic-selection into .opencode/skills/infocom-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-topic-selection", 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.
infocom-topic-selectionA skill your agent uses when deciding whether a networking project belongs at IEEE INFOCOM or should be routed to SIGCOMM, NSDI, MobiCom, ICNP, or an IEEE/ACM networking journal (ToN, JSAC)…
Infocom Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a networking project belongs at IEEE INFOCOM or should be routed to SIGCOMM, NSDI, MobiCom, ICNP, or an IEEE/ACM networking journal (ToN, JSAC), distinguishing INFOCOM by its breadth, its analytical/optimization tradition alongside systems, and the modeling-vs-building axis.
Its SKILL.md is about 1.5k 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.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Infocom Topic Selection loads about 1.5k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 610 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.
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.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 610 words, ~1,481 tokens.
.claude/skills/infocom-topic-selection/SKILL.md (or your agent's skills folder).Decide the venue before drafting. INFOCOM — the IEEE International Conference on Computer Communications, the IEEE ComSoc networking flagship — is the broad, large-scale networking venue. Its defining feature relative to its siblings is breadth plus a living analytical tradition: a well-posed model with a theorem and a convincing evaluation is a first-class INFOCOM paper, not a second-class one. A pure systems-building paper is welcome, but so is a scheduling/optimization/queueing/game-theory result that SIGCOMM or NSDI would push to a journal.
The decisive question is rarely "is this networking?" but "is the contribution a model/analysis, a built system, or a measurement — and which community rewards that shape now?" INFOCOM is the safe home for the analytical and the broad; SIGCOMM/NSDI pull toward built-and-measured systems with a deployment story. Use the finer signals below and the live calendar to choose.
| Signal in your project | Better home | Why |
|---|---|---|
| Modeling/optimization/algorithmic core (scheduling, resource allocation, queueing, game theory, network economics) with analysis + simulation | IEEE INFOCOM | Its analytical tradition treats theorems-with-evaluation as first-class |
| Broad networking contribution, ready now, with the next INFOCOM deadline nearer | IEEE INFOCOM | Large flagship; broad scope and reviewer pool |
| A built, deployed system with a measured Internet/datacenter deployment story | ACM SIGCOMM | Rewards architecture + real deployment; smaller, systems-first |
| A systems artifact whose case is a real implementation and hard performance numbers | USENIX NSDI | Networked-systems building, artifact-heavy |
| Wireless/mobile system with real devices, PHY/MAC + measurement | ACM MobiCom / MobiSys | Mobile-computing center of gravity |
| A focused protocol-design/analysis contribution | IEEE ICNP | Protocols venue; narrower than INFOCOM |
| Study too long or too incremental for a nine-page conference limit | IEEE/ACM ToN, IEEE JSAC | Journals with no page ceiling and a revise-and-resubmit cycle |
Two quick tests sharpen a borderline verdict:
Fit is necessary but not sufficient. A formulation with a theorem but no evaluation reads as incomplete for the main track; a system evaluated only on a toy topology needs realistic scale before it convinces; a measurement without a methodology a reviewer can audit will not survive the crowded pool. INFOCOM's scale means a marginal paper competes against ~1,400 others for ~19% of slots — submit when the analysis and the evaluation are both ready.
[Scope] scan the last two INFOCOM programs (dblp conf/infocom) for your subarea
-> several recent papers = a reviewer pool exists; near-zero = mismatch or opening
[Shape] is your core a model/algorithm, a built system, or a measurement?
-> model/algorithm leans INFOCOM; built-and-deployed leans SIGCOMM/NSDI
[Calendar] compare the next INFOCOM deadline (late July) with SIGCOMM/NSDI/MobiCom/journal dates
-> route to the nearest honest fit rather than idling a year[Audience] who acts differently if the claim holds? -> network designers/operators/theorists?
[Claim type] analytical / protocol / wireless / measurement / learning-for-networking
[Axis] model-and-analyze -> INFOCOM; build-and-deploy -> SIGCOMM/NSDI; wireless system -> MobiCom
[Sibling check] protocol-focused -> ICNP; too long/incremental -> ToN/JSAC
[Verdict] INFOCOM main track / sibling venue / journal, with a one-line reasonRun this before the writing skills; a wrong venue decision wastes every later step. When the verdict
is INFOCOM, continue with infocom-workflow for the calendar and infocom-writing-style for the
paper shape.
© 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
Just SKILL.md in INFOCOM-Skills/skills/infocom-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Infocom Topic Selection 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 |
|---|---|---|---|---|---|---|
| Infocom Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Linux NetworkingRightNow-AI/openfang | 18k | — | ~882 | Automated safety check: Pass | Apache-2.0 | |
| Performing Ot Network Security Assessmentmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~6.1k | Automated safety check: Pass | Apache-2.0 | |
| Gke Networkinggoogle/skills | 21k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Performing Network Forensics With Wiresharkmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3k | Automated safety check: Notes | Apache-2.0 | |
| Performing Network Packet Capture Analysismukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 |
RightNow-AI/openfang
Linux networking expert for iptables, nftables, routing, DNS, and network troubleshooting
mukul975/Anthropic-Cybersecurity-Skills
This skill covers conducting comprehensive security assessments of Operational Technology (OT) networks including SCADA systems, DCS architectures, and industrial control system communication paths.
google/skills
Plans, configures, and manages core GKE cluster networking. An agent skill from google/skills.
mukul975/Anthropic-Cybersecurity-Skills
Capture and analyze network traffic using Wireshark and tshark to reconstruct network events from PCAP/PCAPNG files, extract transferred files and credentials, and identify command-and-control…
mukul975/Anthropic-Cybersecurity-Skills
Perform forensic analysis of network packet captures (PCAP/PCAPNG) using Wireshark, tshark, and tcpdump to reconstruct network communications, extract transferred files, identify malicious traffic…
sickn33/agentic-awesome-skills
Configure VPCs, firewall rules, and Cloud NAT. An agent skill from sickn33/agentic-awesome-skills.
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…
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…
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…
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…
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…
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…
A skill your agent uses when deciding whether a networking project belongs at IEEE INFOCOM or should be routed to SIGCOMM, NSDI, MobiCom, ICNP, or an IEEE/ACM networking journal (ToN, JSAC)…. Infocom Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a networking project belongs at IEEE INFOCOM or should be routed to SIGCOMM, NSDI, MobiCom, ICNP, or an IEEE/ACM networking journal (ToN, JSAC), distinguishing INFOCOM by its breadth, its analytical/optimization tradition alongside systems, and the modeling-vs-building axis.
Infocom Topic Selection fits situations like: deciding whether a networking project belongs at IEEE INFOCOM; should be routed to SIGCOMM; an IEEE/ACM networking journal (ToN; distinguishing INFOCOM by its breadth.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-topic-selection -a claude-code`. Or copy the skill folder (INFOCOM-Skills/skills/infocom-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/infocom-topic-selection in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-topic-selection -a codex`. Or copy the skill folder (INFOCOM-Skills/skills/infocom-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/infocom-topic-selection in your project. Codex loads it when a task matches its description.
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 infocom-topic-selection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/infocom-topic-selection, .gemini/skills/infocom-topic-selection, .github/skills/infocom-topic-selection and .opencode/skills/infocom-topic-selection in your project.
SKILL.md names no scripts, command-line tools or credentials: Infocom Topic Selection is instructions for the agent only.
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.
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.
Infocom Topic Selection is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Infocom Topic Selection: Linux Networking (RightNow-AI/openfang, 18k stars), Performing Ot Network Security Assessment (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Gke Networking (google/skills, 21k stars) and Performing Network Forensics With Wireshark (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.
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.