Individual skill
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.
UIST-Skills/skills/uist-artifact-evaluation/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,405
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- design Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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 |