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

Jbes Review Process

ASecurity

Use when planning around the Journal of Business & Economic Statistics (JBES) peer-review process — the multi-Co-Editor model, what method referees scrutinize, and the discussion-paper tradition. Sets expectations; it does not draft the response letter (see jbes-rebuttal).

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

Installs into .claude/skills of the current project.

Are you the author of Jbes Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jbes-review-process
description: Use when planning around the Journal of Business & Economic Statistics (JBES) peer-review process — the multi-Co-Editor model, what method referees scrutinize, and the discussion-paper tradition. Sets expectations; it does not draft the response letter (see jbes-rebuttal).
---

# Review Process (jbes-review-process)

## When to trigger

- You want to understand how JBES handles a submission before you send it
- You are deciding how to frame the cover letter for a multi-Co-Editor journal
- You wonder whether your paper could be an invited discussion paper
- You need to anticipate what method referees will attack

## How JBES review is structured

JBES is run by a **rotating panel of Co-Editors / Joint Editors with no single Editor-in-Chief**. The confirmed 2022–2024 term was held by **Atsushi Inoue (Vanderbilt) and Ivan Canay (Northwestern)**; the current Joint Editors are reported as **Yingying Fan (USC), Michael Kolesár (Princeton), and Dacheng Xiu (Chicago)** — 待核实, since this comes from secondary snippets rather than a directly fetched official board page. Practical consequence: unlike a single-Editor-in-Chief journal, **field fit and cover-letter targeting** matter, because a handling Co-Editor whose expertise matches your method is more likely to evaluate and route it well. The submission platform, the peer-review blinding model (single- vs double-anonymized), and review timelines are **待核实** — the official instructions page was inaccessible — so do not assert them; verify on the live page.

## What method referees scrutinize

Because JBES is a **methods-with-empirics** journal owned by the ASA, referees are method experts who interrogate, in order: (1) **statistical validity** — are the assumptions, asymptotics, and inference correct and as general as claimed? (2) **empirical relevance** — is there a substantive application, and does the method genuinely help it? (3) **reproducibility** — can the simulation and empirical results be regenerated from the supplement? A paper strong on only one axis is vulnerable.

## The discussion-paper tradition

JBES has a long-standing association with **invited discussion papers and published comments/rejoinders** (a hallmark shared with leading statistics journals such as JASA). Treat this as a strong convention rather than a verbatim-sourced rule (待核实): a sufficiently novel and broadly relevant method may be handled as a discussion paper, which shapes how the contribution should be pitched.

## Checklist

- [ ] Cover letter targets the method to a plausible handling Co-Editor's expertise
- [ ] The three referee axes (validity / relevance / reproducibility) each addressed
- [ ] No unverified claims about platform, blinding, or timeline in your planning (待核实)
- [ ] Considered whether the paper fits the discussion-paper format
- [ ] ASA editorial/ethics norms (not AEA Data Editor norms) assumed

## Anti-patterns

- Assuming a single Editor-in-Chief and writing a generic cover letter
- Asserting a blinding model or timeline the official page does not confirm
- Submitting strong theory with no application (or vice versa) to a methods-with-empirics journal
- Expecting an AEA-style mandatory pre-publication replication check; JBES follows ASA policy

## Output format

```
【Editor model】multi-Co-Editor; targeted handling editor: ...
【Three axes】validity / relevance / reproducibility addressed? [Y/N each]
【Unverified items】platform / blinding / timeline flagged as 待核实? [Y/N]
【Discussion paper?】plausible fit considered? [Y/N]
【Next step】jbes-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 →