Agent 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.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-topic-selection --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: CHI-Skills/skills/chi-topic-selection/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 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 interface differently, a policy team understands a user population differently. If no answer survives scrutiny, the project is an engineering result wearing an HCI costume, and reviewers will say exactly that. A system with no study can still be CHI-worthy — but only when the system itself embodies a claim about interaction that others can build on. ## Name the contribution type before the venue CHI's own guidance enumerates the contribution types the c

What's inside
Steps it walks through
  1. Start with the human, not the system
  2. Name the contribution type before the venue
  3. The subcommittee decision
  4. When CHI is the wrong room
  5. Anti-signals before you commit a year
  6. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the chi-topic-selection skill do?

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.

How do I install it?

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