Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
A skill your agent uses when deciding whether a security project belongs at NDSS — the Network and Distributed System Security Symposium — or should route to IEEE S&P, USENIX Security, CCS, PETS…
Install Ndss Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-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/NDSS-Skills/skills/ndss-topic-selection .claude/skills/ndss-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 "ndss-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-topic-selection into .claude/skills/ndss-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-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/NDSS-Skills/skills/ndss-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 ndss-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-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/NDSS-Skills/skills/ndss-topic-selection .agents/skills/ndss-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 "ndss-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-topic-selection into .agents/skills/ndss-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-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 ndss-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-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/NDSS-Skills/skills/ndss-topic-selection .cursor/skills/ndss-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 "ndss-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-topic-selection into .cursor/skills/ndss-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-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 NDSS-Skills/skills/ndss-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 ndss-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-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/NDSS-Skills/skills/ndss-topic-selection .gemini/skills/ndss-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 "ndss-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-topic-selection into .gemini/skills/ndss-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-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 ndss-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 ndss-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/NDSS-Skills/skills/ndss-topic-selection .github/skills/ndss-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 "ndss-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-topic-selection into .github/skills/ndss-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-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 ndss-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 ndss-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/NDSS-Skills/skills/ndss-topic-selection .opencode/skills/ndss-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 "ndss-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-topic-selection into .opencode/skills/ndss-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-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
ndss-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 571 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 security project belongs at NDSS — the Network and Distributed System Security Symposium — or should route to IEEE S&P, USENIX Security, CCS, PETS…
- Works in 3 steps: The wire test. Describe the contribution… → The deployment-envelope test. NDSS… → The adversary-ownership test. Someone…
- Deciding whether a security project belongs at NDSS — the Network and Distributed System Security Symposium —
- SKILL.md covers Three fit tests, Routing against the neighbors, NDSS-specific constraints that… and Decision procedure, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ndss Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a security project belongs at NDSS — the Network and Distributed System Security Symposium — or should route to IEEE S&P, USENIX Security, CCS, PETS, IMC, or ACSAC, applying NDSS's networked-adversary and deployment-realism tests before any writing begins.
Its SKILL.md is about 1.4k 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 DevOps & Cloud. 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 security project belongs at NDSS — the Network and Distributed System Security Symposium —
- Should route to IEEE S&P
- USENIX Security
- Applying NDSSs networked-adversary and deployment-realism tests before any writing begins
Example prompts
- “/ndss-topic-selection”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- The wire test. Describe the contribution without mentioning a network, a protocol, a
- The deployment-envelope test. NDSS repeatedly rewards work whose design is forced
- The adversary-ownership test. Someone concrete must be attacking something concrete.
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
Ndss Topic Selection loads about 1.4k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 571 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). 571 words, ~1,350 tokens.
Download SKILL.mdSave it as
.claude/skills/ndss-topic-selection/SKILL.md (or your agent's skills folder).- name
- ndss-topic-selection
- description
- Use when deciding whether a security project belongs at NDSS — the Network and Distributed System Security Symposium — or should route to IEEE S&P, USENIX Security, CCS, PETS, IMC, or ACSAC, applying NDSS's networked-adversary and deployment-realism tests before any writing begins.
NDSS Topic Selection
NDSS is the Internet Society's slice of the security big four, and its center of gravity is literal: security of things that are networked or distributed — protocols, the web, DNS and routing, cloud and edge infrastructure, IoT fleets, and the measurement of all of the above under attack. Work can be excellent and still be mis-routed here. Run these tests before a word is drafted; the cheapest rejection is the one you never submit into.
Three fit tests
- The wire test. Describe the contribution without mentioning a network, a protocol, a distributed deployment, or Internet-scale phenomena. If the description survives intact, the paper's heart is somewhere else — a crypto venue, a software-engineering venue, an ML venue — and NDSS reviewers will sense it.
- The deployment-envelope test. NDSS repeatedly rewards work whose design is forced by real-world constraints: no source code, no firmware access, gateway-class hardware, off-path adversaries, providers who must act unilaterally. If your evaluation only runs in a simulator with parameters you chose, expect the "would this survive contact with the Internet?" objection.
- The adversary-ownership test. Someone concrete must be attacking something concrete. A robustness study without a capability-bounded adversary is a reliability paper.
Routing against the neighbors
| Signal in your project | Better first target | Why |
|---|---|---|
| Networked/distributed adversary, deployable result | NDSS | Exactly the center of scope |
| Systematization (SoK) ambition | IEEE S&P | The labeled SoK lane lives there, not at NDSS |
| Broad systems security, OS/hardware depth | USENIX Security | Its community leans systems-artifact |
| Applied-crypto protocol with proofs as the core | CCS or a crypto venue | Proof-first work fits their PC composition |
| Privacy as the primary lens, PET construction | PETS | Dedicated reviewer pool, journal-style rounds |
| Internet measurement with no adversarial angle | IMC | Measurement without attack is IMC's home turf |
| Operational/practitioner defense, modest novelty | ACSAC | Applied bar, friendlier to incremental hardening |
Route by contribution shape and reviewer community, never by prestige ranking or by which deadline lands next — the workflow skill covers calendar strategy separately.
Show full SKILL.md (244 more words)Show less
NDSS-specific constraints that affect the decision
- Two cycles, no same-year retry. A paper rejected in the 2027 summer cycle cannot return with major overlap in the 2027 fall cycle. Choosing NDSS prematurely can burn the whole edition, not one deadline (CFP, checked 2026-07-08).
- Six submissions per author per cycle. Large groups must ration slots; a marginal-fit paper spends a slot a strong-fit paper may need.
- Ethics gate at entry. Projects built on live scanning, user data, or unpatched vulnerabilities need a disclosure-and-mitigation story at submission time; an Ethics Review Board can sink an otherwise strong paper. If the ethics story cannot be told, the project is not NDSS-ready regardless of technical merit.
- The 2027 edition meets in Seoul (22-26 March) — the first move away from San Diego — so factor travel and funding for the team into the venue choice like any other cost.
Decision procedure
1. State the adversary: capabilities, cost, vantage (on-path / off-path / insider).
2. Name the networked or distributed system under attack or defense.
3. Say which real-world constraint forces your design (the "envelope").
4. Draft the one-sentence delta vs. the nearest big-four paper of the last 3 years.
5. Confirm the ethics story is tellable today (disclosure state, harm handling).
6. If any of 1-5 fails → run the routing table above and pick the venue whose
reviewers naturally ask the questions your paper actually answers.Anti-patterns seen at this venue
- ML paper wearing a security costume: novel model, borrowed intrusion dataset, no
adversary reasoning. NDSS accepts ML-heavy work when the deployment envelope shapes the
method (see Kitsune in
../../resources/exemplars/library.md); it rejects the inverse. - Attack without a victim population: a clever trick demonstrated on one lab target, with no argument about prevalence or preconditions in the wild.
- Defense against yesterday's attacker: evaluation only against published, non-adaptive attacks — reviewers here will improvise the adaptive one during discussion.
- Journal pacing: saving the strongest result for a follow-up. NDSS review gives no credit for a roadmap.
Output format
[NDSS fit] Strong / Plausible / Mis-routed
[Wire test] pass/fail — one line
[Deployment envelope] <the real constraint that shapes the design, or "none">
[Adversary] <capabilities and vantage in one line>
[Ethics story] tellable now / blocked by <item>
[Cycle risk] <summer/fall implications, cap usage, no-retry exposure>
[Alternative venue] <name + one-line reason, if fit is not Strong>© 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 NDSS-Skills/skills/ndss-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ndss 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 |
|---|---|---|---|---|---|---|
| Ndss Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Monitor CInrwl/nx | 29k | 6 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Terraform and OpenTofu Guideagentscope-ai/QwenPaw | 35k | 6 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 9 repos | ~4.3k | Automated safety check: Pass | None | |
| Openclaw Live Updateropenclaw/openclaw | 392k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence |
Similar skills
Terraform and OpenTofu Guide
agentscope-ai/QwenPaw
Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
- Official
Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
KubeSphere Multi-Tenant Management
kubesphere/kubesphere
Creates and queries KubeSphere users, workspaces and projects and assigns built-in roles, defaulting to least privilege and never deleting anything.
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 Ndss Topic Selection
What does Ndss Topic Selection do?
A skill your agent uses when deciding whether a security project belongs at NDSS — the Network and Distributed System Security Symposium — or should route to IEEE S&P, USENIX Security, CCS, PETS…. Ndss Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a security project belongs at NDSS — the Network and Distributed System Security Symposium — or should route to IEEE S&P, USENIX Security, CCS, PETS, IMC, or ACSAC, applying NDSS's networked-adversary and deployment-realism tests before any writing begins.
When should I use Ndss Topic Selection?
Ndss Topic Selection fits situations like: deciding whether a security project belongs at NDSS — the Network and Distributed System Security Symposium —; should route to IEEE S&P; USENIX Security; applying NDSSs networked-adversary and deployment-realism tests before any writing begins.
How do I install Ndss Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-topic-selection -a claude-code`. Or copy the skill folder (NDSS-Skills/skills/ndss-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ndss-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Ndss Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-topic-selection -a codex`. Or copy the skill folder (NDSS-Skills/skills/ndss-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ndss-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Ndss 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 ndss-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/ndss-topic-selection, .gemini/skills/ndss-topic-selection, .github/skills/ndss-topic-selection and .opencode/skills/ndss-topic-selection in your project.
What does Ndss Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Ndss Topic Selection is instructions for the agent only.
Does Ndss 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 Ndss 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 Ndss Topic Selection use?
Ndss 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 Ndss Topic Selection use?
About 1.4k tokens (SKILL.md is roughly 5.4k 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 Ndss Topic Selection?
Skills that share tags, products or a category with Ndss Topic Selection: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 35k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Openclaw Live Updater (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ndss 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.