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

Jar Review Process

ASecurity

Use when setting expectations for how Journal of Accounting Research (JAR) review and decisions work, or when reading a JAR decision letter — the Senior-Editor-panel structure, double-anonymized review, the desk-screen and tiered-fee gate, and the distinctive Ray Ball Conference and Registered Reports tracks. Explains the process; it does not draft the R&R response (jar-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 jar-review-process --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jar Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jar-review-process
description: Use when setting expectations for how Journal of Accounting Research (JAR) review and decisions work, or when reading a JAR decision letter — the Senior-Editor-panel structure, double-anonymized review, the desk-screen and tiered-fee gate, and the distinctive Ray Ball Conference and Registered Reports tracks. Explains the process; it does not draft the R&R response (jar-rebuttal).
---

# Understanding the JAR Review Process (jar-review-process)

## When to trigger

- Before submitting, to understand what to expect at JAR specifically
- A decision letter arrived and you need to read it correctly
- You are deciding between the regular track, a Registered Report, or the conference
- You are unsure how the editor-panel structure assigns and decides papers

## How JAR is governed and decides

JAR has **no single editor-in-chief**. It is run by a panel of **Senior Editors** (Philip G. Berger, Anna Costello, Luzi Hail, Valeri Nikolaev, Haresh Sapra, Laurence van Lent, Regina Wittenberg Moerman), supported by ~18 Associate Editors and Editorial Manager Lisa M. Heiberger. A submission is assigned to a Senior Editor who, typically with one or more Associate Editors and external referees, runs a **double-anonymized** review of regular manuscripts. The journal is sponsored by the **Chookaszian Accounting Research Center at Chicago Booth** and published with Wiley-Blackwell — a single-center "house" identity rather than a scholarly-society journal.

## Gates before and during review

- **Desk screen / conformance.** Non-conforming submissions can be **desk-rejected** (with only a **half refund** of the fee). Get format, anonymization, scope, and the article type right before submitting.
- **Tiered fee gate.** The **$750 / $500 / $50** fee must be **received within one week** or the paper is withdrawn — an explicit pay-to-review gate; budget for it.
- **Submission cap.** At most **four new papers per author over a rolling two-year period** (R&Rs excluded) — plan which projects to send.

## Reading a JAR decision

Outcomes range from desk reject, to reject after review, to **revise-and-resubmit (R&R)**, to (rarely on a first round) acceptance. Treat an R&R as a serious invitation: identify which referee concerns are **first-order** (identification, the channel, sample/measurement) versus second-order (exposition, additional robustness). The Senior Editor's letter is the binding guide — it prioritizes among the referees. First-round accepts are essentially unheard of; multiple rounds are normal.

## The distinctive tracks

- **Ray Ball JAR Annual Conference.** A flagship conference at Chicago Booth funded by the Chookaszian Center; selected papers are considered **simultaneously** for the conference and for journal publication and appear in the **conference issue** (historically June) **subject to passing normal editorial review**. The **62nd (2027)** conference is themed **"Current Topics in Accounting Research by Emerging Scholars,"** giving **preference to untenured authors who received a PhD no earlier than 2017**; submission deadline **Dec 1, 2026**; conference dates **Apr 30-May 1, 2027**. Verify the current call.
- **Registered Reports.** A **two-stage** process pioneered at JAR in 2017 (with Robert Bloomfield): authors pre-register hypotheses and an analysis plan; after **Stage 1** protocol review the journal grants **in-principle acceptance**, guaranteeing publication regardless of whether results support predictions, provided the approved protocol is followed at **Stage 2**. Best for higher-outcome-risk work requiring new data collection.

## Checklist

- [ ] You know which Senior Editor track / article type fits and submitted accordingly
- [ ] Format/anonymization conform (to avoid a half-refund desk reject)
- [ ] Fee payment within one week is arranged; within the four-new/two-year cap
- [ ] You have parsed the editor letter's first-order vs. second-order concerns
- [ ] If relevant: Ray Ball eligibility/deadline or Registered Reports stage understood

## Anti-patterns

- **Treating JAR like a single-EIC journal** — it is an editor panel.
- **Skimping on conformance** and drawing a desk reject with only a half refund.
- **Reading every referee point as equal** instead of following the editor's priorities.
- **Misusing the conference track** (ignoring eligibility/theme) or the RR track (no real pre-registration).

## Output format

```
【Decision type】desk reject / reject / R&R / accept
【Editor priorities】first-order: [...]; second-order: [...]
【Track】regular / Ray Ball conference / Registered Report (stage)
【Gates】conformance / fee-timing / submission-cap status
【What to do next】revise per editor → jar-rebuttal
```

## Resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — official JAR/Chicago Booth/Wiley URLs (accessed 2026-06-01); editor roster and conference theme are live-check items
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — submission and reproducibility tooling

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 →