hri-artifact-evaluation
Use when packaging the artifacts of an accepted ACM/IEEE HRI paper — code, robot behaviors, de-identified data, and study materials — for openness and any ACM badges the edition offers, while being honest about the limits of reproducing an embodied human-subjects study.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-artifact-evaluation --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 Artifact Evaluation HRI's artifact and reproducibility culture is **less formalized than software-engineering venues'**: there is not a long-standing, uniformly enforced ACM artifact-badge track at every HRI edition, and whether a given year runs a formal reproducibility/artifact evaluation is **待核实 per cycle**. So treat artifact work at HRI as a **credibility and openness** move first, and follow a formal badge process only if this edition offers one. Either way, the artifact of an HRI paper is unusual: it is the **study**, not a runnable system that reproduces a number. This skill packages it honestly. It builds on `hri-reproducibility` and the shared kit in [`../../resources/code/README.md`](../../resources/code/README.md). ## First: does this edition run a formal evaluation? - Check the current call for a **reproducibility/artifact track**, its badges, and its own deadline (**待核实**). If it exists, follow its instructions exactly. - If ACM badges are offered, they follow the ACM scheme (Artifacts Available / Evaluated - Functional / Reusable / Results Reproduced). Map your package to whichever the edition supports. - If no formal track runs, **still** release an open, well
- First: does this edition run a formal evaluation?
- What an HRI artifact actually contains
- Make it reusable, within honest limits
- Human-subjects constraints on the artifact
- Camera-ready badge mechanics (if applicable)
- Anti-patterns
- Output format
What does the hri-artifact-evaluation skill do?
Use when packaging the artifacts of an accepted ACM/IEEE HRI paper — code, robot behaviors, de-identified data, and study materials — for openness and any ACM badges the edition offers, while being honest about the limits of reproducing an embodied human-subjects study.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-artifact-evaluation --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.