webconf-artifact-evaluation
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-artifact-evaluation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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* c
- What the badge checks vs. what readers need
- Web-data artifacts are legally different
- Minimum viable package
- During review vs. after acceptance
- Vignette: the crawl that got a takedown notice
- Badge application dry run
- Honest labeling
- Output format
What does the webconf-artifact-evaluation skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-artifact-evaluation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.