Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Jhr Review Process

ASecurity

Use to understand and plan around the Journal of Human Resources (JHR) editorial process — single-anonymous review, the fast desk-reject without outside review, the reconciliation requirement, and the optional review-recycling shortcut. Sets expectations; it does not draft the paper.

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agents

Works with

cli

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jhr-review-process --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jhr Review Process?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Jhr Review Process
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jhr-review-process/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jhr-review-process)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: jhr-review-process
description: Use to understand and plan around the Journal of Human Resources (JHR) editorial process — single-anonymous review, the fast desk-reject without outside review, the reconciliation requirement, and the optional review-recycling shortcut. Sets expectations; it does not draft the paper.
---

# Editorial Process (jhr-review-process)

## When to trigger

- Setting expectations on timelines and decision types at JHR
- Deciding whether to attach a prior journal's reports to speed review
- Understanding why a paper might be desk-rejected without referees
- Wanting to pre-empt the reconciliation / sensitivity demands referees apply

## How JHR review works (verified 2026-06-01)

- **Single-anonymous (single-blind):** "Referees are anonymous, but author names are not kept from reviewers." The process is run by the **Editor (Anna Aizer, Brown; Michael Lovenheim, Cornell, from 2026-07-01)**, coeditors, and associate editors, with volunteer expert reviewers.
- **Fast desk-reject WITHOUT outside review.** Papers a handling editor/coeditor judges unlikely to survive review are **released quickly without being sent to referees**, at the editor's discretion. The **$175 fee does not guarantee outside review** and is **not refunded** for out-of-scope (management/personnel) papers — so the desk screen is the first real hurdle.
- **Reconciliation requirement (distinctive):** manuscripts are judged partly on whether they **reconcile their results with prior published work** on the same topic. Authors **may be required to run comparative estimation** (re-estimate under the prior literature's spec/sample) and **present sensitivity tests**. Build this in before submitting, not after a referee demands it.
- **Review-recycling shortcut (optional):** authors may **submit a prior journal's decision letter and referee reports**; JHR may use them — and may **contact the prior journal's editor or referees** — to speed review. Useful when a paper was close at another journal and the reports are constructive.

## How to act on it

- Treat the **desk screen** as the highest-leverage gate: a legible policy-relevant question, a clearly stated identifying variation, and a one-paragraph reconciliation note give the handling editor a reason to send it out.
- If a prior submission generated strong-but-fixable reports, consider attaching them — but only if your revision genuinely answers them.
- Anticipate the reconciliation ask in `jhr-data-analysis`: have the comparative estimates and sensitivity tests ready.

## Checklist

- [ ] Question and identifying variation legible in the first two pages (desk screen)
- [ ] Reconciliation with prior published estimates addressed up front
- [ ] Comparative estimation and sensitivity tests prepared
- [ ] Decision made on whether to attach prior-journal reports
- [ ] Scope confirmed (not HR-management) so the fee is not wasted

## Anti-patterns

- Assuming the fee buys outside review — it does not
- Ignoring prior published estimates that contradict yours
- Attaching old referee reports the revision does not actually address
- Burying the identifying variation past the desk-reading window

## Output format

```
【Decision risk】desk-reject likelihood / why
【Reconciliation】prior estimates addressed? [Y/N]
【Sensitivity】comparative/robustness ready? [Y/N]
【Recycling】attach prior reports? [Y/N + reason]
【Next step】jhr-submission or jhr-rebuttal
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →