A skill your agent uses when designing or auditing the evaluation of an NSDI submission — choosing traces, testbeds, and deployment evidence, sizing scale and failure-injection experiments, picking…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-experiments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-experiments --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/NSDI-Skills/skills/nsdi-experiments .claude/skills/nsdi-experiments && 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 "nsdi-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-experiments into .claude/skills/nsdi-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-experiments", 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/NSDI-Skills/skills/nsdi-experimentsType 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 nsdi-experiments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-experiments --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/NSDI-Skills/skills/nsdi-experiments .agents/skills/nsdi-experiments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nsdi-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-experiments into .agents/skills/nsdi-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-experiments", 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 nsdi-experiments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-experiments --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/NSDI-Skills/skills/nsdi-experiments .cursor/skills/nsdi-experiments && 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 "nsdi-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-experiments into .cursor/skills/nsdi-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-experiments", 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 NSDI-Skills/skills/nsdi-experiments--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 nsdi-experiments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-experiments --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/NSDI-Skills/skills/nsdi-experiments .gemini/skills/nsdi-experiments && 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 "nsdi-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-experiments into .gemini/skills/nsdi-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-experiments", 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 nsdi-experimentsInstalls 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 nsdi-experiments -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/NSDI-Skills/skills/nsdi-experiments .github/skills/nsdi-experiments && 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 "nsdi-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-experiments into .github/skills/nsdi-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-experiments", 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 nsdi-experiments -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 nsdi-experiments --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/NSDI-Skills/skills/nsdi-experiments .opencode/skills/nsdi-experiments && 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 "nsdi-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-experiments into .opencode/skills/nsdi-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-experiments", 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.
nsdi-experimentsA skill your agent uses when designing or auditing the evaluation of an NSDI submission — choosing traces, testbeds, and deployment evidence, sizing scale and failure-injection experiments, picking…
Nsdi Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing the evaluation of an NSDI submission — choosing traces, testbeds, and deployment evidence, sizing scale and failure-injection experiments, picking baselines that fight back, and reporting tail behavior so networked-systems reviewers can see where the design wins, loses, and breaks.
Its SKILL.md is about 1.6k 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, covering Chaos engineering. 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.
3 steps, taken from the first numbered list in SKILL.md.
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.
Nsdi Experiments loads about 1.6k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 718 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). 718 words, ~1,620 tokens.
.claude/skills/nsdi-experiments/SKILL.md (or your agent's skills folder).NSDI's phrase is "practical evaluation," and its reviewer culture decodes that as: realistic traffic, honest baselines, visible tails, and at least one experiment where the system is hurt on purpose. Design the evaluation as a set of questions the paper must answer, then build the smallest experiment matrix that answers them.
Climb as high as the project honestly can, and say plainly which rung you are on:
nsdi-topic-selection).Write the evaluation section's subsection titles as questions first — Does the lease mechanism help under regional congestion? What does it cost at baseline? When does it misfire? — then design one experiment per question. The inverted approach (run everything, narrate survivors) produces the benchmark tour that NSDI reviews call unfocused.
A minimal matrix for a design-track paper:
| Question | Experiment | Metrics that answer it |
|---|---|---|
| Does it work under the motivating pain? | replay of the incident-class workload | p99/p99.9 latency, goodput during events |
| What does it cost when the pain is absent? | baseline weeks, no faults | median latency, CPU/memory/bandwidth overhead |
| Why does it work? | component breakdown / ablation | per-mechanism contribution |
| Does it scale? | node / connection / load sweeps | knee location, per-node cost curve |
| When does it break? | adversarial or boundary regimes | the regime where baselines win |
| Does it survive failures? | injected partitions, crashes, stragglers | recovery time, correctness under churn |
Networked-systems phenomena live in distributions and in time:
nsdi-writing-style).Per-experiment provenance record (kept as the runs happen, machine-readable):
topology: nodes, cores/RAM, NIC speed, switch model, RTT matrix
software: kernel, framework versions, config diffs from defaults
workload: trace id + collection context + scaling transform
fault schedule: what was injected, when, by what tool
outputs: raw logs location + commit hash of analysis scriptsThis record is simultaneously the reproducibility ledger (nsdi-reproducibility),
the artifact-evaluation seed (nsdi-artifact-evaluation), and the insurance policy
for a one-shot revision that demands re-running experiments months later on the same
setup (nsdi-author-response).
Evaluation scope should be sized to the gate being targeted (nsdi-workflow): the
question map above, costed in machine-days, tells you whether the fall gate is
reachable or the plan is quietly a spring plan. Two rules of thumb from systems
deadline archaeology: trace-replay pipelines take twice as long to stabilize as to
run, and the break-it experiments — the ones reviewers value most — are always the
ones cut when the schedule slips. Protect them by running the failure-injection
matrix before the final scale sweeps, not after.
[Evidence rung] micro / trace+testbed / deployment (claimed vs actual)
[Question map] question -> experiment -> metric (gaps flagged)
[Baseline audit] incumbent? tuned? do-less alternative?
[Tail report] percentiles + distribution figures present? y/n per claim
[Break experiment] regime where the design loses: <named or MISSING>
[Priority additions] ordered by review-risk reduction per machine-week© 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 NSDI-Skills/skills/nsdi-experiments of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Nsdi Experiments 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 |
|---|---|---|---|---|---|---|
| Nsdi Experiments this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Executing Distributed System Testsshenli/distributed-system-testing | 231 | — | ~5.1k | Automated safety check: Notes | MIT | |
| Audit Reviewtestflows/TestFlows-GitHub-Hetzner-Runners | 102 | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Chaos EngineerJeffallan/claude-skills | 12k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Chaos Dr Testharness/harness-skills | 115 | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Chaos Experimentharness/harness-skills | 115 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 |
shenli/distributed-system-testing
A skill your agent uses when running a previously designed distributed-systems test plan against a real or simulated cluster — driving fault injection, workload, chaos scenarios, linearizability /…
testflows/TestFlows-GitHub-Hetzner-Runners
Perform deep feature audits with transition-matrix and logical fault-injection validation.
Jeffallan/claude-skills
Designs chaos experiments, failure injection and game days for distributed systems, with blast radius limits, rollback plans and written learnings.
harness/harness-skills
A skill your agent uses when working with Chaos Engineering steps inside a Harness pipeline.
harness/harness-skills
A skill your agent uses when the user asks to create, edit, update, design, or configure a Harness Chaos Experiment — including faults, probes, actions, experiment YAML, fault injection, pod-delete…
Jeffallan/claude-skills
Defines SLIs, SLOs and error budgets, and sets up golden-signal monitoring, blameless postmortems, toil automation and chaos experiments for production systems.
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…
Categories
A skill your agent uses when designing or auditing the evaluation of an NSDI submission — choosing traces, testbeds, and deployment evidence, sizing scale and failure-injection experiments, picking…. Nsdi Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing the evaluation of an NSDI submission — choosing traces, testbeds, and deployment evidence, sizing scale and failure-injection experiments, picking baselines that fight back, and reporting tail behavior so networked-systems reviewers can see where the design wins, loses, and breaks.
Nsdi Experiments fits situations like: auditing the evaluation of an NSDI submission — choosing traces; deployment evidence; sizing scale and failure-injection experiments; picking baselines that fight back.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-experiments -a claude-code`. Or copy the skill folder (NSDI-Skills/skills/nsdi-experiments in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/nsdi-experiments in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-experiments -a codex`. Or copy the skill folder (NSDI-Skills/skills/nsdi-experiments in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/nsdi-experiments 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 nsdi-experiments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nsdi-experiments, .gemini/skills/nsdi-experiments, .github/skills/nsdi-experiments and .opencode/skills/nsdi-experiments in your project.
SKILL.md names no scripts, command-line tools or credentials: Nsdi Experiments 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.
Nsdi Experiments 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.6k tokens (SKILL.md is roughly 6.5k 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 Nsdi Experiments: Executing Distributed System Tests (shenli/distributed-system-testing, 231 stars), Audit Review (testflows/TestFlows-GitHub-Hetzner-Runners, 102 stars), Chaos Engineer (Jeffallan/claude-skills, 12k stars) and Chaos Dr Test (harness/harness-skills, 115 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,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
