jet-review-process
Use when interpreting the Journal of Economic Theory (JET) review pipeline — editor desk-screening, single-anonymized refereeing, at least two reviewers, editor decisions, and the generative-AI bar on referees.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jet-review-process --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Review Process (jet-review-process) ## When to trigger - You want to understand how JET evaluates a theory submission before sending it - You are deciding how defensively to write proofs and which objections to pre-empt - You received a decision and want to read it against JET's actual process ## How JET evaluates (verified 2026-06-20) - **Two-stage flow.** Editors first assess **suitability** (a desk-screen / desk-rejection stage); papers that pass are sent out for refereeing. - **Single anonymized review (single-blind).** Referees see author identities; authors do not see referee identities. This differs from QJE/AEA-style double-blind — so **do not** rely on anonymization to neutralize reputation effects; let the result and proofs carry the paper. - **Minimum of two referees.** Papers that clear the desk screen go to **at least two** independent expert reviewers for assessment of correctness, originality, and the size of the theoretical contribution. - **Editors decide.** The accept/reject decision is taken by the **editors**. JET uses a multi-editor **"Lead Editor + Editors"** governance: a submission is routed to whichever editor's field best matches, and that editor — not a
- When to trigger
- How JET evaluates (verified 2026-06-20)
- What this implies for you
- What a JET referee checks first
- Desk-reject patterns for theory submissions
- Self-referee pass (run before submitting)
- Output format
What does the jet-review-process skill do?
Use when interpreting the Journal of Economic Theory (JET) review pipeline — editor desk-screening, single-anonymized refereeing, at least two reviewers, editor decisions, and the generative-AI bar on referees.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jet-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.