A skill your agent uses 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…

MITAuto-check passedAgent Workflows

Install Hri Topic Selection

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-topic-selection -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-topic-selection --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/HRI-Skills/skills/hri-topic-selection .claude/skills/hri-topic-selection && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
hri-topic-selection
GitHub stars
1.2k
Token cost
~1.6k tokens
SKILL.md length
794 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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…

  • Works in 2 steps: Robot-embodiment test. Is there a robot… → Human-in-the-loop test. Is a person…
  • Deciding whether a human-robot-interaction project belongs at the ACM/IEEE HRI conference versus CHI
  • SKILL.md covers The two gating tests, Route among the siblings, Then pick the track (this is… and The re-label test (does it…, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Hri Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Human-in-the-loop approvals. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. | 覆盖主流期刊的… The licence is MIT.

When your agent uses it

  • Deciding whether a human-robot-interaction project belongs at the ACM/IEEE HRI conference versus CHI
  • The THRI/JHRI journals
  • Then which of HRIs five full-paper tracks (User Studies
  • Theory and Methods

Example prompts

  • “/hri-topic-selection”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Robot-embodiment test. Is there a robot — a physical or virtual embodied agent — that is
  2. Human-in-the-loop test. Is a person interacting with the robot, and is the paper's claim

What it can do on your machine

Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Hri Topic Selection loads about 1.6k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 794 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~98
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 794 words, ~1,584 tokens.

Download SKILL.mdSave it as .claude/skills/hri-topic-selection/SKILL.md (or your agent's skills folder).
name
hri-topic-selection
description
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.

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 a human (benchmarks, trajectories, success rates), it belongs at ICRA/IROS/CoRL, even if the long-term motivation is human-facing.

Pass both and you are plausibly at HRI. Fail the first → CHI (or a design/AI venue). Fail the second → a robotics/learning venue. Pass both but the human is incidental → reconsider whether the human study is real or decorative.

Route among the siblings

If the core contribution is...PreferWhy not HRI
Interaction with an embodied robot, evaluated with peopleHRI—
A general HCI/UI interaction with no robot embodimentCHINo robot; HRI requires embodiment
Robot autonomy/control/perception/learning, no human studyICRA / IROS / CoRLNo human-in-the-loop; HRI wants the interaction
Robot-and-human communication with an engineering-comms framingRO-MANRO-MAN overlaps; HRI is more selective and study-centric — a judgment call, decide by community fit
Human-agent interaction where the agent is not a robotHAIEmbodiment/robot focus is weaker
A mature, extended study or synthesis better as an archival articleTHRI (journal)HRI is an 8-page conference paper, not a journal article
Early-stage result or new idea, not yet a full studyHRI Late-Breaking ReportsFull papers need a complete, defensible study
Bold, provocative, or unconventional work / methodsHRI alt.HRIThe main track expects standard rigor; alt.HRI invites the unorthodox

The RO-MAN vs HRI and CHI vs HRI calls are the frequent ones. Decide RO-MAN/HRI by selectivity and evidence culture (HRI leans harder on study design and effect sizes); decide CHI/HRI by whether the robot's embodiment is doing real work in the interaction.

Show full SKILL.md (366 more words)Show less

Then pick the track (this is HRI-specific)

Full papers enter exactly one of five tracks, and are reviewed by the subcommittee matched to that contribution type. Choose by what your primary contribution is, not by your topic:

  • User Studies — new knowledge about human-robot interaction from a study involving people. The default home for empirical/behavioral work. Reproducibility studies also go here. Typically the largest track (and may be split into multiple subcommittees).
  • Technical — the primary contribution is an algorithm, model, or method, best judged by component-level testing rather than a full system evaluation (e.g., a perception or behavior- generation method for interaction).
  • Design — the contribution is a designed interaction, artifact, or interface for HRI, with design insight demonstrated (often with people, but the contribution is the design).
  • Theory and Methods — the contribution advances the conceptual foundations of HRI or the methods by which we do HRI research (frameworks, measures, methodology).
  • Systems — the contribution is an integrated robotic system achieving new interactive capability, evaluated at the system level.

Mismatch is costly: a design contribution shoved into User Studies will be marked down for a weak study it never claimed to be. If two tracks fit, pick the one matching the contribution you most want judged, and make that contribution unmistakable on the first page.

The re-label test (does it survive as an HRI paper?)

Ask: if I removed the robot, would the contribution survive? If yes, it is probably a CHI/ML/ psychology paper wearing a robot costume. And: if I removed the human study, would the contribution survive? If yes, it is probably an ICRA/IROS systems paper. An HRI paper is one where both the robot and the human interaction are load-bearing.

Calendar as a routing input

HRI runs an annual cycle with an early-fall full-paper deadline. For the 2026 cycle: abstract 22 Sep 2025, paper 30 Sep 2025 (AoE); alt.HRI 17 Oct 2025; LBR / video / Student Design 8 Dec 2025; conference March. If the study will not be complete and defensible by the full-paper deadline, the honest routes are LBR (early-stage) now and a full paper next cycle, or a different venue — not a thin full-paper submission that a User Studies subcommittee will see through.

Output format

text
[Venue decision] HRI / CHI / ICRA-IROS-CoRL / RO-MAN / HAI / THRI / other
[Both gating tests] robot embodiment: yes/no · human-in-the-loop: yes/no
[Re-label test] survives without robot? without human study? (both should be "no")
[Track] User Studies / Technical / Design / Theory and Methods / Systems — why
[If not HRI] recommended venue + reason
[Calendar fit] complete by the full-paper deadline? else LBR/alt.HRI/next cycle

© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in HRI-Skills/skills/hri-topic-selection of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Hri Topic Selection next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Hri Topic Selection compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Hri Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.6kAutomated safety check: PassMIT
Show Me Your Work Decision Logcursor/plugins10k8 repos~1.6kAutomated safety check: PassNone
Darwin Skill Optimizeralchaincyf/darwin-skill6.2k1 repos~4.7kAutomated safety check: PassMIT
Loop Constraints Enforcercobusgreyling/loop-engineering11k1 repos~475Automated safety check: NotesMIT
Ask User QuestionMemTensor/MemOS12k—~1kAutomated safety check: PassApache-2.0
PUA High-Agency Governancetanweai/pua20k—~502Automated safety check: PassMIT

Similar skills

  • Official

    Keeps a TSV decision log for long or unattended agent runs, one row per decision with what, why, evidence and result, so a reviewer can check the work later.

    10k GitHub starsUsed in 8 repos~1.6k tokens
    Agent WorkflowsAuto-check passed
  • Darwin Skill Optimizer

    alchaincyf/darwin-skill

    Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.

    6.2k GitHub starsUsed in 1 repo~4.7k tokens
    Agent WorkflowsAuto-check passed
  • Loop Constraints Enforcer

    cobusgreyling/loop-engineering

    Loads a project's loop-constraints.md before any other action and blocks pushes, edits or merges that violate the rules it defines.

    11k GitHub starsUsed in 1 repo~475 tokens
    Agent WorkflowsAuto-check: notes
  • Ask User Question

    MemTensor/MemOS

    Shows a question as a modal in the interface to clarify a task, collect a preference or get approval, since the user cannot see terminal output.

    12k GitHub stars~1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Pushes an agent to keep verifying and changing approach after repeated failures, using a diagnosis line, evidence-based completion and confirmation before risky edits.

    20k GitHub stars~502 tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Agentmemory Forget

    rohitg00/agentmemory

    Deletes chosen memories from agentmemory only after showing the matches and getting an explicit yes, for privacy requests and cleanup of outdated notes.

    29k GitHub stars~612 tokensUpdated today
    Agent WorkflowsAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo
  • Aaag Data Analysis

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…

    1.2k GitHub stars~1.3k tokensUpdated 12 days ago
    Auto-check passed
  • Aaag Literature Positioning

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…

    1.2k GitHub stars~1.3k tokensUpdated 12 days ago
    Auto-check passed
  • Aaag Rebuttal

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…

    1.2k GitHub stars~1.4k tokensUpdated 12 days ago
    Auto-check passed
  • Aaag Research Design

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…

    1.2k GitHub stars~1.4k tokensUpdated 12 days ago
    Auto-check passed
  • Aaag Review Process

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…

    1.2k GitHub stars~1.3k tokensUpdated 12 days ago
    Auto-check passed
  • Aaag Submission

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…

    1.2k GitHub stars~1.6k tokensUpdated 12 days ago
    Auto-check passed

Categories

Questions about Hri Topic Selection

What does Hri Topic Selection do?

A skill your agent uses 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…. Hri Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.

When should I use Hri Topic Selection?

Hri Topic Selection fits situations like: deciding whether a human-robot-interaction project belongs at the ACM/IEEE HRI conference versus CHI; the THRI/JHRI journals; then which of HRIs five full-paper tracks (User Studies; theory and Methods.

How do I install Hri Topic Selection in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-topic-selection -a claude-code`. Or copy the skill folder (HRI-Skills/skills/hri-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/hri-topic-selection in your project. Claude Code loads it when a task matches its description.

How do I install Hri Topic Selection in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-topic-selection -a codex`. Or copy the skill folder (HRI-Skills/skills/hri-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/hri-topic-selection in your project. Codex loads it when a task matches its description.

Can I use Hri Topic Selection in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-topic-selection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hri-topic-selection, .gemini/skills/hri-topic-selection, .github/skills/hri-topic-selection and .opencode/skills/hri-topic-selection in your project.

What does Hri Topic Selection need to run?

SKILL.md names no scripts, command-line tools or credentials: Hri Topic Selection is instructions for the agent only.

Does Hri Topic Selection access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Hri Topic Selection safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Hri Topic Selection use?

Hri Topic Selection is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Hri Topic Selection use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Hri Topic Selection?

Skills that share tags, products or a category with Hri Topic Selection: Show Me Your Work Decision Log (cursor/plugins, 10k stars), Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars), Loop Constraints Enforcer (cobusgreyling/loop-engineering, 11k stars) and Ask User Question (MemTensor/MemOS, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hri Topic Selection?

brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.

Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.