Agent skill · Code Review & Quality

humrel-review-process

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).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill humrel-review-process --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: Human-Relations-Skills/skills/humrel-review-process/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 |

What's inside
Steps it walks through
  1. When to trigger
  2. How HR review actually works
  3. What HR decisions usually mean
  4. Calibrating expectations
  5. When a sibling is the better route
  6. Checklist
  7. Anti-patterns
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the humrel-review-process skill do?

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).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill humrel-review-process --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.

Keep going