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

Joe Review Process

ASecurity

Use to understand and navigate the Journal of Econometrics (JoE) editorial process — single-anonymized review, editor screening before a minimum of two referees, the three submission tracks (Regular/Annals/Themed), Guest Associate Editors, and what referees of a methods paper look for.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Joe Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: joe-review-process
description: Use to understand and navigate the Journal of Econometrics (JoE) editorial process — single-anonymized review, editor screening before a minimum of two referees, the three submission tracks (Regular/Annals/Themed), Guest Associate Editors, and what referees of a methods paper look for.
---

# Review Process (joe-review-process)

## When to trigger

- You want to know how JoE evaluates a methodological submission, end to end
- You are choosing among the Regular / Annals / Themed Issue tracks
- You are anticipating referee objections before submitting or after a revision request
- You are unsure who decides (editors, Co-Editors, Guest Associate Editors)

## How JoE review works

- **Single-anonymized review:** referees know the authors' identities; authors do **not** know the referees. (待核实: confirm on the live Guide for Authors.)
- **Editor screening first:** editors screen submissions; suitable papers are sent to a **minimum of two independent expert referees**, and the editors make the **final decision**. Unsuitable or out-of-scope papers are desk-screened out.
- **Co-Editors-in-Chief:** Michael Jansson (UC Berkeley) and Aureo de Paula (UCL), supported by a set of Co-Editors. The full current board beyond the two EICs is **待核实** (the editorial-board page 403'd to automated fetches; older RePEc rosters are outdated).

## The three submission tracks

- **Regular Issues** — standard standalone methodological papers; the default route.
- **Annals Issues** — focused volumes assembled around a coherent theme.
- **Themed Issues** — topic-based collections, often originating from conferences. Proposal **organizers may serve as Guest Associate Editors** who make recommendations to the Co-Editors; Themed Issues still go through the **regular editorial process**. If your work matches an active theme, this can be a strong, well-matched route (check the journal's Themes page for current calls).

Pick the track deliberately: a standalone advance → Regular; a contribution that fits an active call → Themed/Annals, where a Guest Associate Editor close to the topic may handle it.

## What methods referees look for

1. **Genuine methodological contribution** with mathematical rigor — proofs/asymptotics, not a relabeled method.
2. **Primitive, verifiable assumptions** and honest asymptotics (no smuggling the conclusion).
3. **Monte Carlo** that reports size and size-adjusted power and stresses the assumptions.
4. **Precise positioning** against the nearest estimator/test.
5. **Reproducibility** — runnable estimator and a `run_all` pipeline.
6. **Scope fit** — a methodological advance, not a purely applied result.

## Practical reading of the process

- A clean editor screen rewards a contribution stated plainly in the abstract/intro (see `joe-contribution-framing`, `joe-writing-style`).
- Because referees are specialists, the closest-competitor comparison and the boundary-case Monte Carlo are where reports are won or lost.
- Expect detailed, technical referee reports; a revision request usually means "make the theory/Monte Carlo airtight," handled in `joe-rebuttal`.

## Anti-patterns

- Treating JoE like a double-anonymized journal and over-anonymizing (it is single-anonymized — 待核实)
- Submitting to a Themed Issue whose scope your paper does not actually match
- Ignoring that editors screen first — a buried contribution dies at the screen
- Assuming a purely applied paper will survive referees here

## Output format

```
【Review model】single-anonymized; editor screen → ≥2 referees
【Track】Regular / Annals / Themed (+ Guest AE if themed)
【Handling editor】Co-Editor / Guest AE; final call by editors
【Referee hot spots】assumptions / asymptotics / size-power / positioning / reproducibility
【Scope check】methodological advance present? [Y/N]
【Next step】joe-submission
```

Attribution

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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', ...

693161 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 →