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

Jpube Review Process

ASecurity

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

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jpube Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jpube-review-process
description: Use to understand and plan around the Journal of Public Economics (JPubE) editorial process — single anonymized review with a minimum of two reviewers, the Editorial Manager workflow, the Friedman–Kopczuk editorial leadership, SSRN preprint option, and the one-appeal policy. Explains the process; for the final file check use jpube-submission.
---

# 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 journal is run by **Co-Editors-in-Chief John N. Friedman (Brown)** and **Wojciech Kopczuk (Columbia)**, supported by an editorial board (full current board 待核实). A handling editor manages your manuscript and synthesizes the reports into the decision.
- **Editorial Manager workflow.** Submission and all correspondence run through Elsevier's **Editorial Manager** system; decisions (desk reject / reject / major or minor revision / accept) and revision uploads happen there.
- **SSRN preprint option.** At submission you may opt to have the manuscript posted publicly on **SSRN** after initial quality checks; this choice has **no effect on the editorial process or outcome**, so it is a free dissemination option, not a strategic lever.
- **Generative-AI disclosure** is required at submission and is part of the editorial-integrity screen.

## Appeals (verified)

- Formal **appeals are permitted** under Elsevier's Appeal Policy, but **only one appeal per submission** is considered. Treat the appeal as a scarce, one-shot instrument: use it only for a clear factual or procedural error in the handling of the paper, with a calm, evidence-based case — not to relitigate taste. (See `jpube-rebuttal` for crafting the substance.)

## Planning implications

- Write for **named, specialist referees** who can see your identity — frame contribution and self-citations accordingly.
- Do not over-invest in anonymization; invest in a transparent design two specialist reviewers can endorse.
- Decide the SSRN option deliberately (visibility vs. preferring to wait), knowing it does not change your odds.

## Checklist

- [ ] Manuscript written for single-anonymized (identity-visible) specialist review
- [ ] Expect ≥ 2 reviewers; address the obvious public-finance objections pre-emptively
- [ ] Editorial Manager account and metadata ready
- [ ] SSRN preprint decision made deliberately
- [ ] AI-use disclosure prepared
- [ ] Appeal reserved for a clear error, used at most once

## Anti-patterns

- Stripping author identity expecting double-blind review (JPubE is single anonymized)
- Treating the SSRN option as if it improved acceptance odds
- Burning the single appeal on a taste disagreement instead of a factual/procedural error
- Ignoring AI disclosure requirements during submission

## Output format

```
【Review model】single anonymized (identity visible), ≥2 reviewers — understood? [Y/N]
【Editorial Manager】account + metadata ready? [Y/N]
【SSRN preprint】opt-in decision: [yes/no]
【AI disclosure】prepared? [Y/N]
【Appeal status】reserved for clear error, ≤1 use — noted? [Y/N]
【Next step】jpube-submission
```

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 →