uist-artifact-evaluation
Use when packaging the artifacts behind a UIST paper — code, toolkits, hardware design files, and datasets — first as anonymous review-time evidence that the system is real, then as a public release engineered for reuse, in a venue with no formal badge committee doing the checking for you.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-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.
# UIST Artifact Evaluation UIST has no artifact-evaluation committee or badge track (none was found for the 2026 cycle — 待核实 each year); the CFP-level instrument of proof is the video figure. That absence raises rather than lowers the packaging bar: your artifacts are judged twice, informally — at review time as *evidence the system exists as claimed*, and after publication as *infrastructure other builders adopt*. Nobody will certify either; both simply succeed or fail. ## What counts as the artifact, by paper type | Paper type | Review-time artifact | Reuse-time artifact | |---|---|---| | Interaction technique | Reference implementation + demo scene | Portable library with the technique isolated | | Toolkit / authoring system | Runnable toolkit + the example apps from the paper | Documented API, tutorials, package registry entry | | Hardware / fabrication | Design files, firmware, BOM, assembly photos | Fab-ready files + sourcing notes + calibration guide | | Sensing / recognition pipeline | Trained models + capture data + eval harness | Dataset with collection protocol + retraining scripts | | Human-AI / LLM system | Prompts, orchestration code, pinned model IDs, logged transcri
- What counts as the artifact, by paper type
- Review-time packaging: the five-minute skeptic
- Release-time packaging: engineering for strangers
- What the informal evaluators open first
- Toolkit papers: adoption is the long evaluation
- Hardware honesty
- Output format
What does the uist-artifact-evaluation skill do?
Use when packaging the artifacts behind a UIST paper — code, toolkits, hardware design files, and datasets — first as anonymous review-time evidence that the system is real, then as a public release engineered for reuse, in a venue with no formal badge committee doing the checking for you.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-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.