Ieee Paper Reader
CloudWave818/ieee-skills
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.
A skill your agent uses when writing or auditing the related-work and positioning of an ACM/IEEE HRI full paper — covering HRI's crossing literatures (robotics, HCI, psychology, design), writing a…
Install Hri Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-related-work --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-related-work .claude/skills/hri-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-related-work into .claude/skills/hri-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-related-work", 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-related-workType 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-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-related-work --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-related-work .agents/skills/hri-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-related-work into .agents/skills/hri-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-related-work", 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-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-related-work --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-related-work .cursor/skills/hri-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-related-work into .cursor/skills/hri-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-related-work", 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-related-work--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-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-related-work --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-related-work .gemini/skills/hri-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-related-work into .gemini/skills/hri-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-related-work", 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-related-workInstalls 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-related-work -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-related-work .github/skills/hri-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-related-work into .github/skills/hri-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-related-work", 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-related-work -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-related-work --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-related-work .opencode/skills/hri-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-related-work into .opencode/skills/hri-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-related-work", 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.
Facts
- Skill name
hri-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 699 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing or auditing the related-work and positioning of an ACM/IEEE HRI full paper — covering HRI's crossing literatures (robotics, HCI, psychology, design), writing a…
- Auditing the related-work and positioning of an ACM/IEEE HRI full paper — covering HRIs crossing literatures (robotics
- SKILL.md covers Cover the crossing literatures, Delta-first positioning, Credit theory correctly (the… and Double-blind self-citation, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Writing a delta-first argument that credits each community
What it does
Hri Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing or auditing the related-work and positioning of an ACM/IEEE HRI full paper — covering HRI's crossing literatures (robotics, HCI, psychology, design), writing a delta-first argument that credits each community, and keeping self-citation compatible with double-blind review.
Its SKILL.md is about 1.4k 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 Research & Science, covering Literature review, Positioning and messaging and Citation management. 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
- Auditing the related-work and positioning of an ACM/IEEE HRI full paper — covering HRIs crossing literatures (robotics
- Writing a delta-first argument that credits each community
- Keeping self-citation compatible with double-blind review
Example prompts
- “/hri-related-work”
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 Related Work loads about 1.4k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 699 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.
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). 699 words, ~1,432 tokens.
Download SKILL.mdSave it as
.claude/skills/hri-related-work/SKILL.md (or your agent's skills folder).- name
- hri-related-work
- description
- Use when writing or auditing the related-work and positioning of an ACM/IEEE HRI full paper — covering HRI's crossing literatures (robotics, HCI, psychology, design), writing a delta-first argument that credits each community, and keeping self-citation compatible with double-blind review.
HRI Related Work
An HRI related-work section has a harder job than most: it must place the paper in several literatures at once — robotics, HCI, psychology/cognitive science, and design — because HRI reviewers are drawn from all of them, and each expects to see their field cited correctly. A section that reads as an ICRA lit review to a psychologist (or vice versa) signals the authors do not understand the interdisciplinary conversation they are joining. This skill covers coverage, positioning, and double-blind hygiene.
Cover the crossing literatures
Map your paper to the lanes it actually touches, and cite each in that community's terms:
- HRI conference and journal core — the directly adjacent HRI work (prior HRI/THRI/JHRI studies on your construct or interaction). This is where reviewers look first; missing the nearest HRI neighbor is the classic fatal gap.
- Robotics — the technical substrate (perception, control, behavior generation, autonomy) your robot relies on, if the contribution is technical/systems.
- HCI — interaction design, evaluation methods, and any general-HCI phenomenon your interaction instantiates.
- Psychology / cognitive & social science — the theory behind your constructs (trust, mind perception, social presence, warmth/competence, persuasion), cited to its origin, not only to its HRI re-uses.
- Design — if yours is a design contribution, the design methods and precedents (probes, research-through-design, participatory design) it builds on.
You do not need every lane — you need the lanes your contribution genuinely engages, covered well enough that a reviewer from each field trusts you.
Delta-first positioning
HRI reviewers reward a crisp statement of what is new:
- For each closest prior work, state in one sentence what they did and what you do differently — a different robot, a different measured outcome (behavior vs. attitude), a different population, a causal manipulation where they had correlation, a design where they had a study.
- Prefer a short, sharp delta over an exhaustive survey. Eight pages do not allow a textbook review; they allow a targeted argument for why your contribution is needed.
- Avoid the "no one has studied X with a robot" claim unless it is true and load-bearing — novelty of combination is fine, but say why the combination matters, not merely that it is unclaimed.
Credit theory correctly (the interdisciplinary trap)
The most common HRI positioning error is citing a psychological or design construct only through its HRI re-uses:
- If you measure trust, anthropomorphism, social presence, or persuasion, cite the originating theory and the validated instrument, not just the last three HRI papers that used the word. A psychology reviewer notices immediately.
- If you borrow a method (thematic analysis, mixed methods, a specific experimental paradigm), cite its methodological source so a methods reviewer trusts you are using it correctly.
- Do not rename an existing construct; align your terminology with the field that owns it.
Show full SKILL.md (246 more words)Show less
Double-blind self-citation
HRI full-paper review is double-blind; positioning must not de-anonymize you:
- Cite your own prior work in the third person ("Prior work [X] found...", never "our previous work [X]"), and keep those citations in the normal reference list.
- If a new submission builds directly on your unpublished or under-review work, describe the relationship without identifying the authors; do not attach an identifying tech report.
- Do not remove necessary self-citations to avoid detection — a missing obvious reference is itself a signal. Anonymize the phrasing, not the scholarship.
- Watch acknowledgments, grant numbers, and platform/lab names elsewhere in the paper that a
related-work reviewer might connect to an author (see
hri-submission).
Placement and length
- A related-work section works when the paper needs to survey a landscape; inline positioning (delta stated where each idea is introduced) often serves better under the 8-page budget. Choose one primary strategy; do not both survey at length and re-argue inline.
- Keep related work proportional — it exists to justify the contribution, not to prove reading. If it crowds out the method or results, cut it.
Anti-patterns HRI reviewers flag
- Single-field tunnel vision — a robotics-only or psychology-only reference list for a paper that claims to be interdisciplinary.
- Construct laundering — using a theoretical term (e.g., "trust") while citing only its HRI buzzword uses, not its theoretical source or validated measure.
- Survey-as-substitute — a long neutral catalogue with no delta, leaving reviewers to guess the contribution.
- First-person self-citation — an anonymity break hiding in the related work.
Output format
[Literature lanes covered] HRI-core / robotics / HCI / psychology / design — which apply, which cited well
[Nearest HRI neighbor] identified and delta stated? yes/no
[Delta-first] each key prior work paired with an explicit difference? yes/no
[Theory credited] constructs/methods cited to origin + validated instrument? yes/no
[Double-blind] self-citations third-person; no identifying acknowledgments/labs? yes/no
[Fix queue] <ordered edits>© 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-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Hri Related Work 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 Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Ieee Paper ReaderCloudWave818/ieee-skills | 359 | — | ~591 | Automated safety check: Pass | MIT | |
| Gec Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~855 | Automated safety check: Pass | None | |
| Jpe Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
Gec Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when positioning a Global Environmental Change (GEC) manuscript against the relevant literatures.
Jpe Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when writing or repairing the introduction and related-work framing for a Journal of Political Economy (JPE) manuscript — situating the contribution in the economics…
Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag 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…
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…
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…
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…
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…
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…
Related
Categories
Questions about Hri Related Work
What does Hri Related Work do?
A skill your agent uses when writing or auditing the related-work and positioning of an ACM/IEEE HRI full paper — covering HRI's crossing literatures (robotics, HCI, psychology, design), writing a…. Hri Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing or auditing the related-work and positioning of an ACM/IEEE HRI full paper — covering HRI's crossing literatures (robotics, HCI, psychology, design), writing a delta-first argument that credits each community, and keeping self-citation compatible with double-blind review.
When should I use Hri Related Work?
Hri Related Work fits situations like: auditing the related-work and positioning of an ACM/IEEE HRI full paper — covering HRIs crossing literatures (robotics; writing a delta-first argument that credits each community; keeping self-citation compatible with double-blind review.
How do I install Hri Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-related-work -a claude-code`. Or copy the skill folder (HRI-Skills/skills/hri-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/hri-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Hri Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-related-work -a codex`. Or copy the skill folder (HRI-Skills/skills/hri-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/hri-related-work in your project. Codex loads it when a task matches its description.
Can I use Hri Related Work 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-related-work -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-related-work, .gemini/skills/hri-related-work, .github/skills/hri-related-work and .opencode/skills/hri-related-work in your project.
What does Hri Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Hri Related Work is instructions for the agent only.
Does Hri Related Work 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 Related Work 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 Related Work use?
Hri Related Work 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 Related Work use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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 Related Work?
Skills that share tags, products or a category with Hri Related Work: Ieee Paper Reader (CloudWave818/ieee-skills, 359 stars), Gec Literature Positioning (franklee16/academic-research-skills, 223 stars), Jpe Literature Positioning (franklee16/academic-research-skills, 223 stars) and Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hri Related Work?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.