Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when calibrating expectations for the Human Relations (HR) review process — the editorial scoping screen, double-anonymous developmental review, decision types, timelines…
Install Humrel Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill humrel-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills humrel-review-process --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/Human-Relations-Skills/skills/humrel-review-process .claude/skills/humrel-review-process && 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 "humrel-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Relations-Skills/skills/humrel-review-process into .claude/skills/humrel-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "humrel-review-process", 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/Human-Relations-Skills/skills/humrel-review-processType 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 humrel-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills humrel-review-process --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/Human-Relations-Skills/skills/humrel-review-process .agents/skills/humrel-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "humrel-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Relations-Skills/skills/humrel-review-process into .agents/skills/humrel-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "humrel-review-process", 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 humrel-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills humrel-review-process --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/Human-Relations-Skills/skills/humrel-review-process .cursor/skills/humrel-review-process && 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 "humrel-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Relations-Skills/skills/humrel-review-process into .cursor/skills/humrel-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "humrel-review-process", 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 Human-Relations-Skills/skills/humrel-review-process--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 humrel-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills humrel-review-process --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/Human-Relations-Skills/skills/humrel-review-process .gemini/skills/humrel-review-process && 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 "humrel-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Relations-Skills/skills/humrel-review-process into .gemini/skills/humrel-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "humrel-review-process", 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 humrel-review-processInstalls 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 humrel-review-process -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/Human-Relations-Skills/skills/humrel-review-process .github/skills/humrel-review-process && 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 "humrel-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Relations-Skills/skills/humrel-review-process into .github/skills/humrel-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "humrel-review-process", 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 humrel-review-process -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 humrel-review-process --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/Human-Relations-Skills/skills/humrel-review-process .opencode/skills/humrel-review-process && 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 "humrel-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Relations-Skills/skills/humrel-review-process into .opencode/skills/humrel-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "humrel-review-process", 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
humrel-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 522 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when calibrating expectations for the Human Relations (HR) review process — the editorial scoping screen, double-anonymous developmental review, decision types, timelines…
- Calibrating expectations for the Human Relations (HR) review process — the editorial scoping screen
- SKILL.md covers When to trigger, How HR review actually works, What HR decisions usually mean and Calibrating expectations, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Double-anonymous developmental review
What it does
Humrel Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when calibrating expectations for the Human Relations (HR) review process — the editorial scoping screen, double-anonymous developmental review, decision types, timelines, and when a sibling journal is the better route. Sets expectations; it does not draft the rebuttal (see humrel-rebuttal).
Its SKILL.md is about 1.2k 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
- Calibrating expectations for the Human Relations (HR) review process — the editorial scoping screen
- Double-anonymous developmental review
- When a sibling journal is the better route
Example prompts
- “/humrel-review-process”
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
Humrel Review Process loads about 1.2k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 522 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). 522 words, ~1,157 tokens.
Download SKILL.mdSave it as
.claude/skills/humrel-review-process/SKILL.md (or your agent's skills folder).- name
- humrel-review-process
- description
- Use when calibrating expectations for the Human Relations (HR) review process — the editorial scoping screen, double-anonymous developmental review, decision types, timelines, and when a sibling journal is the better route. Sets expectations; it does not draft the rebuttal (see humrel-rebuttal).
Review Process (humrel-review-process)
When to trigger
- A submission is in (or about to enter) the HR pipeline and you want to calibrate odds and timing
- A decision letter arrived and you must read it correctly (R&R vs. reject vs. resubmit-as-new)
- You are deciding whether to persist at HR or reroute to a sibling
- A coauthor expects fast quantitative-style turnaround and needs the developmental reality
How HR review actually works
HR runs a two-gate process. First, an editorial scoping screen: the handling editor assesses fit and whether the manuscript shows a plausible "unique and substantive theoretical contribution." HR is explicit that "suitable data are a necessary but not sufficient feature to get to full peer review" — so a competent empirical paper with no theoretical advance, or one that reads as a sibling-journal paper, can be returned before reviewers see it. Second, if it passes, it goes to double-anonymous peer review (typically multiple reviewers) and a developmental cycle. Reviews engage the argument seriously and tend to push on theory, contribution, and craft as much as on method.
What HR decisions usually mean
| Decision | Read it as | Your move |
|---|---|---|
| Desk return (scoping) | fit/contribution not legible, or sibling-shaped | reframe (humrel-contribution-framing / humrel-literature-positioning) or reroute |
| Reject after review | a fundamental theory/contribution gap, not just fixes | rethink the contribution before any resubmission elsewhere |
| Major revision (R&R) | the idea is promising; deepen theory + evidence | revise substantively, then humrel-rebuttal |
| Minor revision | contribution accepted; tighten and clarify | targeted edits; do not reopen the theory |
| Conditional accept | nearly there | comply precisely; preserve anonymized files |
An R&R at HR is an invitation to make the contribution deeper, not merely to add robustness — treat it as a developmental opportunity.
Calibrating expectations
- Theory-first bar. Acceptance turns on the theoretical contribution and HR fit, not on a clean estimate alone. Methodological polish without theoretical payoff underperforms.
- Timelines vary and are volatile; do not promise coauthors a specific turnaround (检索于 2026-06；以官网为准). Plan for a developmental, multi-round cycle rather than a fast accept/reject.
- Plural-methods reality: a strong ethnography or critical paper competes on equal footing with quantitative work — the binding question is always the contribution.
Show full SKILL.md (174 more words)Show less
When a sibling is the better route
If reviews repeatedly say the paper is empirically sound but theoretically thin, or that it belongs elsewhere, that is signal. Consider Work, Employment and Society (sociology of work), JMS (managerial relevance), AMJ (US empirical OB), Organization Studies (organization-theory internal), or Organization (critical) — see humrel-literature-positioning for the boundary logic. Rerouting is a strategy, not a defeat.
Checklist
- You can name which gate the paper is at (scoping screen vs. full review)
- The decision type is read correctly (R&R ≠ accept; desk return ≠ reject-after-review)
- An R&R plan deepens the contribution, not just adds robustness
- No specific timeline promised to coauthors (volatile)
- Anonymized files preserved for the next round
- If reviews say "wrong journal," a reroute target is identified honestly
Anti-patterns
- Treating the scoping screen as a formality and submitting a contribution-thin paper
- Reading "major revision" as "almost accepted" and revising superficially
- Promising coauthors a fixed turnaround
- Assuming quantitative work is favored (it is not — contribution decides)
- Resubmitting a rejected paper elsewhere without rethinking the theoretical gap reviewers named
Output format
【Journal】Human Relations
【Skill】humrel-review-process
【Gate】scoping screen / full double-anonymous review
【Decision read】desk return / reject / major R&R / minor / conditional
【Binding issue】theory/contribution / fit / method / craft
【Plan】deepen contribution + which humrel-* skills
【Reroute?】stay at HR / consider sibling (which + why)
【Next skill】humrel-rebuttal (if R&R)© 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 Human-Relations-Skills/skills/humrel-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Humrel Review Process 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 |
|---|---|---|---|---|---|---|
| Humrel Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | 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 Humrel Review Process
What does Humrel Review Process do?
A skill your agent uses when calibrating expectations for the Human Relations (HR) review process — the editorial scoping screen, double-anonymous developmental review, decision types, timelines…. Humrel Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when calibrating expectations for the Human Relations (HR) review process — the editorial scoping screen, double-anonymous developmental review, decision types, timelines, and when a sibling journal is the better route.
When should I use Humrel Review Process?
Humrel Review Process fits situations like: calibrating expectations for the Human Relations (HR) review process — the editorial scoping screen; double-anonymous developmental review; when a sibling journal is the better route.
How do I install Humrel Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill humrel-review-process -a claude-code`. Or copy the skill folder (Human-Relations-Skills/skills/humrel-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/humrel-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Humrel Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill humrel-review-process -a codex`. Or copy the skill folder (Human-Relations-Skills/skills/humrel-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/humrel-review-process in your project. Codex loads it when a task matches its description.
Can I use Humrel Review Process 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 humrel-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/humrel-review-process, .gemini/skills/humrel-review-process, .github/skills/humrel-review-process and .opencode/skills/humrel-review-process in your project.
What does Humrel Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Humrel Review Process is instructions for the agent only.
Does Humrel Review Process 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 Humrel Review Process 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 Humrel Review Process use?
Humrel Review Process 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 Humrel Review Process use?
About 1.2k tokens (SKILL.md is roughly 4.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 Humrel Review Process?
Skills that share tags, products or a category with Humrel Review Process: 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 Humrel Review Process?
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.