Acm Workshop On Hot Topics In Networks
franklee16/academic-research-skills
A skill your agent uses when targeting ACM Workshop on Hot Topics in Networks (HotNets) or deciding whether a computer-science manuscript fits this venue.
A skill your agent uses when deciding whether a networking project belongs at ACM CoNEXT or should be routed to SIGCOMM, NSDI, IMC, SIGMETRICS, MobiCom, or HotNets, and when using CoNEXT's…
MITAuto-check passed
Install Conext Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills conext-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/CoNEXT-Skills/skills/conext-topic-selection .claude/skills/conext-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 "conext-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoNEXT-Skills/skills/conext-topic-selection into .claude/skills/conext-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conext-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/CoNEXT-Skills/skills/conext-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 conext-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills conext-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/CoNEXT-Skills/skills/conext-topic-selection .agents/skills/conext-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 "conext-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoNEXT-Skills/skills/conext-topic-selection into .agents/skills/conext-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conext-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 conext-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills conext-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/CoNEXT-Skills/skills/conext-topic-selection .cursor/skills/conext-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 "conext-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoNEXT-Skills/skills/conext-topic-selection into .cursor/skills/conext-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conext-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 CoNEXT-Skills/skills/conext-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 conext-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills conext-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/CoNEXT-Skills/skills/conext-topic-selection .gemini/skills/conext-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 "conext-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoNEXT-Skills/skills/conext-topic-selection into .gemini/skills/conext-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conext-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 conext-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 conext-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/CoNEXT-Skills/skills/conext-topic-selection .github/skills/conext-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 "conext-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoNEXT-Skills/skills/conext-topic-selection into .github/skills/conext-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conext-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 conext-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 conext-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/CoNEXT-Skills/skills/conext-topic-selection .opencode/skills/conext-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 "conext-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoNEXT-Skills/skills/conext-topic-selection into .opencode/skills/conext-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conext-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.
Facts
- Skill name
conext-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 723 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding whether a networking project belongs at ACM CoNEXT or should be routed to SIGCOMM, NSDI, IMC, SIGMETRICS, MobiCom, or HotNets, and when using CoNEXT's…
- Works in 2 steps: Which networking community and rigor bar… → Which of CoNEXT's two cycles is the…
- Deciding whether a networking project belongs at ACM CoNEXT
- SKILL.md covers The two routing questions that…, Sibling-venue routing table, Contribution shapes CoNEXT… and The platform-realism and…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Conext Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a networking project belongs at ACM CoNEXT or should be routed to SIGCOMM, NSDI, IMC, SIGMETRICS, MobiCom, or HotNets, and when using CoNEXT's two-cycles-per-year calendar and PACMNET journal-style fit to choose the venue and the cycle by contribution shape and evidence maturity.
Its SKILL.md is about 1.7k 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
- Deciding whether a networking project belongs at ACM CoNEXT
- Should be routed to SIGCOMM
Example prompts
- “/conext-topic-selection”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Which networking community and rigor bar fits this contribution? (CoNEXT vs. SIGCOMM/NSDI/
- Which of CoNEXT's two cycles is the nearest honest deadline my evidence is ready for?
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
Conext Topic Selection loads about 1.7k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 723 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). 723 words, ~1,706 tokens.
Download SKILL.mdSave it as
.claude/skills/conext-topic-selection/SKILL.md (or your agent's skills folder).- name
- conext-topic-selection
- description
- Use when deciding whether a networking project belongs at ACM CoNEXT or should be routed to SIGCOMM, NSDI, IMC, SIGMETRICS, MobiCom, or HotNets, and when using CoNEXT's two-cycles-per-year calendar and PACMNET journal-style fit to choose the venue and the cycle by contribution shape and evidence maturity.
CoNEXT Topic Selection
Decide the venue and the cycle before drafting. CoNEXT — the ACM International Conference on emerging Networking EXperiments and Technologies, sponsored by ACM SIGCOMM — is a broad systems-and-measurement networking venue whose research papers are PACMNET journal articles. Reviewers read for a durable networking contribution evaluated on the real target (a testbed, deployment, or trace), not a one-conference result. A technically strong paper whose real lesson is about pure theory, pure ML, or a non-networking system is respected and then rejected as out of scope.
The two routing questions that matter most
Networking has several strong flagships with overlapping scope, so ask two things:
- Which networking community and rigor bar fits this contribution? (CoNEXT vs. SIGCOMM/NSDI/ IMC/SIGMETRICS/MobiCom.)
- Which of CoNEXT's two cycles is the nearest honest deadline my evidence is ready for? (December vs. June — a real lever unique to CoNEXT.)
A strong paper is often publishable at more than one venue; the nearer honest deadline and the best community fit usually win.
Sibling-venue routing table
| Signal in your project | Better home | Why |
|---|---|---|
| Broad networking contribution — systems, measurement, or architecture — evaluated on a real platform, ready for the nearer CoNEXT cycle | CoNEXT | Two-cycle PACMNET track; broad systems-networking scope |
| Top-tier, polished result aimed at the field's most selective single-deadline stage | SIGCOMM | The flagship; single annual deadline, its own bar and calendar |
| Systems paper centered on a built-and-deployed networked system with a strong implementation story | NSDI | Networked-systems design and implementation focus; USENIX proceedings |
| The whole contribution is a measurement study of the Internet or a large system | IMC | Purpose-built internet-measurement venue |
| Core is performance modeling, analysis, or evaluation methodology | SIGMETRICS | Measurement-and-modeling home (also a PACMNET-family stream) |
| Wireless/mobile systems are the heart | MobiCom / MobiSys | Mobile/wireless-systems scope |
| Early idea or position with an argument but little evaluation | HotNets (or CoNEXT Student Workshop) | Venue for provocative early work |
Contribution shapes CoNEXT rewards
- Systems + implementation + evaluation on the real target — a new mechanism in the data plane, transport, routing, or the network stack, built and run on real hardware or a faithful testbed (the ASIC-switch-insertions lineage).
- Internet / systems measurement — a campaign that changes what the community believes about how networks or protocols behave in the wild (the QUIC/TLS-performance lineage).
- Network architecture with deployment or scalability evidence — a design shown running and scaling, not merely proposed (the inter-domain multi-path lineage).
- Operational / traffic-engineering systems — measurement plus intervention at real carrier/operator scale (the hyper-giants lineage).
- Wireless and low-power networking — a model or protocol that respects a real device constraint and is validated on a testbed (the ultra-low-power broadcast lineage).
Show full SKILL.md (300 more words)Show less
The platform-realism and re-label tests
Two quick tests sharpen a borderline verdict:
- Platform-realism test: is the central claim evaluated on the real target the paper is about (switch, NIC, kernel, testbed, deployment, or real trace), or does a simulation stand in for hardware? CoNEXT rewards evidence on the real platform; a simulation-only systems claim is a re-route or a revision risk.
- Re-label test: could this paper be submitted to IMC (pure measurement), NSDI (a built system), or a theory venue unchanged and read as native there? If its heart is one of those, route accordingly; CoNEXT rewards the broad networking framing with real-platform evidence.
The model-swap test (for ML-for-networking papers)
If your paper leans on a learner or LLM, ask whether the networking lesson survives swapping the
model for another. If not, the model is the contribution and an ML venue fits better; if the
lesson is about the network (a measured phenomenon, a deployable mechanism), CoNEXT fits — evaluate
it on the real target and add a contamination-aware ablation (see
conext-experiments).
Evidence maturity, without the ladder cliché
Fit is necessary but not sufficient: the same idea sits at different doors depending on how far the evidence has come. An idea with an argument but little evaluation is a HotNets or Student-Workshop paper; a mechanism evaluated only in simulation needs a testbed before the research track; a measurement too preliminary for the bar belongs in a workshop first. Submitting one step early earns a "promising, but..." — but CoNEXT's two cycles soften this: the next honest deadline is months away, not a year.
Cheap reconnaissance before committing
[Scope] scan the last two CoNEXT programs (dblp, conferences.sigcomm.org) for your subarea
-> 3+ recent papers = a reviewer pool exists; 0 = opening or mismatch
[Citations] is your bibliography majority networking venues (CoNEXT/SIGCOMM/NSDI/IMC/SIGMETRICS)?
-> majority non-networking => reviewers read you as a visitor; naturalize the intro first
[Calendar] which CoNEXT cycle (Dec/Jun) is next, vs. SIGCOMM/NSDI/IMC dates -> route to the nearest
honest fit rather than waiting for a marginal preferenceDecision procedure
[Audience] who acts differently if the claim holds? -> operators / protocol designers / systems builders / researchers?
[Claim type] systems mechanism / measurement / architecture / operational / wireless
[Platform] is it evaluated on the real target, or only simulated? -> real => CoNEXT-ready
[CoNEXT vs siblings] pure measurement -> IMC; built system with deep impl -> NSDI; top polish -> SIGCOMM
[Cycle] December vs June -> nearest honest deadline the evidence is ready for
[Verdict] CoNEXT <cycle> / sibling venue / workshop, with a one-line reasonRun this before the writing skills; a wrong venue or cycle decision wastes every later step. When
the verdict is CoNEXT, continue with conext-workflow for the
calendar and conext-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
Files
Just SKILL.md in CoNEXT-Skills/skills/conext-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Conext 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 |
|---|---|---|---|---|---|---|
| Conext Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Acm Workshop On Hot Topics In Networksfranklee16/academic-research-skills | 223 | 1 repos | ~1.9k | Automated safety check: Pass | None | |
| 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 |
Similar skills
Linux Networking
RightNow-AI/openfang
Linux networking expert for iptables, nftables, routing, DNS, and network troubleshooting
Performing Ot Network Security Assessment
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.
- Official
Gke Networking
google/skills
Plans, configures, and manages core GKE cluster networking. An agent skill from google/skills.
Performing Network Forensics With Wireshark
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…
Performing Network Packet Capture Analysis
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…
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 Conext Topic Selection
What does Conext Topic Selection do?
A skill your agent uses when deciding whether a networking project belongs at ACM CoNEXT or should be routed to SIGCOMM, NSDI, IMC, SIGMETRICS, MobiCom, or HotNets, and when using CoNEXT's…. Conext Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a networking project belongs at ACM CoNEXT or should be routed to SIGCOMM, NSDI, IMC, SIGMETRICS, MobiCom, or HotNets, and when using CoNEXT's two-cycles-per-year calendar and PACMNET journal-style fit to choose the venue and the cycle by contribution shape and evidence maturity.
When should I use Conext Topic Selection?
Conext Topic Selection fits situations like: deciding whether a networking project belongs at ACM CoNEXT; should be routed to SIGCOMM.
How do I install Conext Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-topic-selection -a claude-code`. Or copy the skill folder (CoNEXT-Skills/skills/conext-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/conext-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Conext Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-topic-selection -a codex`. Or copy the skill folder (CoNEXT-Skills/skills/conext-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/conext-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Conext Topic Selection 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 conext-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/conext-topic-selection, .gemini/skills/conext-topic-selection, .github/skills/conext-topic-selection and .opencode/skills/conext-topic-selection in your project.
What does Conext Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Conext Topic Selection is instructions for the agent only.
Does Conext Topic Selection 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 Conext Topic Selection 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 Conext Topic Selection use?
Conext 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.
How many tokens does Conext Topic Selection use?
About 1.7k tokens (SKILL.md is roughly 6.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 Conext Topic Selection?
Skills that share tags, products or a category with Conext Topic Selection: Acm Workshop On Hot Topics In Networks (franklee16/academic-research-skills, 223 stars), Linux Networking (RightNow-AI/openfang, 18k stars), Performing Ot Network Security Assessment (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Gke Networking (google/skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Conext Topic Selection?
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.