Individual skill
chi-topic-selection
Use when deciding whether a project belongs at ACM CHI, which of CHI's contribution types it makes, and which reviewing subcommittee should judge it — or whether the work is better routed to UIST, CSCW, DIS, IUI, ASSETS, IMWUT, or TOCHI before any drafting starts.
CHI-Skills/skills/chi-topic-selection/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
- Yes
- 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
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,103 bytes
Read excerpt
# CHI Topic Selection
CHI accepts almost every topic that touches people and computing, so "is this in
scope?" is rarely the real question. The decisions that actually shape the outcome
are: *which contribution type is this paper*, and *which subcommittee should read it*.
Both are declared at submission time in PCS, and both are strategy, not paperwork —
CHI 2026 rejected roughly three quarters of 6,730 completed submissions, and a large
share of early rejections trace to papers pitched at the wrong reviewer community
inside CHI itself.
## Start with the human, not the system
Ask: **who changes what they do because this paper exists?** A designer picks a
different pattern, a researcher runs a study differently, a developer builds an