Datasets
Arize-ai/phoenix
Understand what a Phoenix dataset is and reason well about its examples, outputs, splits, and how it feeds evaluators and experiments.
Agent skill
Webconf Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging datasets, models, or code for the Web Conference (WWW) Artifacts Available badge or for reviewer scrutiny, covering archival-repository choice, the…
MITAuto-check passed
Install Webconf Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-artifact-evaluation .claude/skills/webconf-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 "webconf-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-artifact-evaluation into .claude/skills/webconf-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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/The-Web-Conference-Skills/skills/webconf-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 webconf-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-artifact-evaluation .agents/skills/webconf-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 "webconf-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-artifact-evaluation into .agents/skills/webconf-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 webconf-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-artifact-evaluation .cursor/skills/webconf-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 "webconf-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-artifact-evaluation into .cursor/skills/webconf-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 The-Web-Conference-Skills/skills/webconf-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 webconf-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-artifact-evaluation .gemini/skills/webconf-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 "webconf-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-artifact-evaluation into .gemini/skills/webconf-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 webconf-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 webconf-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/The-Web-Conference-Skills/skills/webconf-artifact-evaluation .github/skills/webconf-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 "webconf-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-artifact-evaluation into .github/skills/webconf-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 webconf-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 webconf-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/The-Web-Conference-Skills/skills/webconf-artifact-evaluation .opencode/skills/webconf-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 "webconf-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-artifact-evaluation into .opencode/skills/webconf-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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
webconf-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 748 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when packaging datasets, models, or code for the Web Conference (WWW) Artifacts Available badge or for reviewer scrutiny, covering archival-repository choice, the…
- Works in 4 steps: Freely shareable: your code, your… → Shareable as derivatives: URL lists,… → Shareable on request / gated: user-level… → …
- Packaging datasets
- SKILL.md covers What the badge checks vs. what…, Web-data artifacts are legally…, Minimum viable package and During review vs. after…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Webconf Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging datasets, models, or code for the Web Conference (WWW) Artifacts Available badge or for reviewer scrutiny, covering archival-repository choice, the light-verification bar, web-data licensing and takedown realities, anonymized artifacts during review, and what the badge does and does not certify.
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
- Packaging datasets
- Code for the Web Conference (WWW) Artifacts Available badge
- For reviewer scrutiny
- Covering archival-repository choice
Example prompts
- “/webconf-artifact-evaluation”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Freely shareable: your code, your synthetic data, aggregate statistics.
- Shareable as derivatives: URL lists, item IDs, hydration scripts — release
- Shareable on request / gated: user-level data behind a data-use agreement;
- Not shareable: proprietary logs. Say so in the paper's availability
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
Webconf Artifact Evaluation loads about 1.6k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 748 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). 748 words, ~1,642 tokens.
Download SKILL.mdSave it as
.claude/skills/webconf-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- webconf-artifact-evaluation
- description
- Use when packaging datasets, models, or code for the Web Conference (WWW) Artifacts Available badge or for reviewer scrutiny, covering archival-repository choice, the light-verification bar, web-data licensing and takedown realities, anonymized artifacts during review, and what the badge does and does not certify.
Web Conference Artifact Evaluation
The Web Conference's 2026 artifact program was an availability badge, not a reproducibility audit: a volunteer committee performed a light verification that the artifact exists, is downloadable from a publicly accessible archival repository, and carries minimal instructions. Accepted papers from all tracks of the main or companion proceedings — except workshop papers — could apply, with the artifact submitted at camera-ready time. Design the artifact to clear that bar first, then exceed it for your actual readers.
What the badge checks vs. what readers need
| Dimension | Badge bar (2026) | Reader bar |
|---|---|---|
| Location | Public archival repository | Same, plus a mirror for big files |
| Persistence | Link resolves at check time | DOI/versioned, survives repo moves |
| Instructions | "Minimal" access instructions | Environment, run commands, expected output |
| Completeness | Artifact "exists" | Enough to regenerate headline tables |
| Legality | Not assessed | Licenses and platform ToS actually permit sharing |
"Archival" is the operative word: a personal GitHub repository can be deleted or rewritten and historically has not counted as archival for ACM badging purposes. Deposit a release snapshot in Zenodo, figshare, or an institutional repository that mints DOIs, and let GitHub be the development mirror the README points to.
Web-data artifacts are legally different
This venue's artifacts are dominated by crawls, platform datasets, interaction logs, and derived embeddings — objects with third-party rights attached. Decide the sharing tier per component before promising anything in the paper:
- Freely shareable: your code, your synthetic data, aggregate statistics.
- Shareable as derivatives: URL lists, item IDs, hydration scripts — release the pointers plus the pipeline, not the content, when platform terms forbid redistribution (the standard pattern for social-media datasets).
- Shareable on request / gated: user-level data behind a data-use agreement; document the request path in the README so the artifact is still "available."
- Not shareable: proprietary logs. Say so in the paper's availability statement and ship the measurement code anyway.
A takedown-resilient design states the crawl window, preserves checksums of the original corpus, and includes the re-crawl script — so when 15% of URLs die (they will), a later user can quantify exactly what changed.
Minimum viable package
artifact-v1.0/ (deposited at Zenodo, DOI 10.5281/zenodo.XXXXXXX)
├── README.md # what this is, paper title, 3-command quickstart
├── LICENSE # code license + per-dataset terms table
├── environment.yml # or Dockerfile / requirements.txt with pins
├── data/
│ ├── MANIFEST.md # per-file: source, crawl window, row counts, sha256
│ └── ids/ # hydration pointers where content can't ship
├── src/ # training/analysis code, seeds surfaced as flags
├── scripts/
│ ├── reproduce_table2.sh
│ └── recrawl.py # dead-link accounting for future users
└── CITATION.cffThe single highest-leverage file is reproduce_table2.sh — one command per
headline result. Badge reviewers may not run it; the citing researcher eighteen
months later definitely will.
During review vs. after acceptance
Review at this venue is double-blind and the appendix is the sanctioned home for
reproducibility detail, so during review the artifact appears as an anonymized
link (if at all) with no author-identifying paths, git history, or platform account
names. After acceptance, the flow inverts: mint the DOI first, cite it in the
camera-ready, then file the badge application alongside the final files — the
badge's availability check needs the link that will live in the published paper.
Sequence details sit in webconf-camera-ready; content standards for what the
package proves sit in webconf-reproducibility.
Show full SKILL.md (281 more words)Show less
Vignette: the crawl that got a takedown notice
A team releases a 40M-page news crawl with their WWW paper. Eight months later, a publisher demands removal of its articles. Because the artifact followed the tiered design, the response costs an afternoon, not the artifact: the Zenodo deposit v1.1 removes the publisher's content files, the manifest documents the removal (URLs retained as pointers, checksums preserved), the hydration script still lets rights-holding users rebuild the full corpus, and the paper's DOI citation now resolves to a version history that explains itself. The counterfactual design — one monolithic tarball with raw content — would have forced a full withdrawal and orphaned every downstream citation. Design for the takedown on day one; on the Web it is a when, not an if.
Badge application dry run
Before filing with the camera-ready, simulate the committee's light check from a clean machine and a logged-out browser:
- The link in the paper resolves to the archival record (not a login page, not a personal homepage redirect).
- The record shows a version, a license, and a README visible without download.
- One file downloads successfully and matches its manifest checksum.
- The README's first screen states what the artifact is and which paper it accompanies — the committee volunteer decides in minutes.
Honest labeling
The Artifacts Available badge certifies existence, not correctness. Do not write "our results are independently verified" on the strength of it. Conversely, an artifact too encumbered to badge (tier 3-4 data) does not bar publication — the paper just needs an availability statement that says precisely what is released, what is gated and why, and what a reader can still verify with the released parts.
Output format
[Artifact tiering] code=<tier> data=<tiers per set> models=<tier>
[Badge eligibility] track eligible? archival deposit? DOI minted?
[Legal check] platform ToS / license conflicts found: <list or none>
[Decay plan] crawl window stated? checksums? recrawl script?
[One-command repro] present for headline tables: yes/no
[Availability statement] drafted for the paper: yes/no© 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 The-Web-Conference-Skills/skills/webconf-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Webconf 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 |
|---|---|---|---|---|---|---|
| Webconf Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| DatasetsArize-ai/phoenix | 12k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Arize Evaluatorgithub/awesome-copilot | 40k | 1 repos | ~8.1k | Automated safety check: Notes | MIT | |
| Ccs Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~969 | Automated safety check: Pass | MIT | |
| Atc Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Mobisys Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
- Official
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…
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…
Atc Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) artifact for the USENIX-lineage evaluation scheme — earning the Artifacts Available…
Mobisys Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging a MobiSys artifact for the Artifact Evaluation Committee — choosing among the three independent ACM badges (Available, Evaluated–Functional, Results…
Fast Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging a USENIX FAST artifact for the USENIX Artifact Evaluation scheme (Artifacts Available, Artifacts Functional, Results Reproduced), covering what a storage AEC…
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 Webconf Artifact Evaluation
What does Webconf Artifact Evaluation do?
A skill your agent uses when packaging datasets, models, or code for the Web Conference (WWW) Artifacts Available badge or for reviewer scrutiny, covering archival-repository choice, the…. Webconf Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging datasets, models, or code for the Web Conference (WWW) Artifacts Available badge or for reviewer scrutiny, covering archival-repository choice, the light-verification bar, web-data licensing and takedown realities, anonymized artifacts during review, and what the badge does and does not certify.
When should I use Webconf Artifact Evaluation?
Webconf Artifact Evaluation fits situations like: packaging datasets; code for the Web Conference (WWW) Artifacts Available badge; for reviewer scrutiny; covering archival-repository choice.
How do I install Webconf Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-artifact-evaluation -a claude-code`. Or copy the skill folder (The-Web-Conference-Skills/skills/webconf-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/webconf-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Webconf Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-artifact-evaluation -a codex`. Or copy the skill folder (The-Web-Conference-Skills/skills/webconf-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/webconf-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Webconf 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 webconf-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/webconf-artifact-evaluation, .gemini/skills/webconf-artifact-evaluation, .github/skills/webconf-artifact-evaluation and .opencode/skills/webconf-artifact-evaluation in your project.
What does Webconf Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Webconf Artifact Evaluation is instructions for the agent only.
Does Webconf 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 Webconf 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 Webconf Artifact Evaluation use?
Webconf 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 Webconf 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 Webconf Artifact Evaluation?
Skills that share tags, products or a category with Webconf Artifact Evaluation: Datasets (Arize-ai/phoenix, 12k stars), Arize Evaluator (github/awesome-copilot, 40k stars), Ccs Artifact Evaluation (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Atc 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 Webconf 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.