Agent skill · Code Review & Quality

chi-artifact-evaluation

Use when packaging the artifacts behind an ACM CHI paper — prototypes, study instruments, codebooks, datasets, analysis code — for anonymous review scrutiny and for post-acceptance archival release, in a venue with no formal artifact-evaluation committee doing it for you.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-artifact-evaluation --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: CHI-Skills/skills/chi-artifact-evaluation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# CHI Artifact Evaluation CHI's Papers track posted no separate artifact-evaluation committee or badge track for the cycles checked (2026, 2027; confirm each year — 待核实 as a standing item). That absence cuts both ways: nobody certifies your artifacts, and nobody but you ensures a skeptical reviewer can inspect them. At CHI the "artifact" is rarely just code — it is the prototype, the study instruments, the codebook, the dataset, and the video evidence of the system working. Package for two audiences with opposite needs: the anonymous reviewer with five minutes, and the future researcher with a real use for your materials. ## The CHI artifact inventory | Artifact | Reviewer's question | Archival value after acceptance | |---|---|---| | Prototype / system code | "Does the claimed interaction actually exist?" | Others extend or compare against it | | Video figure of real use | "Does it work outside the authors' hands?" | Permanent DL evidence (`chi-supplementary`) | | Study instruments (guides, questionnaires, tasks) | "Was the study what the paper says?" | Direct reuse in replications | | Codebook / analysis audit trail | "Do the themes live in the data?" | Methods teaching material

What's inside
Steps it walks through
  1. The CHI artifact inventory
  2. Reviewer-facing packaging (anonymous, five minutes)
  3. Post-acceptance release is a separate product
  4. Honest holes beat cosmetic completeness
  5. Timing inside the CHI year
  6. Output format
Commands it runs
Cold-simulate the reviewer on the exact ZIP you will upload
rm -rf /tmp/ae && unzip -q supplement.zip -d /tmp/ae && cd /tmp/ae
cat README* | head -30                      # does the claims map appear immediately?
grep -rEil 'author|university|(^|[^a-z])lab' --include='*.md' . | head
time bash run_minimal_demo.sh               # the five-minute budget is literal
More from Awesome-Journal-Skills
All skills →
About this skill
What does the chi-artifact-evaluation skill do?

Use when packaging the artifacts behind an ACM CHI paper — prototypes, study instruments, codebooks, datasets, analysis code — for anonymous review scrutiny and for post-acceptance archival release, in a venue with no formal artifact-evaluation committee doing it for you.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-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.

Keep going