wsdm-artifact-evaluation
Use when packaging code, data, and models as evidence for a WSDM paper - anonymous repositories cited in the PDF, the proprietary-log dilemma of web-scale research, public-benchmark substitution tiers, WSDM Cup datasets, and what credible artifact release looks like at a venue without a formal badge process.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wsdm-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.
# WSDM Artifact Evaluation Package artifacts for a venue where they are persuasion, not process. The pack found no formal artifact-evaluation track or badge system for current WSDM editions (待核实 each cycle) - the CFP-level expectation is the community norm of "practical yet principled": reviewers reward submissions whose claims a skeptic could re-derive. That means the artifact's job is to be *inspectable during review* and *usable after publication*, with no committee to certify it. ## The reviewer-facing artifact Because appendices count against WSDM's page budget and there is no rebuttal in which to hand over materials later, the anonymous repository referenced in the PDF is the only expansion space you get. Build it to be skimmed in ten minutes: ```text anon-artifact/ ├── README.md # 1 screen: claim -> script -> expected output table ├── LICENSE # anonymized placeholder license during review ├── env/ # lockfile or container spec, exact versions ├── data/ │ ├── public/ # download scripts for public benchmarks │ └── PROPRIETARY.md # honest statement of what cannot be shared and why ├── src/ # training/ranking/mining code, no company paths ├── configs/ # one config per reported ta
- The reviewer-facing artifact
- The proprietary-log dilemma
- Public substitutes worth knowing
- Model and prompt artifacts
- Credibility signals at a badge-free venue
- Post-acceptance conversion
- Output format
What does the wsdm-artifact-evaluation skill do?
Use when packaging code, data, and models as evidence for a WSDM paper - anonymous repositories cited in the PDF, the proprietary-log dilemma of web-scale research, public-benchmark substitution tiers, WSDM Cup datasets, and what credible artifact release looks like at a venue without a formal badge process.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wsdm-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.