hri-topic-selection
Use when deciding whether a human-robot-interaction project belongs at the ACM/IEEE HRI conference versus CHI, ICRA/IROS, RO-MAN, CoRL, HAI, or the THRI/JHRI journals, and then which of HRI's five full-paper tracks (User Studies, Technical, Design, Theory and Methods, Systems) it should enter, using the robot-embodiment and human-in-the-loop tests and the HRI calendar.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-topic-selection --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.
# HRI Topic Selection Two decisions precede everything else: **is this an HRI paper at all**, and **which of the five tracks** does it enter. HRI is the flagship *interdisciplinary* venue for human-robot interaction — it uniquely rewards work that sits *between* robotics, HCI, psychology, and design. Getting the venue and track right is the highest-leverage move an author makes, because HRI judges each paper by the contribution type of its chosen track. Facts below were read from the HRI 2026/2027 calls on 2026-07-09 (see `resources/official-source-map.md`); reopen the live call before deciding. ## The two gating tests Apply both. HRI wants **a person and a robot interacting**. 1. **Robot-embodiment test.** Is there a robot — a physical or virtual *embodied* agent — that is central to the study? If the "robot" is really a chatbot, a screen widget, or a disembodied voice assistant with no embodiment, the interaction lessons usually belong at **CHI** or a dialogue venue, not HRI. 2. **Human-in-the-loop test.** Is a *person* interacting with the robot, and is the paper's claim about that interaction? If the contribution is autonomy, control, perception, or learning evaluated **without
- The two gating tests
- Route among the siblings
- Then pick the track (this is HRI-specific)
- The re-label test (does it survive as an HRI paper?)
- Calendar as a routing input
- Output format
What does the hri-topic-selection skill do?
Use when deciding whether a human-robot-interaction project belongs at the ACM/IEEE HRI conference versus CHI, ICRA/IROS, RO-MAN, CoRL, HAI, or the THRI/JHRI journals, and then which of HRI's five full-paper tracks (User Studies, Technical, Design, Theory and Methods, Systems) it should enter, using the robot-embodiment and human-in-the-loop tests and the HRI calendar.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-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.