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

Jaar Review Process

ASecurity

Use to understand how the Journal of the American Academy of Religion (JAAR) evaluates a manuscript — editor pre-screening for broad significance, double-blind review, a roughly 90% rejection rate, a months-long timeline, and a commissioned-only book-review section. Sets expectations and shapes the article to survive; it does not contact editors.

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

Installs into .claude/skills of the current project.

Are you the author of Jaar Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jaar-review-process
description: Use to understand how the Journal of the American Academy of Religion (JAAR) evaluates a manuscript — editor pre-screening for broad significance, double-blind review, a roughly 90% rejection rate, a months-long timeline, and a commissioned-only book-review section. Sets expectations and shapes the article to survive; it does not contact editors.
---

# Review Process (jaar-review-process)

JAAR is highly selective (about **90% of submissions are rejected**) and screens hard **before** peer
review. Knowing the gates lets you avoid the common early deaths and set realistic expectations.

## When to trigger

- Before submitting, to stress-test against JAAR's gates
- Interpreting a decision letter and timeline
- Wondering whether to propose a book review (don't submit unsolicited — see below)

## How JAAR review works

1. **Editorial pre-screening (the first gate).** The editorial office reads **every** submission and
   decides whether to send it out. Two common pre-review outcomes: returned to **reframe** for broad
   significance (if it reads as subfield-only), or advised that **another journal** suits it better.
2. **Double-blind (double-anonymous) review.** Reviewers do not know authors and authors do not know
   reviewers; you submit an **anonymized main document** plus a **separate title page** (see
   `jaar-submission`).
3. **Selectivity.** ~90% rejection; roughly **eight articles per issue / ~32 per year**. Strong,
   field-significant, thesis-driven, method-conscious work clears; description does not.
4. **Timeline.** Plan for a months-long process — up to **six months** to a final decision (an average
   time to first decision around **106 days** was reported as of 2022; 待核实 current figures).
5. **Decisions.** Reject, revise and resubmit, or accept; expect substantive revision for promising work
   (handled in `jaar-revision-and-response`).

## Book reviews (a separate, commissioned track)

- JAAR's **book reviews are commissioned** through the **Book Review Editor**; it does **not** accept
  **unsolicited** reviews and does **not** publish reviews **from graduate students**. Do not plan a
  review submission as an entry point.

## Shape the article to pass

- Make the broad, field-level significance unmistakable in the introduction (avoid the reframing bounce).
- Ensure the essay "has a point" — a contestable thesis, not a survey.
- Show methodological self-awareness and reflexivity; keep it non-confessional.
- Anonymize thoroughly so it can go straight to review.

## Anti-patterns

- A subfield-only framing that triggers the pre-review reframing return
- A descriptive piece with no thesis
- Confessional/advocacy tone that reads as non-scholarly
- Submitting an unsolicited book review (not accepted)
- Expecting a fast decision (the process takes months)

## Output format

```
【Pre-screen risk】broad significance obvious? reframing needed? [Y/N]
【Has a point?】contestable thesis present? [Y/N]
【Method/reflexivity】evident and non-confessional? [Y/N]
【Anonymized】ready for double-blind? [Y/N]
【Expectation】reject / R&R / accept; months-long timeline
【Next】jaar-submission (or jaar-revision-and-response if decided)
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — pre-screening, double-blind, ~90% rejection, timeline, commissioned reviews

Attribution

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

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