hri-camera-ready
Use when preparing the camera-ready of an accepted ACM/IEEE HRI paper — de-anonymizing systematically, completing ACM+IEEE dual-publication metadata (CCS concepts, ORCID, rights/eRights form), delivering every rebuttal promise within the 8-page budget, finalizing the video and de-anonymized archive, and passing production checks.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-camera-ready --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 Camera-Ready Acceptance is not the finish line — the camera-ready is where a double-blind paper becomes a public, dual-published ACM+IEEE record, and where every promise you made in the rebuttal comes due. HRI papers appear in **both the ACM Digital Library and IEEE Xplore**, so the metadata and rights work is real. This skill runs the de-anonymization, the ACM metadata, the promised changes
What does the hri-camera-ready skill do?
Use when preparing the camera-ready of an accepted ACM/IEEE HRI paper — de-anonymizing systematically, completing ACM+IEEE dual-publication metadata (CCS concepts, ORCID, rights/eRights form), delivering every rebuttal promise within the 8-page budget, finalizing the video and de-anonymized archive, and passing production checks.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-camera-ready --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.