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

Jet Review Process

ASecurity

What to expect from the Journal of Economic Theory (JET) review pipeline — an editor desk-screen stage, single-anonymized (single-blind) refereeing with a floor of at least two reviewers, decisions taken by editors (not a single managing EIC), and the generative-AI bar on referees. Sets expectations and informs how to pre-empt referee objections.

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 jet-review-process --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jet Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jet-review-process
description: What to expect from the Journal of Economic Theory (JET) review pipeline — an editor desk-screen stage, single-anonymized (single-blind) refereeing with a floor of at least two reviewers, decisions taken by editors (not a single managing EIC), and the generative-AI bar on referees. Sets expectations and informs how to pre-empt referee objections.
---

# 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 where reachable)

- **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 single managing editor-in-chief — makes the call. The current
  lead editor is **待核实** (the official editorial-board page was unreachable; verify before naming anyone).
- **Generative-AI bar on evaluators.** Reviewers and editors are **prohibited** from using
  generative-AI tools in the evaluation process; authors, separately, must disclose AI use at submission.

## What this implies for you

- The desk screen rewards a **theory-first scope fit** stated on page one (see jet-topic-selection).
- With **single-blind** review, a referee can place your prior work; phrase self-citations plainly,
  not evasively.
- Two expert referees will **check proofs**, not just read them — every step must survive a hostile read.
- Routing-by-field means the cover letter should name the subfield (mechanism design, decision theory,
  matching, etc.) so the right editor picks it up.

## Output format

```
【Stage now】desk-screen / out-to-referees / decision
【Review model】single-anonymized, ≥2 referees, editor decides
【Pre-empt】<top correctness/generality objection to neutralize> → jet-rebuttal / jet-identification-strategy
【待核实】current lead editor — verify on official board page
```

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 →