Arize Evaluator
github/awesome-copilot
Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and…
Agent skill
Nsdi Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when preparing an accepted NSDI paper's artifact for badge evaluation — packaging code, traces, and testbed recipes for the AEC, choosing which badges to pursue, meeting…
MITAuto-check passed
Install Nsdi Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-artifact-evaluation --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-artifact-evaluation .claude/skills/nsdi-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-artifact-evaluation into .claude/skills/nsdi-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-artifact-evaluation", 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-artifact-evaluationType 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-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-artifact-evaluation --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-artifact-evaluation .agents/skills/nsdi-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-artifact-evaluation into .agents/skills/nsdi-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-artifact-evaluation", 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-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-artifact-evaluation --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-artifact-evaluation .cursor/skills/nsdi-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-artifact-evaluation into .cursor/skills/nsdi-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-artifact-evaluation", 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-artifact-evaluation--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-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-artifact-evaluation --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-artifact-evaluation .gemini/skills/nsdi-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-artifact-evaluation into .gemini/skills/nsdi-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-artifact-evaluation", 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-artifact-evaluationInstalls 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-artifact-evaluation -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-artifact-evaluation .github/skills/nsdi-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-artifact-evaluation into .github/skills/nsdi-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-artifact-evaluation", 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-artifact-evaluation -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-artifact-evaluation --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-artifact-evaluation .opencode/skills/nsdi-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-artifact-evaluation into .opencode/skills/nsdi-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-artifact-evaluation", 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
nsdi-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 718 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when preparing an accepted NSDI paper's artifact for badge evaluation — packaging code, traces, and testbed recipes for the AEC, choosing which badges to pursue, meeting…
- Works in 3 steps: Fresh VM or container, no lab dotfiles,… → Stopwatch on: record where the reader… → Fix the artifact, not the reader — each…
- Preparing an accepted NSDI papers artifact for badge evaluation — packaging code
- SKILL.md covers What the '26 cycle established, Choose badges like claims, The Community Award changes… and Package for a stranger with a…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Nsdi Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted NSDI paper's artifact for badge evaluation — packaging code, traces, and testbed recipes for the AEC, choosing which badges to pursue, meeting Zenodo-style permanence expectations, and timing public release to stay eligible for the Community Award.
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.
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
- Preparing an accepted NSDI papers artifact for badge evaluation — packaging code
- Testbed recipes for the AEC
- Choosing which badges to pursue
- Meeting Zenodo-style permanence expectations
Example prompts
- “/nsdi-artifact-evaluation”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Fresh VM or container, no lab dotfiles, no cached dependencies.
- Stopwatch on: record where the reader stalls, every undocumented assumption, and
- Fix the artifact, not the reader — each stall becomes a README line or a setup
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
Nsdi Artifact Evaluation loads about 1.6k tokens when it runs. Until then it costs about 76 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.
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). 718 words, ~1,639 tokens.
Download SKILL.mdSave it as
.claude/skills/nsdi-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- nsdi-artifact-evaluation
- description
- Use when preparing an accepted NSDI paper's artifact for badge evaluation — packaging code, traces, and testbed recipes for the AEC, choosing which badges to pursue, meeting Zenodo-style permanence expectations, and timing public release to stay eligible for the Community Award.
NSDI Artifact Evaluation
Artifact evaluation at NSDI is post-acceptance and opt-in: accepted authors package what the paper is made of, an Artifact Evaluation Committee tries it, and earned badges travel with the paper. Mechanics below follow the NSDI '26 Call for Artifacts as rendered on 2026-07-08 — the '27 call was not yet retrievable (待核实), so treat '26 as the model and reread the live page after acceptance.
What the '26 cycle established
- Evaluation was open to all accepted papers.
- Three separate badges; a paper may earn one, two, or all three. The confirmed name is Artifacts Available — awarded when artifacts are retrievable permanently and publicly, with Zenodo encouraged (public funding, DOI assignment). The other two badge names in the NSDI '26 wording were not fully retrievable (待核实); USENIX's scheme at sibling venues pairs Available with functionality and results-reproduction badges.
- Authors choose which badges the AEC should consider at artifact-submission time — the evaluation is scoped to what you claim.
- '26 timeline anchor: artifacts due July 31, 2025, decisions October 14, 2025 — i.e., months after the first acceptance cohort, weeks-scale effort windows. Expect cohort-specific dates in '27 (待核实).
Choose badges like claims
The badge menu is a claims menu; over-claiming wastes AEC goodwill exactly as over-claiming in the paper wastes reviewer goodwill.
| You can honestly promise | Pursue | Do not pursue |
|---|---|---|
| The bits are public forever (DOI'd archive) | Available | — |
| An evaluator can build and run the core on documented hardware | + functionality-level badge | results claims tied to your production traces |
| Headline figures regenerate within characterized variance on accessible hardware | + reproduction-level badge | anything requiring your private fleet |
The networked-systems complication: results badges collide with topology dependence.
If p99.9 numbers need 80 nodes and a specific RTT matrix, ship a documented
downscaled configuration with expected outputs at that scale, and say explicitly
which paper trends survive downscaling and which do not (nsdi-reproducibility).
The Community Award changes your timeline
NSDI's Community Award goes to the best paper whose code and/or dataset is made
publicly available by the final-papers deadline. Note the trigger: not badge
completion — public release by camera-ready time. Teams that treat openness as a
post-AE cleanup task silently exit the running. If the artifact will be public
anyway, make it public early enough to count (nsdi-camera-ready).
Package for a stranger with a deadline
AEC members evaluate many artifacts on volunteer time. The artifact that wins is the one where the first fifteen minutes succeed:
artifact/
README.md # claims -> badge(s) sought; hardware/software needs up front
GETTING_STARTED.md # <=30 min smoke path: build, tiny topology, one sanity result
CLAIMS.md # paper claim -> experiment -> script -> expected output ± variance
setup/ # topology recipes: containers/CloudLab profile/VM configs
traces/ # shippable traces or synthetic generators + fidelity notes
experiments/<id>/ # one runnable unit per paper experiment (run.sh + provenance)
figures/Makefile # regenerate paper figures from logs (fresh or shipped)
LICENSE # explicit license; unlicensed code is not "available"NSDI-specific packaging notes:
- State the variance. Tail-latency reproduction is stochastic; publish the spread you observed so the evaluator can tell noise from failure.
- Solve the testbed problem for them: a public-testbed profile (e.g., CloudLab) or an emulated topology beats instructions that assume your lab's switches.
- Trace substitutions documented: where production data cannot ship, the synthetic stand-in's construction and its fidelity limits are part of the artifact, not a footnote.
- Kernel/NIC settings pinned — the classic source of "works for authors only."
Show full SKILL.md (239 more words)Show less
Dry-run protocol before submission
The single highest-yield hour: a lab member who did not build the artifact follows
GETTING_STARTED.md on a machine you did not prepare.
- Fresh VM or container, no lab dotfiles, no cached dependencies.
- Stopwatch on: record where the reader stalls, every undocumented assumption, and the wall-clock to first sanity result.
- Fix the artifact, not the reader — each stall becomes a README line or a setup script, then re-run with a second novice if anything structural changed.
Process notes
- By artifact-submission time you provide a stable URL or uploaded archive; from there, treat the artifact as frozen except through communication with the AEC.
- Evaluation is typically interactive at systems venues — expect clarification questions and budget author time during the window rather than vacationing through it.
- Badges recognize the artifact; they change neither the paper's acceptance nor its
page budget. The two-page artifact-appendix conventions of some sibling venues are
not an NSDI '26 fact — final-paper packaging follows
nsdi-camera-readyand the live instructions.
Common failure modes at systems AECs
- The build assumes the authors' distribution/toolchain; pin everything or ship the container.
- Scripts hardcode the lab's hostnames, interface names, or IP ranges.
- Expected outputs given as exact numbers with no variance band — evaluators "fail" runs that are actually fine.
- The trace download link requires the authors' institutional login.
- The README's experiment names do not match the paper's section numbers, forcing the evaluator to reverse-map claims.
Output format
[Badge plan] sought badges + honest basis for each
[Fifteen-minute test] GETTING_STARTED verified on a clean machine? time observed
[Scale strategy] downscale config + surviving-trends statement present?
[Trace shippability] per-dataset: ship / substitute / withhold (documented)
[Community Award] public release date vs final-papers deadline
[Gaps] ordered fixes before artifact submission© 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 NSDI-Skills/skills/nsdi-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Nsdi Artifact Evaluation 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 Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Arize Evaluatorgithub/awesome-copilot | 40k | 1 repos | ~8.1k | Automated safety check: Notes | MIT | |
| Artifacts Buildernexu-io/open-design | 100k | — | ~347 | Automated safety check: Pass | Apache-2.0 | |
| Isca Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Icse Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Osdi Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
- Official
Artifacts Builder
nexu-io/open-design
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).
Isca Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when preparing an accepted ISCA paper's artifact for evaluation under the ACM Review and Badging policy — scoping which results are reproducible within evaluator budgets…
Icse Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when preparing an artifact for the ICSE Artifact Evaluation track after paper acceptance, covering the ACM badge system (Available, Reusable, Results Reproduced/Replicated)…
Osdi Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when preparing an OSDI artifact for sysartifacts-run evaluation — the post-acceptance timeline, the 2026 narrowing to a single Artifacts Available badge, Zenodo-grade…
Ccs Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging ACM CCS artifacts for the artifact-evaluation committee and the ACM badges — Artifacts Available, Artifacts Evaluated Functional, Artifacts Evaluated Reusable…
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 Nsdi Artifact Evaluation
What does Nsdi Artifact Evaluation do?
A skill your agent uses when preparing an accepted NSDI paper's artifact for badge evaluation — packaging code, traces, and testbed recipes for the AEC, choosing which badges to pursue, meeting…. Nsdi Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted NSDI paper's artifact for badge evaluation — packaging code, traces, and testbed recipes for the AEC, choosing which badges to pursue, meeting Zenodo-style permanence expectations, and timing public release to stay eligible for the Community Award.
When should I use Nsdi Artifact Evaluation?
Nsdi Artifact Evaluation fits situations like: preparing an accepted NSDI papers artifact for badge evaluation — packaging code; testbed recipes for the AEC; choosing which badges to pursue; meeting Zenodo-style permanence expectations.
How do I install Nsdi Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-artifact-evaluation -a claude-code`. Or copy the skill folder (NSDI-Skills/skills/nsdi-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/nsdi-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Nsdi Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-artifact-evaluation -a codex`. Or copy the skill folder (NSDI-Skills/skills/nsdi-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/nsdi-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Nsdi Artifact Evaluation 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 nsdi-artifact-evaluation -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-artifact-evaluation, .gemini/skills/nsdi-artifact-evaluation, .github/skills/nsdi-artifact-evaluation and .opencode/skills/nsdi-artifact-evaluation in your project.
What does Nsdi Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Nsdi Artifact Evaluation is instructions for the agent only.
Does Nsdi Artifact Evaluation 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 Nsdi Artifact Evaluation 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 Nsdi Artifact Evaluation use?
Nsdi Artifact Evaluation 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 Nsdi Artifact Evaluation use?
About 1.6k tokens (SKILL.md is roughly 6.6k 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 Nsdi Artifact Evaluation?
Skills that share tags, products or a category with Nsdi Artifact Evaluation: Arize Evaluator (github/awesome-copilot, 40k stars), Artifacts Builder (nexu-io/open-design, 100k stars), Isca Artifact Evaluation (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Icse Artifact Evaluation (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nsdi Artifact Evaluation?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.