Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when preparing the camera-ready of an accepted ACM/IEEE HRI paper — de-anonymizing systematically, completing ACM+IEEE dual-publication metadata (CCS concepts, ORCID…
Install Hri Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-camera-ready --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-camera-ready .claude/skills/hri-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-camera-ready into .claude/skills/hri-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-camera-ready", 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-camera-readyType 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-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-camera-ready --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-camera-ready .agents/skills/hri-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-camera-ready into .agents/skills/hri-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-camera-ready", 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-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-camera-ready --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-camera-ready .cursor/skills/hri-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-camera-ready into .cursor/skills/hri-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-camera-ready", 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-camera-ready--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-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hri-camera-ready --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-camera-ready .gemini/skills/hri-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-camera-ready into .gemini/skills/hri-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-camera-ready", 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-camera-readyInstalls 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-camera-ready -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-camera-ready .github/skills/hri-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-camera-ready into .github/skills/hri-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-camera-ready", 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-camera-ready -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-camera-ready --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-camera-ready .opencode/skills/hri-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HRI-Skills/skills/hri-camera-ready into .opencode/skills/hri-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hri-camera-ready", 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-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 636 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when preparing the camera-ready of an accepted ACM/IEEE HRI paper — de-anonymizing systematically, completing ACM+IEEE dual-publication metadata (CCS concepts, ORCID…
- Preparing the camera-ready of an accepted ACM/IEEE HRI paper — de-anonymizing systematically
- SKILL.md covers De-anonymize systematically, Deliver every rebuttal promise, ACM + IEEE metadata and rights and Finalize the video and…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Completing ACM+IEEE dual-publication metadata (CCS concepts
What it does
Hri Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
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. 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
- Preparing the camera-ready of an accepted ACM/IEEE HRI paper — de-anonymizing systematically
- Completing ACM+IEEE dual-publication metadata (CCS concepts
- Rights/eRights form)
- Delivering every rebuttal promise within the 8-page budget
Example prompts
- “/hri-camera-ready”
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 Camera Ready loads about 1.4k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 636 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). 636 words, ~1,390 tokens.
Download SKILL.mdSave it as
.claude/skills/hri-camera-ready/SKILL.md (or your agent's skills folder).- name
- hri-camera-ready
- description
- 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.
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, and the
production checks. Timing for the HRI 2026 cycle: camera-ready ~9-12 Jan 2026 (待核实 exact date;
see resources/official-source-map.md).
De-anonymize systematically
Double-blind is over; reverse every anonymization deliberately, and do not miss one:
- Author block — real names, affiliations, and emails in the
acmartauthor fields. - Self-citations — convert third-person "prior work [X]" back to natural phrasing where appropriate; ensure your own cited work is complete.
- Acknowledgments — restore funding sources, grant numbers, and thanks.
- Materials, code, and data archive — swap the anonymized review archive for the de-anonymized
public archive with a DOI (see
hri-artifact-evaluation); update the link in the paper. - Video — replace the review-only anonymized cut with the intended public version only if participants consented to public video; otherwise keep the de-identified cut and say so.
Then read the paper cold once more for any remaining "anonymized for review" placeholder.
Deliver every rebuttal promise
Reviewers accepted the paper partly on what you promised. Within the 8-page budget (incl. figures, excl. references):
- Make each promised change — the reframed claim, the added analysis or effect size, the foregrounded Wizard-of-Oz disclosure, the added citation, the clarified figure.
- If the edition assigned a shepherd / conditional acceptance, make the required changes and get the shepherd's sign-off before submitting (待核实 whether the cycle uses this).
- Do not quietly add new claims the reviewers never saw; camera-ready is for fulfilling promises and polishing, not re-scoping.
ACM + IEEE metadata and rights
HRI's dual publication means both publishers' metadata must be right:
- Rights / eRights form — complete the ACM rights process; the resulting rights block, DOI, and conference citation must appear on the first page exactly as issued. Because papers also go to IEEE Xplore, follow any IEEE copyright/PDF-eXpress step the author kit specifies (待核实 per cycle whether a separate IEEE step applies).
- CCS concepts — add the ACM Computing Classification System concepts for your paper.
- Author keywords — the index terms readers and search will use.
- ORCID — register/attach ORCIDs for authors as the metadata requires.
- Title/author metadata in the PDF must match the submission-system record exactly.
Show full SKILL.md (240 more words)Show less
Finalize the video and supplement
- Provide the final video figure at the required format/size (待核实 limits per cycle), now with correct attribution if public use was consented.
- Ensure supplementary materials and the artifact archive are the final, de-anonymized versions and
are referenced correctly from the paper (see
hri-supplementary).
Production checks
- Compile clean against the required
acmart(and any IEEE) specification; fix every LaTeX/font warning that affects the PDF. - Embed all fonts; verify figures are legible in grayscale and at print size.
- Check the page count — the body (incl. figures) must still fit 8 pages after adding names, acknowledgments, and rights block; these additions often push a tight paper over.
- Validate the PDF against any portal checker (e.g., PDF eXpress if IEEE requires it) and re-open the final upload cold.
- Verify links — the DOI archive and any URLs resolve and point to the public, permanent versions.
Common camera-ready failures
- Leftover anonymization (a "[anonymized]" acknowledgment, a review-only archive link).
- Over length after the author block, acknowledgments, and rights block are added.
- Missing CCS concepts / ORCID / keywords the metadata requires.
- Rights block or DOI absent or not matching the issued text.
- Video or archive still the anonymized review version, or an unconsented public video.
- A rebuttal promise silently dropped.
Reverify each cycle
- The exact camera-ready date and whether a separate IEEE (Xplore/PDF-eXpress) step applies.
- The required
acmartrevision, CCS/ORCID/keyword fields, and video format limits. - Whether shepherding/conditional acceptance applies to your paper.
Output format
[De-anonymization] authors/affiliations/acks/self-cites/archive/video all restored? leftover anon: <where>
[Rebuttal promises] each delivered within 8 pages? shepherd signed off (if any)?
[ACM+IEEE metadata] rights block + DOI · CCS concepts · keywords · ORCID · IEEE step (if req.)
[Video/supplement] final format · de-anonymized · consent-appropriate · referenced
[Production] clean compile · fonts embedded · page count ≤ 8 (body) · PDF checker passed
[Fix queue] <ordered, before the camera-ready deadline>© 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-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Hri Camera Ready 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 Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
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 Camera Ready
What does Hri Camera Ready do?
A skill your agent uses when preparing the camera-ready of an accepted ACM/IEEE HRI paper — de-anonymizing systematically, completing ACM+IEEE dual-publication metadata (CCS concepts, ORCID…. Hri Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Hri Camera Ready?
Hri Camera Ready fits situations like: preparing the camera-ready of an accepted ACM/IEEE HRI paper — de-anonymizing systematically; completing ACM+IEEE dual-publication metadata (CCS concepts; rights/eRights form); delivering every rebuttal promise within the 8-page budget.
How do I install Hri Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-camera-ready -a claude-code`. Or copy the skill folder (HRI-Skills/skills/hri-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/hri-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Hri Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hri-camera-ready -a codex`. Or copy the skill folder (HRI-Skills/skills/hri-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/hri-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Hri Camera Ready 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-camera-ready -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-camera-ready, .gemini/skills/hri-camera-ready, .github/skills/hri-camera-ready and .opencode/skills/hri-camera-ready in your project.
What does Hri Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Hri Camera Ready is instructions for the agent only.
Does Hri Camera Ready 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 Camera Ready 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 Camera Ready use?
Hri Camera Ready 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 Camera Ready use?
About 1.4k tokens (SKILL.md is roughly 5.6k 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 Camera Ready?
Skills that share tags, products or a category with Hri Camera Ready: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hri Camera Ready?
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.