Show Me Your Work Decision Log
cursor/plugins
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.
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…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-topic-selection --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "hri-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-topic-selection into .claude/skills/hri-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-topic-selection", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-topic-selectionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-topic-selection --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/HRI-Skills/skills/hri-topic-selection .agents/skills/hri-topic-selection && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hri-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-topic-selection into .agents/skills/hri-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-topic-selection", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-topic-selection --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/HRI-Skills/skills/hri-topic-selection .cursor/skills/hri-topic-selection && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hri-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-topic-selection into .cursor/skills/hri-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-topic-selection", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path HRI-Skills/skills/hri-topic-selection--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-topic-selection --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/HRI-Skills/skills/hri-topic-selection .gemini/skills/hri-topic-selection && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hri-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-topic-selection into .gemini/skills/hri-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-topic-selection", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-topic-selectionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-topic-selection -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/HRI-Skills/skills/hri-topic-selection .github/skills/hri-topic-selection && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hri-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-topic-selection into .github/skills/hri-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-topic-selection", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-topic-selection -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-topic-selection --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/HRI-Skills/skills/hri-topic-selection .opencode/skills/hri-topic-selection && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hri-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-topic-selection into .opencode/skills/hri-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-topic-selection", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
hri-topic-selectionA 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.
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.
2 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 794 words, ~1,584 tokens.
.claude/skills/hri-topic-selection/SKILL.md (or your agent's skills folder).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.
Apply both. HRI wants a person and a robot interacting.
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.
| If the core contribution is... | Prefer | Why not HRI |
|---|---|---|
| Interaction with an embodied robot, evaluated with people | HRI | — |
| A general HCI/UI interaction with no robot embodiment | CHI | No robot; HRI requires embodiment |
| Robot autonomy/control/perception/learning, no human study | ICRA / IROS / CoRL | No human-in-the-loop; HRI wants the interaction |
| Robot-and-human communication with an engineering-comms framing | RO-MAN | RO-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 robot | HAI | Embodiment/robot focus is weaker |
| A mature, extended study or synthesis better as an archival article | THRI (journal) | HRI is an 8-page conference paper, not a journal article |
| Early-stage result or new idea, not yet a full study | HRI Late-Breaking Reports | Full papers need a complete, defensible study |
| Bold, provocative, or unconventional work / methods | HRI alt.HRI | The 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.
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:
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.
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.
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.
[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
Just SKILL.md in HRI-Skills/skills/hri-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hri Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Show Me Your Work Decision Logcursor/plugins | 10k | 8 repos | ~1.6k | Automated safety check: Pass | None | |
| Darwin Skill Optimizeralchaincyf/darwin-skill | 6.2k | 1 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Loop Constraints Enforcercobusgreyling/loop-engineering | 11k | 1 repos | ~475 | Automated safety check: Notes | MIT | |
| Ask User QuestionMemTensor/MemOS | 12k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| PUA High-Agency Governancetanweai/pua | 20k | — | ~502 | Automated safety check: Pass | MIT |
cursor/plugins
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.
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.
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.
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.
tanweai/pua
Pushes an agent to keep verifying and changing approach after repeated failures, using a diagnosis line, evidence-based completion and confirmation before risky edits.
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.
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…
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…
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…
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…
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…
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…
Categories
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.
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.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Hri Topic Selection is instructions for the agent only.
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.
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.
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.
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.
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.
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.