Agent skill · Code Review & Quality

jpube-review-process

Use when you need to understand or plan around the Journal of Public Economics (JPubE / JPubEc) editorial process — single anonymized review with a minimum of two reviewers, the Editorial Manager workflow, the Hendren–Kopczuk editorial leadership, SSRN preprint option, and the one-appeal policy. Explains the process; for the final file check use jpube-submission.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-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: 6 KB
Bundled scripts: none
Path: Journal-of-Public-Economics-Skills/skills/jpube-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 (jpube-review-process) ## When to trigger - You want to know what happens after you press submit at JPubE - You are deciding whether to post an SSRN preprint at submission - You need to plan timelines and expectations around the review model - A decision arrived and you are weighing whether to appeal ## How JPubE review works (verified facts) - **Single anonymized review.** Reviewers' identities are hidden from authors, but **authors' identities are known to reviewers and editors**. This is *not* double-anonymized — do not strip your name from the manuscript expecting blind review; write knowing referees see who you are. (Contrast: some venues use double-anonymized review.) - **Minimum of two reviewers.** Suitable submissions are typically sent to at least two reviewers; expect substantive, specialist public-finance reports. - **Editorial leadership.** The current ScienceDirect masthead lists **Editors Nathaniel Hendren (MIT)** and **Wojciech Kopczuk (Columbia)**, supported by co-editors and advisory editors. A handling editor manages your manuscript and synthesizes the reports into the decision. - **Editorial Manager workflow.** Submission and all correspondence r

What's inside
Steps it walks through
  1. When to trigger
  2. How JPubE review works (verified facts)
  3. Appeals (verified)
  4. Planning implications
  5. Checklist
  6. Anti-patterns
  7. Decision pathways after submit
  8. Worked vignette: deciding whether to appeal (illustrative)
  9. Calibration anchors
  10. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jpube-review-process skill do?

Use when you need to understand or plan around the Journal of Public Economics (JPubE / JPubEc) editorial process — single anonymized review with a minimum of two reviewers, the Editorial Manager workflow, the Hendren–Kopczuk editorial leadership, SSRN preprint option, and the one-appeal policy. Explains the process; for the final file check use jpube-submission.

How do I install it?

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